ewxrjk/disorder

(very) intermittent queue.py failure

Closed this issue · 2 comments

--- queue ---
 starting daemon
FATAL: daemon failed to start up
Traceback (most recent call last):
  File "/home/richard/_builds/deodand/disorder/tests/dtest.py", line 335,
in run
    module.test()
  File "./queue.py", line 27, in test
    dtest.start_daemon()
  File "/home/richard/_builds/deodand/disorder/tests/dtest.py", line 245,
in start_daemon
    sys.exit(1)
SystemExit: 1
  daemon already stopped
 FAILED
FAIL: queue.py


richard@deodand:~/_builds/deodand/disorder/tests$ cat queue.log
disorderd: INFO: process ID 3865
disorderd: INFO:
PATH=/home/richard/_builds/deodand/disorder/tests:/home/richard/_builds/deodand/
disorder/clients:/home/richard/_builds/deodand/disorder/server:/usr/local/bin:/u
sr/bin:/bin:/usr/bin/X11:/usr/games:/usr/bin/:/usr/sbin/
disorderd: INFO: RLIM_NOFILE is 1024
disorderd: ERROR:
/home/richard/_builds/deodand/disorder/tests/testroot/config:26: invalid
network address
disorderd: ERROR: cannot read configuration

    26    broadcast_from 127.0.0.1 51940

...but that's probably been overwritten by subsequent tests.

Original issue reported on code.google.com by ewx...@gmail.com on 15 Jul 2009 at 8:11

Original comment by ewx...@gmail.com on 15 Jul 2009 at 8:13

  • Added labels: OpSys-All
  • Removed labels: ****
revno: 928
committer: Richard Kettlewell <rjk@greenend.org.uk>
branch nick: disorder.dev
timestamp: Sat 2009-07-18 13:43:11 +0100
message:
  Leave a bit of headroom above test port number, since we go at least
  one above it.  Almost certainly the cause of issue #36.

Original comment by ewx...@gmail.com on 18 Jul 2009 at 12:44

  • Changed state: Fixed
  • Added labels: ****
  • Removed labels: ****