[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new
From: |
Knut Petersen |
Subject: |
Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?' |
Date: |
Sun, 20 Jan 2019 11:17:47 +0100 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:60.0) Gecko/20100101 Thunderbird/60.4.0 |
Hi Werner
I don't know what the difference is between the two 'make' functions
but at the moment I cannot do a full set of tests on patches.
Whatever :-) I found a problem with `output-distance.py', which I
hot-fixed in staging. Please retry!
output-distance.py ... I think my system hit the same problem tonight:
Test full lilypond build with gub on openSuSE Tumbleweed, user not gub,
gub not in /home/gub/NewGub/gub
=======================================================================================================
- gub moved from /home/gub/Newgub/gub to /home/knut/sources/gub,
- execute as user knut, all files in gub chowned to knut:users
- gub is current gperciva/gub master + pull request #53, #54, #55, #56,
#57 + openSuSE Tumbleweed fixes described earlier
- regtest/ files: ./lilypond-2.19.81-1.test-output.tar.bz2, ./ignore
CLEAN
=====
address@hidden:~/sources/gub> git clean -dfx
# After moving gub to another place, 'git clean -dfx' is not enough! we
also need:
address@hidden:~/sources/gub> rm -rf target
Build lilypond
==============
address@hidden:~/sources/gub> time make lilypond
# Succeeded after about 175 real minutes (431 minutes user, 50 minutes
system time)
address@hidden:~/sources/gub> du -sh
# Now build stable
address@hidden:~/sources/gub> time make LILYPOND_BRANCH=stable/2.20 lilypond
# Unfortunately that fails with
[...]
0.303501
/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression/instrument-name.profile
0.302414
/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-master/input/regression/completion-heads-factor.profile
0.300030 tree.gittxt
1287 below threshold
919 unchanged
invoking rm -rf
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1
mkdir
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1
mkdir
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1/v2.21.0-1
mkdir
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1/v2.19.81-1
v2.19.81-1/rest-positioning.ly ->
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1/v2.19.81-1/rest-positioning.ly
v2.21.0-1/rest-positioning.ly ->
/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1/v2.21.0-1/rest-positioning.ly
invoking gs -sDEVICE=png16m -dGraphicsAlphaBits=4 -dTextAlphaBits=4 -slilypond-datadir=v2.19.81-1/share/lilypond/current -r101 -dAutoRotatePages=/None -sOutputFile=/home/knut/sources/gub/uploads/webtest/v2.21.0-1/compare-v2.19.81-1/v2.19.81-1/rest-positioning.png -dNOSAFER -dEPSCrop -q
-dNOPAUSE v2.19.81-1/rest-positioning.eps -c quit
Error: /undefinedfilename in --file--
Operand stack:
(share/lilypond/current/fonts/otf/emmentaler-20.otf) (r)
Execution stack:
%interp_exit .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval-- --nostringval-- --nostringval-- false 1 %stopped_push 1999 1 3 %oparray_pop 1998 1 3 %oparray_pop --nostringval-- 1982 1 3 %oparray_pop 1868
1 3 %oparray_pop --nostringval-- %errorexec_pop .runexec2 --nostringval-- --nostringval-- --nostringval-- 2 %stopped_push --nostringval--
Dictionary stack:
--dict:1214/1684(ro)(G)-- --dict:0/20(G)-- --dict:82/200(L)--
Current allocation mode is local
Last OS error: No such file or directory
Current file position is 424
GPL Ghostscript 9.21: Unrecoverable error, exit code 1
Traceback (most recent call last):
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 1349, in ?
main ()
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 1346, in main
compare_tree_pairs (zip (args[0::2], args[1::2]), out,
options.threshold)
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 1061, in compare_tree_pairs
data.create_html_result_page (dest_dir, threshold)
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 1043, in create_html_result_page
link.link_files_for_html (dest_dir)
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 660, in link_files_for_html
to_compare = self.create_images (dest_dir)
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 650, in create_images
system (cmd)
File
"/home/knut/sources/gub/target/linux-64/src/lilypond-git.sv.gnu.org--lilypond.git-stable-2.20/scripts/build/output-distance.py",
line 1091, in system
assert stat == 0
AssertionError
Traceback (most recent call last):
File "test-lily/rsync-test.py", line 221, in ?
main ()
File "test-lily/rsync-test.py", line 215, in main
compare_test_info (options)
File "test-lily/rsync-test.py", line 186, in compare_test_info
compare_test_tarballs (options, versions_found[-3:])
File "test-lily/rsync-test.py", line 136, in compare_test_tarballs
system (cmd)
File "test-lily/rsync-test.py", line 87, in system
raise Exception ('fail')
Exception: fail
make[3]: *** [unlocked-test-export] Fehler 1
make[3]: Leaving directory `/home/knut/sources/gub'
make[2]: *** [cached-test-export] Fehler 2
make[2]: Leaving directory `/home/knut/sources/gub'
make[1]: *** [test-export] Error 2
make[1]: Leaving directory `/home/knut/sources/gub'
make: *** [lilypond] Error 2
real 20m37,917s
user 74m5,046s
sys 6m4,173s
Bad news. But Werner wrote about an output-distance.py problem he fixed
in staging ... test staging ...
=======================================================================================================
address@hidden:~/sources/gub> time make LILYPOND_BRANCH=staging lilypond
Good news. That succeeded!
==========================
BTW: I think it's time to merge pull requests #53, #54, #55, #56 and #57.
Knut
- I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/19
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?',
Knut Petersen <=
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/20
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/21
- Message not available
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Werner LEMBERG, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', James Lowe, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', Thomas Morley, 2019/01/22
- Re: I cannot run make check since Issue 5450: relocate.cc: Introduce new command `set?', pkx166h, 2019/01/22