On 25/05/2022 22.54, Paul Gevers wrote:
Please consider making your test suite much less intense. Looking at
Upstream comes with a rather exhaustive test matrix ...
I'm now running a smaller subset of it and in a more fine grained way to
make it easier to decide which parts to skip as well.
The OpenMP parts were even slower than on my machine ... so far I hadn't
seen invididual tests time out in ctest. Synchronizing between 56
threads seems to be a hard job ;-)
On arm64 and ppc64el your tests seem to tmpfail. I am *suspecting*
that is because they run out of diskspace. All our arm64 and ppc64el
With the more fine grained testing I've tried to free disk space at the
end of the smaller test chinks, not sure it that was successful.
For now, I have put libthrust on our rejectlist for those three
architectures and I just flushed the amd64 queue because there were
Once the backlog is cleared, it would be nice to reenable libthrust,
probably starting with amd64, to see whether I managed to get it down to
an acceptable size.
Hmm, a first test for -4 on amd64 has already finished (so the
blacklisting did not work?), mostly telling me 'SKIP test name may not
contain / character' (that should be checked by lintian). Preparing -5
now ...
The tests are temporarily all on flaky to avoid introducing regressions
while testing the tests ;-)
The tests are all superficial, since we can't run (but only compile) the
most relevant part of the testsuite: the cuda tests.
Andreas
PS: src:cub needs to be trimmed down as well, that has done some 12 h
runs on ci-worker13, too ... not touching that before we have resolved
src:libthrust
