treewide: mark failing packages as broken#451447
Conversation
|
trilinos is 4 major behind! |
xyce can unpin trilions accroding to spack https://github.com/spack/spack-packages/blob/5ce2e954ef85769b410ce2550bac78382d75be27/repos/spack_repo/builtin/packages/xyce/package.py#L106 i will give it a try to upgrade trilinos since some of my packages (e.g. petsc) may optional rely on trilinos. |
3073512 to
6b59b31
Compare
|
Can we add a short comment why those packages where marked broken? Otherwise it is not easy to assess afterwards if it is worth fixing them or it can be just dropped. |
22b3bf6 to
50d4848
Compare
|
I added a more recent evaluation, which removed from this PR all of the packages iedame mentioned except scipopt-gcg, which I removed manually. I also added a comment for each package. |
|
some packages failed due to cmake v4 error. e.g. itk_5_2/getdp. itk is not broken, only mark broken for itk version 5.2. Also, getdp's original source url is not available anymore, the fix will be getdp 4.0 (currently 4.0 is not released). |
9b07cb2 to
1f3b573
Compare
1f3b573 to
30f460e
Compare
On 16 separate Hydra evaluations (which I selected for their relatively low failure numbers, and which span just over a year), these packages have done nothing other than fail for all platforms. For Python packages, they also fail across all built Python versions.
04df981 to
1d64177
Compare
|
Rebased again, removed all packages that have been fixed as of https://hydra.nixos.org/eval/1820524 or dropped. Still no changes beyond running |
lukegb
left a comment
There was a problem hiding this comment.
Sounds good (at least from my perspective for oven-media-engine). Are you planning on marking these as broken in 25.11 as well?
|
Yes, I was going to backport this. Thanks for the reminder! |
|
Successfully created backport PR for |
| }; | ||
|
|
||
| meta = { | ||
| # Marked broken 2025-11-28 because it has failed on Hydra for at least one year. |
There was a problem hiding this comment.
This broke eval of everything on cygwin. master already had a fix for this by limiting the platform to cygwin. I'd like to remove the broken flag in #468157.
There was a problem hiding this comment.
Noted; looks like 9dd0669 post-dates my PR, which would explain why I missed it :).
On 12 separate Hydra evaluations (which I selected for their relatively low failure numbers, and which span over a year), these packages have done nothing other than fail for all platforms.
That is, if a package had a status other than "Failed" on any platform for any of the selected evaluations, it is not included here.
For Python packages and Linux kernel modules, they also fail across all built Python versions (so if the package succeeds with Python 3.12 but fails with Python 3.13, it's not included here).
The marking itself was done with
pkgs/common-updater/scripts/mark-broken, generation of the packages to be marked was done with a modification to https://git.helsinki.tools/janne.hess/zhf/-/commits/master and a custom Python script.This should have 0 rebuilds.
Things done
passthru.tests.nixpkgs-reviewon this PR. See nixpkgs-review usage../result/bin/.Add a 👍 reaction to pull requests you find important.