You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I was installing a whole bunch of apps using an easystack file, and suddenly it crashed at the installation of zlib-1.2.12.eb because $EBROOTZLIB was already set. I hadn't done that myself (started with a clean environment), and after inspecting the log file, I noticed that for all installations after the very first one Easybuild was warning that a bunch of modules were loaded. This list consisted of the (build) dependencies of the first application that it installed.
I was able to reproduce it with a simple example, using this easystack file:
Installing this with eb -f --experimental --easystack test.yml (note that the dependencies of attr are already available on my system) results in a successful installation of attr, but:
So it looks like it didn't unload the attr (build) dependencies. This is with EB 4.7.0, and based on some older logs of applications built with a similar easystack (but with the old structure) and EB 4.6.2, the latter version didn't have this issue.
The text was updated successfully, but these errors were encountered:
That likely introduced with the changes in #4057, which includes a large refactor.
We're probably not properly resetting the build environment after completing an installation?
Thanks a lot for reporting this @bedroge, we'll look into catching this in a CI test, and fixing it - as it is now, easystack files aren't exactly production ready, that's clear...
I was installing a whole bunch of apps using an easystack file, and suddenly it crashed at the installation of
zlib-1.2.12.eb
because$EBROOTZLIB
was already set. I hadn't done that myself (started with a clean environment), and after inspecting the log file, I noticed that for all installations after the very first one Easybuild was warning that a bunch of modules were loaded. This list consisted of the (build) dependencies of the first application that it installed.I was able to reproduce it with a simple example, using this easystack file:
Installing this with
eb -f --experimental --easystack test.yml
(note that the dependencies ofattr
are already available on my system) results in a successful installation ofattr
, but:The
attr
log has:But the one for
zlib
has:So it looks like it didn't unload the
attr
(build) dependencies. This is with EB 4.7.0, and based on some older logs of applications built with a similar easystack (but with the old structure) and EB 4.6.2, the latter version didn't have this issue.The text was updated successfully, but these errors were encountered: