Bugzilla – Bug 715
let ./test.py not to store traces in /tmp/unchecked-traces in multiuser environment
Last modified: 2009-10-12 17:03:01 UTC
Created attachment 623 [details] proposed change Say, 2 users are running ./test.py simultaneously. Both of them are trying to write their tests to /tmp/unchecked-traces, causing random tests crashes. This is usually not an issue for desktop runs, but really a problem for servers with many users. So, I suggest to move TMP_TRACES_DIR and TMP_OUTPUT_DIR to the ns-3 build directory (like "build/optimized/tmp").
The number of temporary files was getting annoyingly large, and it was harder than expected to find output files for debugging, so I reworked this area completely. test.py now stores its temporary files "locally" an not in /tmp. It creates a "testpy-output" directory and saves temporary files under the directory "testpy-output" with a timestamp for a name, like, 2009-10-12-20-54-26-CUT/ This is year, month, day, hour, minute, second Coordinated Universal Time. Normally, test.py creates dozens of little temporary files and trace files as it runs. If you don't select the --retain option, these temporary files are removed by deleting the directory above. If you "./test.py --retain" then test.py will not delete the temporary files. e.g. ./test.py -r or ./test.py --retain You can then wander around in the (currently) 373 temporary files generated during a complete test run and try and figure out what went wrong.
Fixed changeset 00d7fe69d024