Skip to content
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

distinguish known-bad targets from random failures #2

Open
Habbie opened this issue Jun 29, 2023 · 0 comments
Open

distinguish known-bad targets from random failures #2

Habbie opened this issue Jun 29, 2023 · 0 comments

Comments

@Habbie
Copy link
Member

Habbie commented Jun 29, 2023

In our job matrix (currently 92 big) there are a few targets that really fail at build-time for a few reasons (that we should enumerate). Let's call those "known bad targets" for our specific purpose. Then, sometimes specific target/version combinations fail because, say, git.openwrt.org was having a moment. We currently have no way to distinguish these two failure modes from each other other than manually going over each one.

We should, once, and then periodically, go over all, and decide which targets we can do without (because they fail consistently), and fail the build if any other targets didn't pass the build for transient reasons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant