-
Couldn't load subscription status.
- Fork 190
Open
Description
@likewhatevs I am opening a separate issue out of the pull request so we can discuss adding a CI job for WD40. The scheduler should only fail when it gets added features that have not yet been merged into upstream trees, though that happens from time to time. I assume we can add a CI job that fails silently to avoid excessive noise, right? Basically same way we were treating the CI jobs against bpf-next in the past.
Metadata
Metadata
Assignees
Labels
No labels