-
-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
18.03 Zero Hydra Failures - aarch64 edition #32326
Comments
|
Hmm, at this rate of almost four thousand failing jobs (and no fast progress), we might need some script to exclude aarch64 automatically for packages that remain failing at the end of the month. |
I think the single biggest cause is every single Haskell package failing, due to some old GHC not supporting AArch64, disabling the platform for that should cut a couple of thousand easily. |
@peti ^^ in case you have some simple idea how to work around the problem. |
The final ghc build timed out on Hydra. I tried twice on the community machine, but it always segfaulted after a few hours. EDIT: we'll see – I suppose we may give up on Haskell on aarch64 for now... |
kbfs is broken because it uses a vendored keybase client which doesn't support arm (the non vendored one does). I'll send them a PR to get it fixed. EDIT - nvm this is working currently. |
{qt5,qt511,qt59}.qtwebengine are now passing: https://hydra.nixos.org/eval/1475582 |
I think we need a new working list for 18.09. |
We should have a hydra jobset for that in less than a week (after branching off master). |
Thanks for all the fixes in 18.03 round! (I'm late, I know.) The next ZHF iteration: #45962 |
See the generic description. This mainly makes a place to discuss aarch64-specific issues for ZHF.
As of https://hydra.nixos.org/eval/1430755, there are 263 aarch64-specific failures (here the exact criterion is: never succeeded in the trunk jobset on aarch64, is currently succeeding on x86_64, is not broken only due to failing dependencies):
(I'm re-using this as a scratchpad for some notes on why the packages are failing; that is for the unticked "needs marking x86-only" ones I just haven't got around to writing a patch yet, feel free to be faster than me to commit).
The text was updated successfully, but these errors were encountered: