[easybuild] RE: EasyBuild 5 and Community Feedback
Dear EasyBuilders, Thanks to those who have left feedback on the potential EasyBuild 5 changes mentioned below. If you wish to leave feedback then please do so this week. The EasyBuild 5.0 Working Group Meeting take place on the first Wednesday of each month at 14:00 CEST (https://time.is/CEST). This means that the next one will be next week - Wednesday 5th July. Regards, Simon From: easybuild-requ...@lists.ugent.be On Behalf Of Simon Branford Sent: 07 June 2023 15:47 To: easybuild@lists.ugent.be Subject: [easybuild] EasyBuild 5 and Community Feedback Dear EasyBuilders, We have started work on EasyBuild 5. Very initial, and work in progress, information is available at https://docs.easybuild.io/easybuild-v5/overview-of-changes/ As part of this we are requesting community feedback on some of the potential changes: * Toolchain Support Policy: https://github.com/easybuilders/easybuild/issues/872 * Minimum supported Lmod Version: https://github.com/easybuilders/easybuild/issues/871 If you wish to feedback on either of those then please add comments to the GitHub issues. Regards, Simon -- Dr Simon Branford Deputy Leader of the Research Software Group and Principal Research Software Engineer Research Software Group, Advanced Research Computing IT Services, University of Birmingham Web: https://www.birmingham.ac.uk/bear-software Support: https://itservicedesk.bham.ac.uk/
[easybuild] EasyBuild 5 and Community Feedback
Dear EasyBuilders, We have started work on EasyBuild 5. Very initial, and work in progress, information is available at https://docs.easybuild.io/easybuild-v5/overview-of-changes/ As part of this we are requesting community feedback on some of the potential changes: * Toolchain Support Policy: https://github.com/easybuilders/easybuild/issues/872 * Minimum supported Lmod Version: https://github.com/easybuilders/easybuild/issues/871 If you wish to feedback on either of those then please add comments to the GitHub issues. Regards, Simon -- Dr Simon Branford Deputy Leader of the Research Software Group and Principal Research Software Engineer Research Software Group, Advanced Research Computing IT Services, University of Birmingham Web: https://www.birmingham.ac.uk/bear-software Support: https://itservicedesk.bham.ac.uk/
RE: [easybuild] EB file for building a recent version of Meep?
Hi Ole, Yes, we have an easyconfig for 1.25 - see https://github.com/bear-rsg/bear-eb/blob/main/easyconfigs/m/Meep/Meep-1.25.0-foss-2021b.eb Regards, Simon -Original Message- From: easybuild-requ...@lists.ugent.be On Behalf Of Ole Holm Nielsen Sent: 26 May 2023 09:29 To: easybuild Subject: [easybuild] EB file for building a recent version of Meep? CAUTION: This email originated from outside the organisation. Do not click links or open attachments unless you recognise the sender and know the content is safe. We have a user request for installing the Meep module. However, the versions of Meep in EasyBuild are very old: https://docs.easybuild.io/version-specific/supported-software/#meep The .eb files would build an old version Meep-1.4.3-intel-2020a.eb from an obsolete source, or old version Meep-1.6.0-intel-2018a-Python-2.7.14.eb with Python 2.7 :-( The current release of Meep is 1.26: https://github.com/NanoComp/meep/releases and installation instructions are in https://meep.readthedocs.io/en/latest/Installation/ Question: Has anyone looked at writing an .eb file for a recent version of Meep with modern compilers and Python3? Thanks, Ole -- Ole Holm Nielsen PhD, Senior HPC Officer Department of Physics, Technical University of Denmark
[easybuild] RE: EasyBuild 5.0 Working Group Meeting
And yes, I forgot an important detail: We will be using the EB conf call Zoom for this - so https://umu.zoom.us/j/561463243 From: easybuild-requ...@lists.ugent.be On Behalf Of Simon Branford Sent: 02 May 2023 18:16 To: easybuild@lists.ugent.be Subject: [easybuild] EasyBuild 5.0 Working Group Meeting Hi all, During the recent EasyBuild User Meeting (https://easybuild.io/eum23), I presented on the plans for EasyBuild 5.0 (https://easybuild.io/eum23/#easybuild5). To work towards this, we are forming a working group for developing EasyBuild 5.0. The working group will meet on the first Wednesday of each month for the next few weeks. This means that the first meeting for this working group is at 14:00 CEST (https://time.is/CEST) tomorrow (Wednesday 3rd May). Regards, Simon
[easybuild] EasyBuild 5.0 Working Group Meeting
Hi all, During the recent EasyBuild User Meeting (https://easybuild.io/eum23), I presented on the plans for EasyBuild 5.0 (https://easybuild.io/eum23/#easybuild5). To work towards this, we are forming a working group for developing EasyBuild 5.0. The working group will meet on the first Wednesday of each month for the next few weeks. This means that the first meeting for this working group is at 14:00 CEST (https://time.is/CEST) tomorrow (Wednesday 3rd May). Regards, Simon
[easybuild] Seven new posts at the University of Birmingham
Dear all, Please share this with anyone you think might be interested: Join our brilliant Advanced Research Computing<https://www.birmingham.ac.uk/bear/> team at the University of Birmingham, where you will have the opportunity to work with cutting-edge technology and on innovative research projects at a world-class university. Recent successes mean we are growing and are now recruiting to 7 new posts: - Research Software Engineer - Research Infrastructure Engineer - Research Applications Specialist - Three Research Data Scientists - Research Software Assistant, a summer post for a University of Birmingham student If you are passionate about research and technology, and want to work in a dynamic, collaborative and supportive team, we would love to hear from you. Find out more here: https://blog.bham.ac.uk/bear/2023/03/27/seven-brand-new-posts-in-advanced-research-computing Many thanks, Simon -- Dr Simon Branford Deputy Leader of the Research Software Group and Principal Research Software Engineer Research Software Group, Advanced Research Computing IT Services, University of Birmingham Web: https://www.birmingham.ac.uk/bear-software Support: https://itservicedesk.bham.ac.uk/
RE: [easybuild] Install fails due to tests run despite --skip-test-cases --ignore-test-failure
Hi, Try: --skip-test-step Regards, Simon -Original Message- From: easybuild-requ...@lists.ugent.be On Behalf Of Loris Bennett Sent: 31 January 2023 11:54 To: easybuild@lists.ugent.be Subject: Re: [easybuild] Install fails due to tests run despite --skip-test-cases --ignore-test-failure Hi Sam, Sam Moors writes: > Hi Loris, > > Not sure what's going on exactly, but it makes no sense to me why you > are using both --skip-test-cases --ignore-test-failure at the same > time? You cannot ignore tests failures if the tests are skipped ;) That was just there result of incremental testing. As --ignore-test-failure didn't ignore test failure, I tried --skip-test-cases as well, which unfortunately didn't skip the test cases. Cheers, Loris > Sam > > On Tue, Jan 31, 2023 at 11:52 AM Loris Bennett > wrote: > > Hi, > > I am running > >eb GROMACS-2019.6-fosscuda-2019b.EasyBuild \ > --robot \ > --cuda-compute-capabilities=6.1,7.5 \ > --buildpath=/dev/shm \ > --tmpdir=/scratch/eb-build \ > --skip-test-cases \ > --ignore-test-failure > > but the installation fails with > >[ FAILED ] HardwareTopologyTest.HwlocExecute (35 ms) > > Why is this test still being run and the failure not ignored? > > It is a little difficult to see what is going on, because I am > running this as a Slurm job and the entire EasyBuild output ends up > as just 3 lines in the Slurm output file: > >[build@admin slurm]$ wc -l < slurm-12012527.out >3 > > :-/ > > Cheers, > > Loris > > -- > Dr. Loris Bennett (Herr/Mr) > ZEDAT, Freie Universität Berlin > -- Dr. Loris Bennett (Herr/Mr) ZEDAT, Freie Universität Berlin
[easybuild] EasyBuild conf call: Wed 20 July 2022 at 08:00 UTC (10:00 CEST)
Dear EasyBuilders, The next EasyBuild conf call is planned for Wed 20 July 2022 at 08:00 UTC (10:00 CEST). You can join the conf call via https://tiny.cc/eb_conf_call Current agenda: * overview of recent developments * Q Suggestions for additional topics are always welcome! More information on the EasyBuild conf calls is available at https://github.com/easybuilders/easybuild/wiki/Conference-calls . Regards, Simon
[easybuild] RE: next EasyBuild conf call: Wed 13 April 2022 at 15:00 UTC ((17:00 CEST)
Notes for today's conf call are available at https://github.com/easybuilders/easybuild/wiki/Conference-call-notes-20220413 Next EasyBuild conf call is planned for Wed 27 Apr 2022 (08:00 UTC, 10:00 CEST), see https://github.com/easybuilders/easybuild/wiki/Conference-calls#next-easybuild-conference-call regards, Simon From: easybuild-requ...@lists.ugent.be On Behalf Of Simon Branford Sent: 13 April 2022 08:27 To: easybuild@lists.ugent.be Subject: [easybuild] next EasyBuild conf call: Wed 13 April 2022 at 15:00 UTC ((17:00 CEST) Dear EasyBuilders, The next EasyBuild conf call is planned for Wed 13 April 2022 at 15:00 UTC (17:00 CEST). You can join the conf call via https://tiny.cc/eb_conf_call . Current agenda: * EasyBuild v4.5.4 release * overview of recent developments * Q Suggestions for additional topics are always welcome! More information on the EasyBuild conf calls is available at https://github.com/easybuilders/easybuild/wiki/Conference-calls . Regards, Simon
[easybuild] next EasyBuild conf call: Wed 13 April 2022 at 15:00 UTC ((17:00 CEST)
Dear EasyBuilders, The next EasyBuild conf call is planned for Wed 13 April 2022 at 15:00 UTC (17:00 CEST). You can join the conf call via https://tiny.cc/eb_conf_call . Current agenda: * EasyBuild v4.5.4 release * overview of recent developments * Q Suggestions for additional topics are always welcome! More information on the EasyBuild conf calls is available at https://github.com/easybuilders/easybuild/wiki/Conference-calls . Regards, Simon
[easybuild] RE: Next EasyBuild conf call: Wed July 7th at 08:00 UTC (10:00 CEST)
Notes from the conf call today are available at https://github.com/easybuilders/easybuild/wiki/Conference-call-notes-20210707 The next conf call is planned for Wed July 21st 2021 at 15:00 UTC (17:00 CEST) Regards, Simon From: easybuild-requ...@lists.ugent.be On Behalf Of Simon Branford Sent: 07 July 2021 07:17 To: easybuild@lists.ugent.be Subject: [easybuild] Next EasyBuild conf call: Wed July 7th at 08:00 UTC (10:00 CEST) Dear EasyBuilders, The next EasyBuild conf call is planned for Wed July 7th at 08:00 UTC (10:00 CEST). You can join the conf call via https://tiny.cc/eb_conf_call . Current agenda: * EasyBuild 4.4.1 released * overview of recent developments * Q As usual, suggestions for additional topics are welcome. More information on the EasyBuild conf calls is available at https://github.com/easybuilders/easybuild/wiki/Conference-calls . Regards, Simon
[easybuild] Next EasyBuild conf call: Wed July 7th at 08:00 UTC (10:00 CEST)
Dear EasyBuilders, The next EasyBuild conf call is planned for Wed July 7th at 08:00 UTC (10:00 CEST). You can join the conf call via https://tiny.cc/eb_conf_call . Current agenda: * EasyBuild 4.4.1 released * overview of recent developments * Q As usual, suggestions for additional topics are welcome. More information on the EasyBuild conf calls is available at https://github.com/easybuilders/easybuild/wiki/Conference-calls . Regards, Simon
RE: [easybuild] Build fails for OpenBLAS-0.3.12-GCC-10.2.0.eb on Intel Ice Lake processors
Hi Ole, OpenBLAS recently added IceLake detection: https://github.com/xianyi/OpenBLAS/pull/3233 This has been patched in EasyBuild for OpenBLAS 0.3.12 and 0.3.15: https://github.com/easybuilders/easybuild-easyconfigs/pull/12865 Regards, Simon -Original Message- From: easybuild-requ...@lists.ugent.be On Behalf Of ole.h.niel...@fysik.dtu.dk Sent: 28 May 2021 13:40 To: easybuild@lists.ugent.be Subject: [easybuild] Build fails for OpenBLAS-0.3.12-GCC-10.2.0.eb on Intel Ice Lake processors Hi, I'm building our software stack on a new Intel Ice Lake server (Xeon Gold 6342 CPU @ 2.80GHz 24 cores dual-socket) running AlmaLinux 8.4 (RHEL 8.4 clone). So this is bleeding-edge CPU and OS :-) The OpenBLAS-0.3.12-GCC-10.2.0.eb build fails: $ eb OpenBLAS-0.3.12-GCC-10.2.0.eb == Temporary log file in case of crash /tmp/eb-2c6j9qyj/easybuild-qhl_uje4.log == found valid index for /home/modules/software/EasyBuild/4.3.4/easybuild/easyconfigs, so using it... == found valid index for /home/modules/software/EasyBuild/4.3.4/easybuild/easyconfigs, so using it... == processing EasyBuild easyconfig /home/modules/software/EasyBuild/4.3.4/easybuild/easyconfigs/o/OpenBLAS/OpenBLAS-0.3.12-GCC-10.2.0.eb == building and installing OpenBLAS/0.3.12-GCC-10.2.0... == fetching files... == creating build dir, resetting environment... == unpacking... == patching... == preparing... == configuring... == building... == FAILED: Installation ended unsuccessfully (build directory: /dev/shm/OpenBLAS/0.3.12/GCC-10.2.0): build failed (first 300 chars): cmd " make -j 48 libs netlib shared BINARY='64' CC='gcc' FC='gfortran' MAKE_NB_JOBS='-1' USE_OPENMP='1' USE_THREAD='1' CFLAGS='-O2 -ftree-vectorize -march=native -fno-math-errno' " exited with exit code 2 and output: getarch_2nd.c: In function main: getarch_2nd.c:14:35: error: SGEMM_DEFAULT_U (took 1 sec) == Results of the build can be found in the log file(s) /tmp/eb-2c6j9qyj/easybuild-OpenBLAS-0.3.12-20210528.142832.FCqTY.log ERROR: Build of /home/modules/software/EasyBuild/4.3.4/easybuild/easyconfigs/o/OpenBLAS/OpenBLAS-0.3.12-GCC-10.2.0.eb failed (err: 'build failed (first 300 chars): cmd " make -j 48 libs netlib shared BINARY=\'64\' CC=\'gcc\' FC=\'gfortran\' MAKE_NB_JOBS=\'-1\' USE_OPENMP=\'1\' USE_THREAD=\'1\' CFLAGS=\'-O2 -ftree-vectorize -march=native -fno-math-errno\' " exited with exit code 2 and output:\ngetarch_2nd.c: In function main:\ngetarch_2nd.c:14:35: error: SGEMM_DEFAULT_U') The EB log file ends with: make: *** [Makefile.prebuild:70: getarch_2nd] Error 1 Makefile:154: *** OpenBLAS: Detecting CPU failed. Please set TARGET explicitly, e.g. make TARGET=your_cpu_target. Please read README for the detail.. Stop. (at easybuild/tools/run.py:537 in parse_cmd_output) == 2021-05-28 14:28:34,190 filetools.py:1810 INFO Removing lock /home/modules/software/.locks/_home_modules_software_OpenBLAS_0.3.12-GCC-10.2.0.lock... == 2021-05-28 14:28:34,191 filetools.py:347 INFO Path /home/modules/software/.locks/_home_modules_software_OpenBLAS_0.3.12-GCC-10.2.0.lock successfully removed. == 2021-05-28 14:28:34,191 filetools.py:1814 INFO Lock removed: /home/modules/software/.locks/_home_modules_software_OpenBLAS_0.3.12-GCC-10.2.0.lock == 2021-05-28 14:28:34,191 easyblock.py:3414 WARNING build failed (first 300 chars): cmd " make -j 48 libs netlib shared BINARY='64' CC='gcc' FC='gfortran' MAKE_NB_JOBS='-1' USE_OPENMP='1' USE_THREAD='1' CFLAGS='-O2 -ftree-vectorize -march=native -fno-math-errno' " exited with exit code 2 and output: getarch_2nd.c: In function main: getarch_2nd.c:14:35: error: SGEMM_DEFAULT_U == 2021-05-28 14:28:34,192 easyblock.py:298 INFO Closing log for application name OpenBLAS version 0.3.12 Question: How can I tell OpenBLAS that we have an Intel Ice Lake CPU? It seems that OpenBLAS doesn't know about Ice Lake nor Cascade Lake :-( https://github.com/xianyi/OpenBLAS/blob/develop/TargetList.txt Thanks, Ole -- Ole Holm Nielsen PhD, Senior HPC Officer Department of Physics, Technical University of Denmark, Fysikvej Building 309, DK-2800 Kongens Lyngby, Denmark E-mail: ole.h.niel...@fysik.dtu.dk Homepage: http://dcwww.fysik.dtu.dk/~ohnielse/ Mobile: (+45) 5180 1620
