Re: Address output-distance problems: (issue 563730043 by address@hidden)

[Han-Wen Nienhuys]

Easiest fix is probably to change disable the test for
output-distance, by backing out the change GNUmakefile.in

I'm curious about the exact procedure for building here. I've tested
this and previous patch in various configurations.



On Thu, Mar 12, 2020 at 12:49 AM David Kastrup <address@hidden> wrote:
>
> address@hidden writes:
>
> > going to fast-track this so the testing can continue.
> >
> > https://codereview.appspot.com/563730043/
>
> Patchy refuses.  Staging is blocked.  Since there is no point in
> admitting a patch that will stop master from building, I am removing
> from staging.  I will retry to make very sure that nothing I did at the
> time on my computer is at fault, though.
>
> 23:27:18 (UTC) Begin LilyPond compile, previous commit at       
> 93c179860f0edf55722e7157ef2024c30b33a47d
> 23:27:22 Merged staging, now at:        
> 93c179860f0edf55722e7157ef2024c30b33a47d
> 23:27:23        Success:                ./autogen.sh --noconfigure
> 23:27:35        Success:                /tmp/lilypond-autobuild/configure 
> --enable-checking
> 23:27:38        Success:                nice make clean
> 23:31:42        Success:                nice make -j9 CPU_COUNT=9
> 23:31:45 *** FAILED BUILD ***
>         nice make test -j9 CPU_COUNT=9
>         Previous good commit:   ee197383f4af552ed433c496617cb5ffe2a28dcf
>         Current broken commit:  93c179860f0edf55722e7157ef2024c30b33a47d
> 23:31:45 *** FAILED STEP ***
>         merge from staging
>         Failed runner: nice make test -j9 CPU_COUNT=9
> See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
> 23:31:45 Traceback (most recent call last):
>   File 
> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 528, in handle_staging
>     self.build (issue_id=issue_id)
>   File 
> "/usr/local/tmp/lilypond-extra/patches/compile_lilypond_test/__init__.py", 
> line 328, in build
>     issue_id)
>   File 
> "/usr/local/tmp/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 test -j9 CPU_COUNT=9
> See the log file log-staging-nice-make-test--j9-CPU_COUNT=9.txt
>
> .
> ----------------------------------------------------------------------
> Ran 1 test in 0.003s
>
> OK
> GNU LilyPond 2.21.0
> cp: cannot stat '19.sub{-*.signature,.ly,-1.eps,.log,.profile}': No such file 
> or directory
> test results in  ./out/test-output-distance
> Traceback (most recent call last):
>   File "/tmp/lilypond-autobuild/scripts/build/output-distance.py", line 1561, 
> in <module>
>     main ()
>   File "/tmp/lilypond-autobuild/scripts/build/output-distance.py", line 1546, 
> in main
>     run_tests ()
>   File "/tmp/lilypond-autobuild/scripts/build/output-distance.py", line 1495, 
> in run_tests
>     test_compare_tree_pairs ()
>   File "/tmp/lilypond-autobuild/scripts/build/output-distance.py", line 1330, 
> in test_compare_tree_pairs
>     system ('cp 19.sub{-*.signature,.ly,-1.eps,.log,.profile} dir1/subdir/')
>   File "/tmp/lilypond-autobuild/scripts/build/output-distance.py", line 1304, 
> in system
>     assert stat == 0, (stat, x)
> AssertionError: (256, 'cp 19.sub{-*.signature,.ly,-1.eps,.log,.profile} 
> dir1/subdir/')
> make[1]: *** [/tmp/lilypond-autobuild/./scripts/build/GNUmakefile:19: 
> local-test] Error 1
> make: *** [/tmp/lilypond-autobuild/GNUmakefile.in:328: test] Error 2
>
>
> --
> David Kastrup



-- 
Han-Wen Nienhuys - address@hidden - http://www.xs4all.nl/~hanwen