testNoLostParticles failing for non-knl vectorization on KNL about ls1-mardyn HOT 7 CLOSED

probably a missing
-fp-model precise
in the common_icc.in file. Tried adding it.

from ls1-mardyn.

Seems to work. Do you want me to cherry-pick and open a PR?

from ls1-mardyn.

sounds like a good idea

from ls1-mardyn.

if you run everything for the knl, it might probably make sense to run some of the configurations with the gcc compiler.

from ls1-mardyn.

I thought it could be useful to have the jobs platform-agnostic, so we would use the vectorization mode as node labels and let jenkins figure out where to run everything. So that'd be

• KNL-cluster: AOS, SOA, SSE, AVX, AVX2, KNL_G_S, KNL_MASK
• atsccs11: AOS, SOA, SSE, AVX, AVX2 (plus SKX_MASK and SKX_G_S through sde)
• openshift cloud (in the future): AOS, SOA, SSE

At the moment, we're running everything on KNL with icc and everything on atsccs11 with gcc, but would of course add some randomness if we go with my proposed setup... Maybe we add the compiler as another axis with just one configuration each? That way we could also easily test clang, which is listed as a supported compiler. I take we don't have a Licenses for the more esoteric ones (PGI, Cray, NEC SX, IBM XL)?

from ls1-mardyn.

yep, I thought so, too. Clang is also a possibility.
I theory I anyways want to put most of it in our kubernetes cloud. That way we have well defined setups and could test everything nicely.
But, for now you may do as you suggested ;)
Fyi: we can also do all the sde stuff on the cloud

from ls1-mardyn.

Ok, then I'll look into that.

Fyi: we can also do all the sde stuff on the cloud

I'll have to check how reliably i can tell jenkins what nodes to prefer for what jobs, we wouldn't want to run into a situation where a node that supports something natively sits idle while the cloud is spinning its wheels with sde.

from ls1-mardyn.