Increase test timeout for Perl v5.42.0 tests - #279
Conversation
casparvl
changed the title
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
@casparvl Forcing to run the tests single-core oesn't seem to work consistently? Maybe we need to set It's certainly relevant for See also Perl/perl5@ec8902c I would set it to edit: if we still see test failures, then perhaps we've hitting a deadlock situation, that's exactly why a timeout was added to |
|
bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
| if self.name == "Perl" and self.version == "5.42.0": | ||
| self.cfg['pretestopts'] = "export PERL_TEST_TIME_OUT_FACTOR=10 && " + self.cfg['pretestopts'] | ||
| if hasattr(self, 'parallel'): | ||
| self.cfg.parallel = 1 |
There was a problem hiding this comment.
@casparvl With $PERL_TEST_TIME_OUT_FACTOR, there should be no need anymore to enforce single-core?
There was a problem hiding this comment.
There isn't, I just didn't bother to take it out yet. But... it seems to not have helped anyway :(
|
FYI: I wasn't able to reproduce this with |
|
@casparvl Rather than using |
Co-authored-by: Kenneth Hoste <kenneth.hoste@ugent.be>
|
Ok, let's also try another build like this. Local testing is actually also slow, the test suite takes 20 minutes. And note that the tests run serially anyway. I'm not sure how disabling the parallelization ever helped @bedroge ... There is a compile step to the tests, that might be executed in parallel with bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
From what I remember it runs multiple tests in parallel, https://github.com/easybuilders/easybuild-easyblocks/blob/develop/easybuild/easyblocks/p/perl.py#L131 also seems to confirm that? |
|
Ah, my bad, I didn't modify that parameter, just added the Anyway, interactive run was succesful with the timeout increase. Let me see if I can actually rerun in parallel. I now indeed see a few more perl processes, I think. Not 16 for sure, but maybe 3-4, and really only one seems to be active at any given time... I'm guessing maybe the degree of parallelism in the test suite is limited. Also, our biggest bottleneck is |
|
Lets get some more datapoints on this: bot: build repo:eessi.io-2026.06-software instance:eessi-bot-mc-aws for:arch=x86_64/amd/zen2 |
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
New job on instance
|
|
@casparvl name of hook + PR title need a fix before we deploy this 🙊 |
|
What do you mean? I just like confusing the hell out of people :D |
casparvl
changed the title
|
3/4 success, just waiting for @casparvl Can you remove the test |
|
That makes me realize: we'll have to be careful with deploying this, since the tarballs for the successful test builds will also be picked up... :-/ |
3 participants
No description provided.