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

Builds failing for > 30 days #15191

Closed
thisisnic opened this issue Jan 4, 2023 · 7 comments
Closed

Builds failing for > 30 days #15191

thisisnic opened this issue Jan 4, 2023 · 7 comments

Comments

@thisisnic
Copy link
Member

@jonkeane and I were discussing the builds which have been failing; there are a lot of conda packaging jobs which have been failing for > 30 days now - see http://crossbow.voltrondata.com/

Do we want to either fix them, or if they're not important, then remove them?

@assignUser
Copy link
Member

Those were renamed/removed jobs and I just fixed that in ursacomputing/crossbow#53 🎉

@paleolimbot is already looking at reproducing the libc++ abi issue so we can also get the last long failing autobrew job green again 🚀

@jonkeane
Copy link
Member

jonkeane commented Jan 4, 2023

Oh wow, I didn't realize just how many of those jobs that were marked as failing consistently were false alarms, I'm really glad we've cleaned that up! These are the issues I'm seeing after that clean up:

And the rest are much more under control vis a vis consistent failing.

@paleolimbot
Copy link
Member

I believe #15001 covers the both sanitizer fails! (The failure is also present on the valgrind job, which includes a test failure and a failure due to memory leaks).

@jonkeane
Copy link
Member

jonkeane commented Jan 4, 2023

Thanks for that, I've updated my comment to show that (but left the original crossed out so as not to gas light!)

@assignUser
Copy link
Member

verify-rc-source-csharp-macos-arm64 has been flakey for a long time now, I once asked (in May) on the ML for c# maintainers to please have a look but no one did.... :(

@westonpace
Copy link
Member

@assignUser do we have an issue for the csharp failure? I'll try and take a look at it tomorrow.

@assignUser
Copy link
Member

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

5 participants