Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove pin for PrgEng-gnu as CPE has moved to a new version. #26442

Merged
merged 2 commits into from
Dec 21, 2024

Conversation

tzinsky
Copy link
Collaborator

@tzinsky tzinsky commented Dec 20, 2024

No description provided.

@tzinsky tzinsky requested a review from jhh67 December 20, 2024 17:10
Signed-off-by: Vassily Litvinov <[email protected]>
@vasslitvinov vasslitvinov merged commit 66ff17e into chapel-lang:main Dec 21, 2024
8 checks passed
@vasslitvinov
Copy link
Member

vasslitvinov commented Dec 21, 2024

@tzinsky @riftEmber and others -- with my change, we now have "module swap" for both "gcc" and "gcc-native". I intentionally put both of them there because I did not know what machines this file is used for. The machine hosting the test configuration hpe-cray-ex-performance-test-perf.hpe-cray-ex.ofi and our GPU configurations has "gcc-native", so the "gcc" line is not needed there. Fortunately, it is harmless: "module swap" reports an error, yet the job continues. Here is what we got in the job hpe-cray-ex-performance-test-perf.hpe-cray-ex.ofi/169 today:

# I do not know what to think about the following. -Vass
Lmod is automatically replacing "cce/19.0.0-rc3" with "gcc-native/14.2".

# This is the error due to 'module swap' on gcc. -Vass
Lmod has detected the following error: Swap failed: "gcc" is not loaded.

# The following confirms correct operation. -Vass.
The following have been reloaded with a version change:
  1) gcc-native/14.2 => gcc-native/12.3

Ideally, we should be able to compile with the default gcc version and remove "module swap" for both "gcc" and "gcc-native", making the above discussion moot.

P.S. The test failures that this PR was intended to resolve have, indeed, resolved.

@riftEmber
Copy link
Member

riftEmber commented Dec 23, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants