On Fri, Nov 13, 2015 at 03:35:24PM +0100, Samuel Thibault wrote: > Ok, so it's actually litl_print from litl-tools which went crazy, thus > reassigning. > > To explain a bit: litl_print read a trace file > (pbuilder1_eztrace_log_rank_1, 570 bytes long), and writes a dump of the > trace (testlog.0.txt). The dump (ascii format) is supposed to be bigger > than the trace (binary format), but not *that* bigger :) > > So I guess somehow the read loop got it wrong while reading the trace. > I couldn't reproduce the issue, even with parallel=64 on a 24-core > system (the testsuite is not supposed to run in parallel anyway), but > the code is quite simple, so perhaps I can just proofread it and submit > patches for tests.
ok, I just remember about this, but things did not went well anyway.
mattia@profitbricks-build1-amd64 ../eztrace-1.1/build-mpich/test/automake % lh
testlog0.txt
-rw-r--r-- 1 1111 1111 8.9G Nov 22 08:01 testlog0.txt
mattia@profitbricks-build1-amd64 ../eztrace-1.1/build-mpich/test/automake %
tail testlog0.txt
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 140194795173632 Reg 0 0
0 %
https://jenkins.debian.net/view/reproducible/job/reproducible_builder_amd64_17/8171/console
and the build stuck there (actually the file is growing...)
I don't think this is supposed to happen, isn't it?
If the build wasn't creating such a file I could keep it running and do
live tests, but this :\
--
regards,
Mattia Rizzolo
GPG Key: 66AE 2B4A FCCF 3F52 DA18 4D18 4B04 3FCD B944 4540 .''`.
more about me: http://mapreri.org : :' :
Launchpad user: https://launchpad.net/~mapreri `. `'`
Debian QA page: https://qa.debian.org/developer.php?login=mattia `-
signature.asc
Description: PGP signature
