Front page | perl.perl5.porters |
Postings from February 2023
On 2023-02-28 3:56 a.m., Darren Duncan wrote: > I say "selection" under the assumption that a tester machine wouldn't do all of > CPAN in one day, but if say it could normally get through all of CPAN in 5 days > for an individual version of Perl, it would do 1/5 against one day's blead, the > next 1/5 against the next day's blead, and so on round robin, so on the 6th day > it does the first 1/5 again with a version of blead 5 days newer. To clarify, the 1/5ths over all CPAN thing is just an example. Just as any given tester presumably doesn't test every module against every regular Perl release, especially every versioned dev release, it doesn't have to test every module against blead either. So "selection" is however a tester wants to define it. If this isn't already done by CPAN testers, something that would be logical to prioritize for more frequent testing are the modules highest up the CPAN river, the knowledge of which we AFAIK already have reliable automated gathering of, and then after those, the most popular modules, which may be a bit trickier to automate knowledge of but a reasonable approximation should be possible. So then those prioritized ones, if say there are just on the order of a few hundred say, they could be retested every time a new blead is built, eg once every 24 hours, and then the rest of CPAN arbitrarily less often, or the rest could be skipped and be it considered that just testing on the monthly dev releases is frequent enough. But there can be a lot of flexibility here and no need to be prescriptive on what gets tested or how often, only prescribe that when something is tested against blead it is done and reported in a prescribed consistent format. -- Darren DuncanThread Previous | Thread Next