-
Notifications
You must be signed in to change notification settings - Fork 1.1k
CI: Consolidate and blanket-ignore kernel definitions on non-glibc #2113
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
r? @Amanieu (rust-highfive has picked a reviewer for you, use r? to override) |
This also experimentally removes |
FYI: https://www.githubstatus.com/incidents/s654n76c1bwr |
Looks reasonable to me.
Let's check it, @bors r+ |
📌 Commit db07dbc has been approved by |
CI: Consolidate and blanket-ignore kernel definitions on non-glibc Skip definitions from the kernel on non-glibc Linux targets. They're libc-independent, so we only need to check them on one libc. We don't want to break CI if musl or another libc doesn't have the definitions yet. (We do still want to check them on every glibc target, though, as some of them can vary by architecture.)
💔 Test failed - checks-actions |
Actually, failed on |
Skip definitions from the kernel on non-glibc Linux targets. They're libc-independent, so we only need to check them on one libc. We don't want to break CI if musl or another libc doesn't have the definitions yet. (We do still want to check them on every glibc target, though, as some of them can vary by architecture.)
Fixed. @bors r=JohnTitor |
📌 Commit 0a9aec7 has been approved by |
☀️ Test successful - checks-actions, checks-cirrus-freebsd-11, checks-cirrus-freebsd-12, checks-cirrus-freebsd-13 |
Skip definitions from the kernel on non-glibc Linux targets.
They're libc-independent, so we only need to check them on one
libc. We don't want to break CI if musl or another libc doesn't
have the definitions yet. (We do still want to check them on
every glibc target, though, as some of them can vary by
architecture.)