Another nondeterministic failure in allmydata.test.test_system.SystemTest.test_mutable #1667

Closed
opened 2012-02-09 05:25:38 +00:00 by stercor · 4 comments
stercor commented 2012-02-09 05:25:38 +00:00
Owner

Failure running 'python setup.py test'

Failure running 'python setup.py test'
tahoe-lafs added the
unknown
major
defect
1.9.1
labels 2012-02-09 05:25:38 +00:00
tahoe-lafs added this to the undecided milestone 2012-02-09 05:25:38 +00:00
stercor commented 2012-02-09 18:11:37 +00:00
Author
Owner

Attachment tahoe-nondeterministic-failure (63380 bytes) added

stdout and stderr output of Tahoe-LAFS installation.

**Attachment** tahoe-nondeterministic-failure (63380 bytes) added stdout and stderr output of Tahoe-LAFS installation.
tahoe-lafs added
minor
and removed
major
labels 2012-02-09 18:13:17 +00:00
stercor commented 2012-02-09 20:13:09 +00:00
Author
Owner

Attachment test.log (235115 bytes) added

**Attachment** test.log (235115 bytes) added
230 KiB
davidsarah commented 2012-03-31 00:13:32 +00:00
Author
Owner

tahoe-nondeterministic-failure seems to be truncated; did you stop the test at that point? If so, the information needed to diagnose what went wrong, which would have been printed later, has been lost (and there is also no useful information in test.log).

To display more output as the tests are run, use python setup.py test --rterrors. Maybe we should make that the default. As it is, there's really no way to debug this or relate it to other tickets, so marking as "cannot reproduce". Feel free to reopen if you can reproduce it.

[tahoe-nondeterministic-failure](/tahoe-lafs/trac-2024-07-25/attachments/000078ac-a102-c5ce-7307-2dc5a4ff6301) seems to be truncated; did you stop the test at that point? If so, the information needed to diagnose what went wrong, which would have been printed later, has been lost (and there is also no useful information in [test.log](/tahoe-lafs/trac-2024-07-25/attachments/000078ac-a102-c5ce-7307-324a41b34d2d)). To display more output as the tests are run, use `python setup.py test --rterrors`. Maybe we should make that the default. As it is, there's really no way to debug this or relate it to other tickets, so marking as "cannot reproduce". Feel free to reopen if you can reproduce it.
tahoe-lafs added
code-mutable
normal
cannot reproduce
and removed
unknown
minor
labels 2012-03-31 00:13:32 +00:00
davidsarah closed this issue 2012-03-31 00:13:32 +00:00
davidsarah commented 2012-03-31 00:19:19 +00:00
Author
Owner

Replying to davidsarah:

To display more output as the tests are run, use python setup.py test --rterrors. Maybe we should make that the default.

Filed as #1699.

Replying to [davidsarah](/tahoe-lafs/trac-2024-07-25/issues/1667#issuecomment-128813): > To display more output as the tests are run, use `python setup.py test --rterrors`. Maybe we should make that the default. Filed as #1699.
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: tahoe-lafs/trac-2024-07-25#1667
No description provided.