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

Extends GitLab CI scripts to run different compiler versions #174

Closed
wants to merge 4 commits into from

Conversation

SimeonEhrig
Copy link
Member

@SimeonEhrig SimeonEhrig commented Jun 4, 2020

Address the Issue #171. It runs over different GCC, Clang, Boost and CUDA versions.

Different versions will be build in single job (and runner), because a single test configuration needs just a few time for building and running and the overhead of pulling the docker image would becomes huge. However, the configuration is flexible. It is also possible to divide a heavy job and more lightweight jobs. For example, the GCC is divided in 3 jobs. Otherwise, they would run in a time out.

Issue #173 is also solved in this PR.

- iterate over: GCC/Clang versions, Boost version and Alpaka ACC versions
@SimeonEhrig SimeonEhrig force-pushed the multiVersionCI branch 3 times, most recently from 1e10753 to 3d9fd78 Compare June 8, 2020 11:43
@SimeonEhrig SimeonEhrig changed the title [WIP] Extends GitLab CI scripts to run different compiler versions Extends GitLab CI scripts to run different compiler versions Jun 8, 2020
@SimeonEhrig
Copy link
Member Author

@psychocoderHPC
Ready for merge and blowing up the CI infrastructure ;-)

@sbastrakov
Copy link
Member

@SimeonEhrig I can also merge cupla stuff. One question: is it meant to go to master or dev branch? (your PR is currently to master)

@SimeonEhrig
Copy link
Member Author

The PR should merged in the master, because my last commit with changes for the CI was also merged in master. But I'm not sure if the last RP was not already merged in the wrong branch. Anyway, this PR does not changes the application code itself, so it should be not a problem to rebase the dev branch and use the new infrastructure in both branches.

@psychocoderHPC
Copy link
Member

I will close this PR that it is not merged by accident. The PR is opened against the master, we never merge directly into the master.

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