[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
GUB test file naming
From: |
Graham Percival |
Subject: |
GUB test file naming |
Date: |
Sat, 11 Jul 2009 00:16:33 -0700 |
User-agent: |
Mutt/1.5.18 (2008-05-17) |
When I try:
make -f lilypond.make unlocked-test-export
(either manually, or as part of "make lilypond"), the build often
ends with an error message:
----
uploads/lilypond-2.13.4-HEAD.test-output.tar.bz2
Traceback (most recent call last):
File "test-lily/rsync-test.py", line 200, in <module>
main ()
File "test-lily/rsync-test.py", line 194, in main
compare_test_info (options)
File "test-lily/rsync-test.py", line 155, in compare_test_info
assert 0
AssertionError
make: *** [unlocked-test-export] Error 1
----
Now, it's no mystery why this happens; the python file contains:
----
def compare_test_info (options):
outputs = glob.glob (options.upload_dir +
'/lilypond-*.test-output*')
current_version = tuple (map (int, options.version))
current_tuple = (current_version, options.build)
versions_found = []
current_test_output = ''
for f in outputs:
m = re.search ('lilypond-([.0-9]+)-([0-9]+).test-output.tar.bz2', f)
if not m:
printf (f)
assert 0
----
The file: uploads/lilypond-2.13.4-HEAD.test-output.tar.bz2
clearly doesn't match the "m = re.search (..." line. What I can't
understand is *why* the script is searching for such a string...
or alternately, *why* does GUB give the test output a filename
that doesn't match what the later script is expecting?
Cheers,
- Graham
PS if you're wondering how I managed to make any releases, the
answer is that after some combination of makes, renaming files,
deleting files, etc; the problem goes away. However, since I
can't figure out which step(s) fixed it, this is hardly a
permenant solution.
- GUB test file naming,
Graham Percival <=