Front page | perl.qa |
Postings from April 2017
On 04/09/2017 11:33 AM, James E Keenan wrote:
> An updated printout of the CPAN River is available here:
>
> https://gist.github.com/jkeenan/a7670b2ffe1ffe3e8d8cbdbc2b3dd721
>
Using this data we can conduct a fourth round of testing.
Today I began a fourth round of testing. I am doing so to reflect
(a) the generation of a new CPAN river file, 'cpan.river.20170409.csv';
and (b) an understanding of why 'PERL_USE_UNSAFE_INC' must be set to '0'
before using the 'cpanm' build against Perl 5 blead.
1. The new input file is, as mentioned above, 'cpan.river.20170409.csv'.
2. Because the input file is now in CSV format, I had to modify the
first program to handle that. I now use 'csv-get-upriver-distros.pl'.
I will fetch the first 1000 distributions from the input file.
#####
perl csv-get-upriver-distros.pl 1000
#####
This program excludes distributions which are shipped with the Perl 5
core as well as certain previously identified as hard-to-test
distributions like mod_perl and Term::ReadLine::Perl.
3. Built and installed an updated perl5 blead for testing:
#####
$ ./bin/perl -v | head -2 | tail -1
This is perl 5, version 26, subversion 0 (v5.26.0
(v5.25.11-50-gb57dd50)) built for x86_64-linux
#####
... and installed Miyagawa's up-to-the-minute cpanm against that perl.
#####
$ ./bin/perl -MApp::cpanminus -E 'say $App::cpanminus::VERSION;'
1.7043
#####
4. Adapting nudge from KENTNL, I worked from a just-updated local
minicpan repository.
#####
$ minicpan
$ cd ~/testing/blead
$ export PERL_USE_UNSAFE_INC=0
$ date > startcpanm
$ cat /home/jkeenan/learn/perl/cpan-river/fourth-round-top-1000.txt | \
xargs bin/cpanm --mirror ~/minicpan --verbose; date > endcpanm
#####
############################################################################
5. Copied and renamed the 'cpanm' build.log to 20170409-1000-build.log.gz.
6. grepped out relevant lines from the build log:
#####
$ zgrep FAIL 20170409-1000-build.log.gz | grep -v 'Result: FAIL' | \
sed -e 's/^-> //' > 20170409-1000-fails.txt
#####
7. Used a revised version of 'order-battle.pl' to record the order in
which various modules *first* appeared in the 'fails' file and the
total number of times each module was cited. Results are attached as
'order-of-battle-20170409.txt'.
What is the "order of battle"? It's an approximation of the order in
which, as of today, we need to get new CPAN releases out so that
down-river distros are no longer failing due to failures in their
upstream dependencies.
This approach is useful for me because I only have a laptop to work
with. YMMV.
Thank you very much.
Jim Keenan
Thread Previous
|
Thread Next