{devel}[multiple] Define MAX_JOBS in easyconfigs of PyTorch from v1.1.0 to v1.4.0#10772
Conversation
|
@boegel Can you take a look at these failed unit tests please? It's weird, it seems that the easyconfigs in gets converted to |
|
@lexming The tests for PyTorch easyconfigs using Python 3.7.x as dependency are indeed failing now because because of the The culprit is the change you are making though, indirectly at least: you're introducing An easy workaround here is to inject a value for the To proper fix is probably to make the template injection in the dumped easyconfig a bit less aggressive, but I doubt that's a trivial thing to fix (I've opened an issue for this at easybuilders/easybuild-framework#3380). |
|
@boegel that is much more complex than anticipated, thanks for the workaround |
|
Test report by @boegel |
|
Test report by @boegel |
|
Test report by @boegel |
|
Going in, thanks @lexming! |
|
Test report by @lexming |
|
Test report by @lexming |
|
Test report by @lexming |
|
Test report by @lexming |
|
Test report by @lexming |
|
Test report by @lexming |
|
FYI: I moved that into the EasyBlock I'm creating: easybuilders/easybuild-easyblocks@919d22b |
(created using
eb --new-pr)Explicitly set
MAX_JOBSto theparallelsetting from EB to avoid build errors from excessive parallelism. The build of PyTorch by default uses all cores physically present in the system.