[CI] Only run quick tests by default.

Well, specifying the variable globally does not seem to work...

added 1 commit

• f1675ad8 - [CI] Only run quick tests by default.

Compare with previous version

added 1 commit

• b76eefbe - [CI] Only run quick tests by default.

Compare with previous version

Hmm.

Running with gitlab-runner 10.9.0~beta.539.g4223dae8 (4223dae8)
  on hd-2c-8g-1h c87abe34
slurm: job 876 allocated on node slave01.parcomp, available resources: 4 hyperthreads (2 cores) , 8192 MiB RAM , estimated start time: 29 May 18 18:42 CEST (in 0s)
Using Docker executor with image duneci/base:9 ...
Pulling docker image duneci/base:9 ...
Using docker image sha256:75dd38e7a4f7106d849876473307c1cf170d357454afdfb83cbc89bdad182bf8 for duneci/base:9 ...
[...]

When I pull, I get

joe@epic:~$ docker pull duneci/base:9
9: Pulling from duneci/base
cc1a78bfd46b: Already exists 
a940f0c8264e: Pull complete 
[...]
6b8203da6c17: Pull complete 
Digest: sha256:6e2bea0aa5a7b0c7517ef4dc658a4d33589fc56df2ccd55655568718bef5e80a
Status: Downloaded newer image for duneci/base:9

@smuething Is it possible that our compute server and the Heidelberg CI server are seeing different registries?

Currently, the image is at 0b9d43f5b5e048456eb9ffae04169b17c53706fe50d8336d8372b74e4db068e1 on that node, so it seems like it is updating...

Right, not sure what is causing the different hashes, but the ineffectiveness of DUNECI_TEST_LABELS was due to a misspelled variable name, joe/dune-docker!2

I am unsure of how per-job and global variables are supposed to interact, see https://gitlab.com/gitlab-org/gitlab-runner/issues/3320.

I'll prepare something that assumes they are merged (which is the currently observed behavior).

added 1 commit

• fc0803b0 - [CI] Only run quick tests by default.

Compare with previous version

merged

mentioned in commit f780797a

mentioned in merge request !496 (closed)

@joe:

You can always merge them at YAML-level:

variables: &global
  GLOBAL_VAR: set

job:
  variables:
    <<: *global
    JOB_VAR: set