{tools}[GCCcore/14.2.0] EasyErgo v1.0.1 w/ EasyBuild 5.1.0#23009
{tools}[GCCcore/14.2.0] EasyErgo v1.0.1 w/ EasyBuild 5.1.0#23009Micket wants to merge 2 commits intoeasybuilders:developfrom
Conversation
|
@boegelbot please test @ jsc-zen3 |
|
@Micket: 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 2934414380 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
Test report by @Micket |
|
Hrm.. i dropped to just using easybuild-easyblocks and easybuild-framework as dependencies, but when i build this i still hit I have no idea how the bot succeeded at jsc-zen3... |
|
@boegelbot please test @ jsc-zen3 |
|
@Micket: 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 2934968120 processed Message to humans: this is just bookkeeping information for me, |
|
Test report by @boegelbot |
|
@Micket I don't think the bot loads an edit: looks like that's indeed the cause. I also fail the sanity check if I build with my |
|
So, it's EB module being clever and unloading itself for the build. Not sure how i can work around that. on a side note, I wanted to add this as an option, anyone curious about using this can just install it into a venv of course. I'm tempted to maybe switch my EB installs into just a |
|
I'm just going with the UV approach for this in my instructions. |
|
Makes sense, it's certainly easier than trying to get this PR to work cleanly |
(created using
eb --new-pr)Decided to add a versionsuffix as we would typically need to update this whenever the new EB release is out.
Also dropped to using easybuild-framework and easybuild-easyblocks in the pyproject.toml so that i don't have to worry about that
easybuildpip check.