John,
I'm still finding my way round the new layout/organization of where
Patchy puts the output and test results, however it is not clear
sometimes what is failing, while I can just run reject patchy and say
'where' in the cycle it fails (make, make test etc.). It does help the
devs if I can be a bit more specific.
So in today's case:
I run ./test-patchy.py as normal..
--snip--
..
Trying issue 2801
Found patch:
2801,/home/jlowe/lilypond-extra/patches/issue6498077_5001.diff,Patch:
Approximates cross-staff slurs in VerticalAxisGroup vertical-skylines.
Fetching, cloning, compiling master.
(UTC) Begin LilyPond compile, previous commit at
6ce800445921f6f32eeb60bfbf7acf1cdba2f9c1
Success: No new commits in master
Git revision has not changed but checksum of test baseline has, must rebuild.
Success: ./autogen.sh --noconfigure
Success: /tmp/lilypond-autobuild/configure --disable-optimising
Success: nice make clean
Success: nice make -j7 CPU_COUNT=7
Success: nice make test-baseline -j7 CPU_COUNT=7
Issue 2801: Patch: Approximates cross-staff slurs in VerticalAxisGroup
vertical-skylines.
Issue 2801: Testing patch issue6498077_5001_diff
Success: git apply --index
/home/jlowe/lilypond-extra/patches/issue6498077_5001.diff
Success: ./autogen.sh --noconfigure
Success: /tmp/lilypond-autobuild/configure
--disable-optimising
Success: nice make clean
Success: nice make -j7 CPU_COUNT=7
*** FAILED BUILD ***
nice make check -j7 CPU_COUNT=7
Previous good commit: 6ce800445921f6f32eeb60bfbf7acf1cdba2f9c1
Current broken commit: 6ce800445921f6f32eeb60bfbf7acf1cdba2f9c1
Error: issue 2801: Problem encountered
Traceback (most recent call last):
File "/home/jlowe/lilypond-extra/patches/projecthosting_patches.py",
line 275, in do_check
results_url = autoCompile.test_issue (issue_id, patch)
File "/home/jlowe/lilypond-extra/patches/compile_lilypond_test/__init__.py",
line 273, in test_issue
self.build (patch_test=True, issue_id=issue_id)
File "/home/jlowe/lilypond-extra/patches/compile_lilypond_test/__init__.py",
line 315, in build
issue_id)
File "/home/jlowe/lilypond-extra/patches/compile_lilypond_test/__init__.py",
line 266, in runner
raise FailedCommand ("Failed runner: %s\nSee the log file %s" %
(command, this_logfilename))
FailedCommand: Failed runner: nice make check -j7 CPU_COUNT=7
See the log file log-2801-nice-make-check--j7-CPU_COUNT=7.txt
Issue 2801: Cleaning up
Success: nice make test-clean
Success: nice make clean
Issue 2801: Done.
--snip--
So I locate 'log-2801-nice-make-check--j7-CPU_COUNT=7.txt' in
/tmp/lilypond-log/.. and get
--snip--
more log-2801-nice-make-check--j7-CPU_COUNT\=7.txt
For tracking crashes: use
grep sourcefilename `grep -L systems.texi out/lybook-testdb/*/*log|sed s
/log/ly/g`
make --no-builtin-rules -C input/regression out=test local-test
make[1]: Entering directory `/tmp/build-lilypond-autobuild/input/regression'
mkdir -p ./out-test
touch ./out-test/dummy.dep
echo '*' > ./out-test/.gitignore
... [lots of logs]
etc.
... [lots of logs]
"/tmp/build-lilypond-autobuild/
out/lybook-testdb/snippet-names-892580628.ly"
Child returned 1
Error ignored by lilylib
Error trapped by lilypond-book
Please see /tmp/build-lilypond-autobuild/out/lybook-testdb/snippet-names-8925806
28.log
... etc.
... [end of log]
--snip--
Now if I look for
'/tmp/build-lilypond-autobuild/out/lybook-testdb/snippet-names-8925806
28.log' it doesn't exist or rather because there is a make clean the
dir '/tmp/build-lilypond-autobuild/out/..' doesn't exist.
However there is one in
/tmp/show-2801
--snip--
jlowe@jlowe26vm /tmp/lilypond-log$ more
/tmp/show-2801/out/lybook-testdb/snippet-names-892580628.log
GNU LilyPond 2.17.2
Forking into jobs: (30244 30243 30242 30241 30240 30239 30238)
job 5 terminated with signal: 6
fatal error: Children (5) exited with errors.
jlowe@jlowe26vm /tmp/lilypond-log$
--snip--
ok so far so good. Doesn't give me much but onwards and upwards.
If I look in the *.ly file corresponding to the log I get this:
--snip--
jlowe@jlowe26vm /tmp/show-2801/out$ more
/tmp/show-2801/out/lybook-testdb/snippet-names-892580628.ly
snippet-map-892580628.ly
84/lily-0f7c4871.ly
aa/lily-4858d0b7.ly
0f/lily-cdc1d94e.ly
8b/lily-ee7f7e54.ly
53/lily-64dfb2d0.ly
b2/lily-1922a761.ly
de/lily-4483657e.ly
3c/lily-14a6ed53.ly
ae/lily-838f2675.ly
... [lots more lines like this]
b0/lily-7821c23e.ly
68/lily-12d29b6a.ly
dc/lily-5d81e32b.ly
8a/lily-3250e012.ly
jlowe@jlowe26vm /tmp/show-2801/out$
--snip--
Now I can find all of those *.ly files but which one can I assume is
the problematic one of this list? The first one or the second one or
could it be any in between. That is does the list get appended to
before each test?
This used to be a bit easier IIRC to find the offending file, but that
may be me out of Patchy practice.
James
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
