{tools}[GCCcore/13.3.0] maturin v1.8.3, uv-build v0.7.5 w/ Rust 1.86.0#25461
{tools}[GCCcore/13.3.0] maturin v1.8.3, uv-build v0.7.5 w/ Rust 1.86.0#25461sassy-crick wants to merge 3 commits intoeasybuilders:developfrom
Conversation
…uild-0.6.13-GCCcore-13.3.0.eb, uv-build-0.7.5-GCCcore-13.3.0.eb
|
Diff of new easyconfig(s) against existing ones is too long for a GitHub comment. Use |
|
@boegelbot please test @ jsc-zen3 |
|
@sassy-crick: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3974563446 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
I think the maturin should be independent on Rust: #22763. No need for versionsuffix |
That puzzled me a bit to be honest. The only difference I can see is that |
|
Test report by @pavelToman |
|
@boegelbot please test @ jsc-zen3 |
|
@sassy-crick: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 3991127483 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
I'm wondering: Why 2 versions of uv-build? |
|
Test report by @Flamefire |
|
Test report by @Flamefire Failure is with an EC from another PR, so fine here |
No particular reason. As I had two, I thought I might as well upload them. Easy to kick out the older one and either way is fine with me. |
|
Then I would only keep the newer one. We already have too many easyconfigs ;-) |
|
@boegelbot please test @ jsc-zen3 |
|
@sassy-crick: Request for testing this PR well received on jsczen3l1.int.jsc-zen3.fz-juelich.de PR test command '
Test results coming soon (I hope)... Details- notification for comment with ID 4005687631 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
(created using
eb --new-pr)