Em 22/01/2018 17:25, Andreas Koenig escreveu:
On Sun, 21 Jan 2018 22:18:12 +0100, Slaven Rezic <sla...@rezic.de> said:
>> 6. Not every CPAN contributor writes tests that allow execution of
>> tests in parallel, or even to run in parallel with another perl
>> executing the same tests at the same time.
> This would be an interesting thing to have, but I always thought that
> the specification should go into the distribution's META.* files (wasn't
> there already a proposal?). And CPAN.pm may inject changes into the META
> information via distroprefs files (at least this is possible for
> dependency information).
My smokers nearly always run several instances of different perls
simultaneously on the same server. Other smokers, e.g. Ether's, have
HARNESS_OPTIONS set up for parallel runs.
The number of issues caused by that seem to be negligible, so I always
wrote bug reports like these:
https://rt.cpan.org/Ticket/Display.html?id=98239
https://rt.cpan.org/Ticket/Display.html?id=85336
https://rt.cpan.org/Ticket/Display.html?id=85303
https://rt.cpan.org/Ticket/Display.html?id=85301
https://rt.cpan.org/Ticket/Display.html?id=84333
I don't find more than these 5, so either I was bad in identifying the
cases or the issue is not very wide-spread.
Interesting, because I didn't enabled it either but still caught far
more than 5 distros that were executing at the same time... but were
just hanging around, usually at the same steps. Sometimes I killed on
(CRTL+C), the other starts running again, sometimes I had to kill both
processes.
It could be something specific to OpenBSD (that indeeds shows processes
waiting for something on tty for no aparent reason) but I don't have
that to show that. I guess I need indeed a watchdog to help me out.
I also argued in the past that asking for metadata should be avoided
because:
- should the need really exist, we should first collect data what kinds
of problems we have and how they can be dealt with besides metadata
How could we collect such data?
Regards,
Alceu
