Skip to content

Conversation

@Flamefire
Copy link
Contributor

@Flamefire Flamefire commented Jul 8, 2021

@Flamefire Flamefire force-pushed the cmake_improvements branch 3 times, most recently from 9448a47 to 9f790a0 Compare July 15, 2021 07:10
@Flamefire Flamefire force-pushed the cmake_improvements branch from f0ccda1 to fcd7b12 Compare July 15, 2021 09:52
@Flamefire
Copy link
Contributor Author

Test report by @Flamefire
SUCCESS
Build succeeded for 75 out of 75 (75 easyconfigs in total)
taurusi5027.taurus.hrsk.tu-dresden.de - Linux RHEL 7.9, x86_64, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (haswell), Python 2.7.5
See https://gist.github.com/78d27869af1428bc1412cbb637ccfde8 for a full test report.

@Flamefire
Copy link
Contributor Author

@Micket Rebuild the whole lot that I still can build (i.e. Intel 2017 doesn't work due to licenses)
As you can see from the commits it also reenables building certain older ECs that are currently broken, at least in some environments.

Would be great if this could be merged soon so future ECs can use the new style/don't C&P old stuff.

@Micket
Copy link
Contributor

Micket commented Sep 6, 2021

This is all caught up now, so a rebase is the next step?

@Flamefire Flamefire force-pushed the cmake_improvements branch 3 times, most recently from 7d6a298 to 1b7cf23 Compare September 14, 2021 10:29
@Flamefire
Copy link
Contributor Author

Test report by @Flamefire
FAILED
Build succeeded for 87 out of 90 (54 easyconfigs in total)
taurusi6276.taurus.hrsk.tu-dresden.de - Linux RHEL 7.9, x86_64, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (haswell), Python 2.7.5
See https://gist.github.com/037a07ddfd6fcee3270b2da9b4029bb5 for a full test report.

@boegel
Copy link
Member

boegel commented Sep 15, 2021

@Flamefire Do you think it makes sense to add a check in the easyconfigs test suite to avoid that new easyconfigs re-introduce the use of -DCMAKE_BUILD_TYPE=Release?

This is still a huge PR to get merged btw, but we'll try...

@Flamefire
Copy link
Contributor Author

I'll add a CI check soonish.

And yeah, it's big: 64 ECs :/ But the changes are trivial after fleshing out the other PRs.

@Flamefire
Copy link
Contributor Author

Test report by @Flamefire
FAILED
Build succeeded for 53 out of 54 (54 easyconfigs in total)
taurusi5570.taurus.hrsk.tu-dresden.de - Linux RHEL 7.9, x86_64, Intel(R) Xeon(R) CPU E5-2680 v3 @ 2.50GHz (haswell), Python 2.7.5
See https://gist.github.com/1e4b408fb98f93c81dbb48dc4398a42b for a full test report.

@Flamefire
Copy link
Contributor Author

CI check added by #14008

@Flamefire
Copy link
Contributor Author

Racon failure fixed with #14010

@boegel boegel modified the milestones: 4.5.1, release after 4.5.1 Dec 8, 2021
@boegel boegel modified the milestones: 4.5.2, release after 4.5.2 Jan 18, 2022
@boegel boegel modified the milestones: 4.5.3, release after 4.5.3 Feb 9, 2022
@boegel boegel removed this from the next release (4.5.4) milestone Mar 28, 2022
@boegel boegel added this to the release after 4.5.4 milestone Mar 28, 2022
@boegel boegel modified the milestones: 4.5.5, release after 4.5.5 Jun 4, 2022
@Flamefire Flamefire force-pushed the cmake_improvements branch from 38414b7 to d896c10 Compare July 26, 2022 08:07
@Flamefire
Copy link
Contributor Author

Rebased to resolve conflicts and remove the changes done in the other PRs.

@boegel
Copy link
Member

boegel commented Sep 10, 2022

Test report by @boegel
SUCCESS
Build succeeded for 12 out of 12 (12 easyconfigs in total)
node2678.swalot.os - Linux RHEL 8.4, x86_64, Intel(R) Xeon(R) CPU E5-2660 v3 @ 2.60GHz (haswell), Python 3.6.8
See https://gist.github.com/d768fb474640994004a7f2b44e1fa119 for a full test report.

Copy link
Member

@boegel boegel left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I gave this a thorough review, and submitted a test report for a bunch of recent easyconfigs touched in this PR, looks good to go, thanks for your efforts here @Flamefire!

As next step, we should add a check to the easyconfigs test suite to avoid that easyconfigs being contributed still specify -DCMAKE_BUILD_TYPE in configopts, or set build_type to Release, or enable separate_build_dir...

@boegel boegel changed the title Remove superflous -DCMAKE_BUILD_TYPE remove superflous -DCMAKE_BUILD_TYPE=Release, use of 'build_type = Release', or enabling separate_build_dir from easyconfigs using CMakeMake easyblock Sep 10, 2022
@boegel
Copy link
Member

boegel commented Sep 10, 2022

Going in, thanks @Flamefire!

@boegel boegel merged commit 516ba24 into easybuilders:develop Sep 10, 2022
@Flamefire
Copy link
Contributor Author

boegel changed the title Remove superflous -DCMAKE_BUILD_TYPE remove superflous -DCMAKE_BUILD_TYPE=Release, use of 'build_type = Release', or enabling separate_build_dir from easyconfigs using CMakeMake easyblock

I usually use plain sentences to describe changes which yields the PR title, i.e. it starts with uppercase. What is the reason for the change to lowercase and do you want that for future PRs?

@Flamefire Flamefire deleted the cmake_improvements branch September 11, 2022 08:43
@boegel
Copy link
Member

boegel commented Sep 11, 2022

@Flamefire It's mainly because the PR titles go straight into the release notes, where they're in a list, see https://docs.easybuild.io/en/latest/Release_notes.html

I often reword PR titles if I feel they're not clear enough, or to make PRs easier to find, to avoid having to do that when composing the release notes...

@boegel boegel removed the bug fix label Sep 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants