Skip to content
Snippets Groups Projects
Commit 269f19ea authored by Ujwal Kundur's avatar Ujwal Kundur
Browse files

Integration Test Scenario #4

spack still concretizies spack.yaml with oneapi compiler instead
of gcc. This test builds with --no-cache option to rule out spack.yaml
caching.
dev.Dockerfile has a CACHE_BUST arg for this purpose but it seems to be
set after copying spack.yaml not before. So if this works, move
CACHE_BUST before COPY instruction copying spack.
parent ea94fe9b
No related branches found
No related tags found
1 merge request!306OneAPI Integration Testing
...@@ -224,6 +224,7 @@ oneapi_jug_dev:default: ...@@ -224,6 +224,7 @@ oneapi_jug_dev:default:
- docker build -t ${CI_REGISTRY_IMAGE}/${BUILD_IMAGE}:${INTERNAL_TAG} - docker build -t ${CI_REGISTRY_IMAGE}/${BUILD_IMAGE}:${INTERNAL_TAG}
-f containers/oneapi/onedev.Dockerfile -f containers/oneapi/onedev.Dockerfile
containers/oneapi containers/oneapi
--no-cache
- !reference [.build, script] - !reference [.build, script]
......
...@@ -42,5 +42,5 @@ spack: ...@@ -42,5 +42,5 @@ spack:
unify: true unify: true
packages: packages:
all: all:
compiler: [intel] compiler: [gcc]
view: /usr/local view: /usr/local
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment