Skip to content

various: move throws to aliases#426639

Merged
wolfgangwalther merged 4 commits intoNixOS:masterfrom
wolfgangwalther:ci-eval-asserts-aliases
Jul 21, 2025
Merged

various: move throws to aliases#426639
wolfgangwalther merged 4 commits intoNixOS:masterfrom
wolfgangwalther:ci-eval-asserts-aliases

Conversation

@wolfgangwalther
Copy link
Contributor

In some cases we throw for already removed packages. These should only be there with aliases enabled. This helps when generating all attrpaths for evaluation in CI.

Part of #426629, ultimately targeting #397184.

Things done


Add a 👍 reaction to pull requests you find important.

@nixpkgs-ci nixpkgs-ci bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 6.topic: python Python is a high-level, general-purpose programming language. 6.topic: haskell General-purpose, statically typed, purely functional programming language labels Jul 19, 2025
@nixpkgs-ci nixpkgs-ci bot added the 12.approvals: 1 This PR was reviewed and approved by one person. label Jul 19, 2025
@nixpkgs-ci nixpkgs-ci bot added 12.approvals: 2 This PR was reviewed and approved by two persons. and removed 12.approvals: 1 This PR was reviewed and approved by one person. labels Jul 19, 2025
@ConnorBaker
Copy link
Contributor

Why the removal of the older versions of Magma?

@wolfgangwalther
Copy link
Contributor Author

As the commit message says: When I try to eval them, I get this error:

the required ROCm 5.7 version for magma 2.6.2 has been removed

Thus, my understanding is that they are already dead effectively, since ROCm 5.7 was removed. Thus, I just turn them into aliases - they already throw anyway.

Is my understanding wrong? Can these still be sensibly used?

@ConnorBaker
Copy link
Contributor

They can, they still build with CUDA -- those eval failures should only occur if ROCm support is enabled. However, the only consumer of Magma in-tree is PyTorch, and IIRC it only builds with the latest... so I suppose the removal is actually for the best :)

@wolfgangwalther
Copy link
Contributor Author

They can, they still build with CUDA -- those eval failures should only occur if ROCm support is enabled.

Ah, OK, I see. If we were to keep them, we'd have to either mark them as broken conditionally or do something like #426645 ...

However, the only consumer of Magma in-tree is PyTorch, and IIRC it only builds with the latest... so I suppose the removal is actually for the best :)

... but dropping them is much easier. I reflected that in the commit message, which is now ..: drop.

@wolfgangwalther wolfgangwalther force-pushed the ci-eval-asserts-aliases branch from 4e5ff45 to 0cd0bb4 Compare July 20, 2025 09:02
@prusnak
Copy link
Member

prusnak commented Jul 20, 2025

+1 for dropping older magma, but the throw message should read something like magma 2.6.2 has been removed. use the latest magma package. instead - mentioning ROcm in throw is confusing especially if building with CUDA

@wolfgangwalther wolfgangwalther force-pushed the ci-eval-asserts-aliases branch from 0cd0bb4 to 67b0c70 Compare July 20, 2025 10:01
@wolfgangwalther
Copy link
Contributor Author

wolfgangwalther commented Jul 20, 2025

+1 for dropping older magma, but the throw message should read something like magma 2.6.2 has been removed. use the latest magma package. instead - mentioning ROcm in throw is confusing especially if building with CUDA

Makes sense, changed accordingly. I also went through magma's generic builder and removed all conditionals for older than the currently only packaged version. If you want to keep any of that, I can revert things there. Let me know.

(another force push fixed treefmt)

These throw this error on eval right now:

```
the required ROCm 5.7 version for magma 2.6.2 has been removed
```

They'd technically be usable with CUDA, but are not used in-tree.
This had already been removed and should be an alias now.
This is required to make CI work properly.
@wolfgangwalther wolfgangwalther force-pushed the ci-eval-asserts-aliases branch from 67b0c70 to 1d4e069 Compare July 20, 2025 10:05
@nixpkgs-ci nixpkgs-ci bot added 12.approvals: 3+ This PR was reviewed and approved by three or more persons. and removed 12.approvals: 2 This PR was reviewed and approved by two persons. labels Jul 21, 2025
@wolfgangwalther wolfgangwalther merged commit 174e6bb into NixOS:master Jul 21, 2025
26 of 28 checks passed
@wolfgangwalther wolfgangwalther deleted the ci-eval-asserts-aliases branch July 21, 2025 06:09
@nixpkgs-ci
Copy link
Contributor

nixpkgs-ci bot commented Jul 22, 2025

Successfully created backport PR for release-25.05:

@github-actions github-actions bot added the 8.has: port to stable This PR already has a backport to the stable release. label Jul 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: haskell General-purpose, statically typed, purely functional programming language 6.topic: python Python is a high-level, general-purpose programming language. 8.has: port to stable This PR already has a backport to the stable release. 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. 12.approvals: 3+ This PR was reviewed and approved by three or more persons.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants