Open pieterdavid opened 5 years ago
The "details" say "not found", so I guess the test has been run so many days ago that the outcome has been cleaned up by the system. Is there a way of forcing again the test?
Indeed. I think it's possible to retrigger the build in jenkins, but this one is not ready for tests yet anyway (and the test configs will need to change if we want some coverage for the "full run2" sample).
Summary:
cms.Task
hacks)updateremotes
), silence GCC7 warning about non-virtual destructors for virtual base classesSCRAM_ARCH
to CentOS7, since much of the computing resources is migrating or will do so soon (e.g. lxbatch, grid sites, the cp3 partition on slurm)Still to do: