Use context managers for templating changes in Bundle easyblock#3547
Use context managers for templating changes in Bundle easyblock#3547boegel merged 3 commits intoeasybuilders:5.0.xfrom
Bundle easyblock#3547Conversation
f004583 to
2f114d0
Compare
|
Found a new failure cause by resolving Only question would be if we want to reduce the scope of the template-disabling and use some more for the updates. Maybe group the cfg.update statements for less clutter |
2f114d0 to
4788b70
Compare
- `default_component_specs` must not be resolved - `self.cfg.update` resolves the current value before doing the update. Just put the whole code inside the context manager to use the old behavior
4788b70 to
6a26673
Compare
|
Using the framework PR in a venv setup with: Test report by @Flamefire Overview of tested easyconfigs (in order)
Build succeeded for 15 out of 19 (16 easyconfigs in total) |
|
@Flamefire What's with the failing test builds? |
|
It's only R that failed to build due to a filesystem issue:
I'm "currently" installing R again. 811/1203 packages so far, running for 7 hrs... |
With EasyBuild 5.0dev, you should be able to use |
|
Test report by @Flamefire Overview of tested easyconfigs (in order)
Build succeeded for 19 out of 19 (16 easyconfigs in total) |
Bundle easyblock
|
Test report by @boegel Overview of tested easyconfigs (in order)
Build succeeded for 10 out of 10 (10 easyconfigs in total) |
This ensures the old value is restored in all cases.
Note that there is some whitespace change which makes the diff look larger
Requires:
enable_templatingandexpect_resolved_template_valueseasybuild-framework#4735See also #3537 for the previous change to this code part