bzr tests fail on OpenBSD 4.4/amd64
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Bazaar |
Confirmed
|
Medium
|
Unassigned |
Bug Description
From: Toni Mueller <email address hidden>
I tried to run the self-test suite for bzr-1.10 on OpenBSD 4.4/amd64,
but encountered a number of problems that you might be able to help me
with.
1. A large number (>> 20 in any case) of self-tests failed. It is very
important to me that these bugs be fixed. I don't know how to do it,
but want to help with it (see below).
2. I had to terminate the test run after a few hundred due to / running
full.
3. It seems to be impossible to run the test suite in the background,
with no terminal. Trying to do this:
$ nohup python2.5 ./bzr selftest --strict 2>&1 &
simply stalled my test run (it displays "Stopped" on the xterm on which
I invoked the command).
I'd like to send in a more detailed report, using 'script' to record
the output, but need to find ways to not clutter /tmp first.
proved to be impossible because the test run simply stalled. I may be
missing something, however.
Please help me run the test suite, and I'll ship you the results.
I've re-tried, and got the results that you find attached. I didn't
check whether all tests were actually performed, but simply ship
everything that the tests yieled, to you. The test run (probably) ended
when Python (2.5.2p4) segfaulted. I have the core lying around, so if
you want me to do some surgery on it, just ask for it (I don't really
know what to do). I created the "...cpio.." archive using "pax -x
sv4cpio". Rolling a tarball was impossible because of the 100 char
pathname limit in the tar archive format.
Changed in bzr: | |
importance: | Low → Medium |
status: | New → Confirmed |
tags: |
added: selftest removed: test |
tags: | added: check-for-breezy |
tags: | removed: check-for-breezy |
contents of tmp after test failure