Conversation
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1735/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Wouldn't you be better off inheriting from the existing boost easyblock and only changing what you need to...or building the necessary logic into the existing boost easyblock? |
|
@ocaisa sure, but I'd like to hear what's the recommended way before tackling that... |
|
Just FIY: This block is based on my PR that I submitted some time ago and this has the problem that it expects aprun to be available on the machine where you build things. |
|
+1 for deriving from existing Boost easyblock, (way) too much copy-pasting now... |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1737/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1738/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
| self.log.info("PRGENV_MODULE_NAME_SUFFIX is %s " % (self.toolchain.PRGENV_MODULE_NAME_SUFFIX)) | ||
| # self.log.info("TC_CONSTANT_CRAYPE is %s " % (self.toolchain.TC_CONSTANT_CRAYPE)) | ||
| #if self.toolchain.TC_CONSTANT_CRAYPE in [toolchain.CRAYPE+'_GNU', toolchain.CRAYPE+'_Intel'] : | ||
| if self.toolchain.PRGENV_MODULE_NAME_SUFFIX in ['gnu', 'intel'] : |
There was a problem hiding this comment.
This would need to be a bit more specific and should also contain a conditional branch for 'cce' and 'pgi' probably (even if that would be just to bail).
There was a problem hiding this comment.
@pforai I've added cray to the list but since we check for a cray toolchain (and I'm not planning to fix boost on -cray or -intel right now), maybe I'll just drop this test for the moment?
unless someone volunteers to work on the intel/cray boost support...
|
Any chance to just enhance the existing Do we have a good way of checking whether we're running Or does |
|
@boegel well I dont feel confident enough to modify the original easyblock without breaking other builds (meaning that I don't have much time for testing now, I'm just bulk pushing things that were waiting for the new cray toolchains). But if that boils down to adding an extra test to check if TC is Cray*, then I think I can do it ;) I'll start with |
|
@gppezzi we can help out with testing and making sure you're not breaking backwards compatibility; It's good that you're pushing out the things you've worked on, and are willing to take the effort to contribute back, thanks for that! |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1767/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
| else: | ||
| f.write("using mpi : %s ;" % os.getenv("MPICXX")) | ||
|
|
||
| f.close() |
There was a problem hiding this comment.
please replace this with:
write_file('user-config.jam', txt, append=True)and construct txt above
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1799/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1800/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1801/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
Easyblocks unit test suite PASSed (see https://jenkins1.ugent.be/job/easybuild-easyblocks-pr-builder/1802/console for more details). This pull request is now ready for review/testing. Please try and find someone who can tackle this; contact @boegel if you're not sure what to do. |
|
@boegel fixed most of remarks, I'll check tomorrow how to correctly bail out in case of unsupported PrgEnv |
|
I've updated the easyblock to avoid the hardcoded reference to aprun/srun, now the mpi launcher can be specified through an extra_var. This argument is optional and it is only used for the regression tests (which we are currently not doing). @pforai The argument Build reports will be provided here |
|
@gppezzi Thanks, it looks perfect |
| else: | ||
| txt = "using mpi : %s ;" % os.getenv("MPICXX") | ||
|
|
||
| write_file('user-config.jam', txt, append=True) |
There was a problem hiding this comment.
@gppezzi indentation seems off here? should be intended one level deeper, so it's in the if self.cfg['boost_mpi']:, otherwise txt is undefined
fix indent on write_file for user-config.jam + minor style issues in Boost easyblock
|
Tested with easybuilders/easybuild-easyconfigs#2615 and existing Boost easyconfigs, good to go, thanks @gppezzi & @pforai! |
|
Thanks everyone for the feedback and help! |
This easyblock is a tweaked version of boost.py for supporting Cray.
I don't know if it is preferable to include Cray support on the original one (but I don't want to break existing builds...)