Bug 820 - Bad things happen in test.py when logging is enabled
Bad things happen in test.py when logging is enabled
Status: RESOLVED FIXED
Product: ns-3
Classification: Unclassified
Component: regression
ns-3-dev
All All
: P4 normal
Assigned To: Craig Dowell
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2010-02-18 15:41 EST by Josh Pelkey
Modified: 2010-02-26 12:36 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Josh Pelkey 2010-02-18 15:41:26 EST
specifically when the examples start getting tested.  For example, I got this once:

PASS: Example csma/csma-ping
PASS: Example csma/csma-raw-ip-socket
Exception in thread Thread-1:
Traceback (most recent call last):
  File "/usr/lib/python2.6/threading.py", line 525, in __bootstrap_inner
    self.run()
  File "./test.py", line 869, in run
    job.cwd, options.valgrind)
  File "./test.py", line 684, in run_job_synchronously
    stdout_results, stderr_results = proc.communicate()
  File "/usr/lib/python2.6/subprocess.py", line 689, in communicate
    return self._communicate(input)
  File "/usr/lib/python2.6/subprocess.py", line 1221, in _communicate
    stderr = ''.join(stderr)
MemoryErKilled


I removed logging, and everything passed.
Comment 1 Craig Dowell 2010-02-26 12:36:03 EST
changeset a4a7ded174dc