JongHyeon Hwang

Reproduced random failure for `./runtest -vdik 222` on x64 WSL2 Ubuntu 20.04 The info below is from one instance of failure where the external data comment is missing `uftrace replay...

Adding output when external-data message is misplaced between 2 functions. Test ran as `./runtest.py -dk 222` and the following was the 4th test ``` # TIMESTAMP FUNCTION 35775.262034200 | __monstartup();...

I suggest also setting the strtoull base to 10 @ L535, which parses the number before the decimal point, for consistency. Octal in a timestamp doesn't make much sense anyways....

> Test 261 fails like this: > > ``` > Traceback (most recent call last): > File "/home/namhyung/project/uftrace/tests/./runtest.py", line 941, in > results = run_single_case(name, flags, opts.split(), arg, compilers) >...

I can think of some solutions to freeing `uftrace_opts.exename` but maybe someone might have a better idea? | Idea | Notes| | --- | --- | | Add a boolean...

If you mean the temp directory created by `runtest.py` then that is preserved with `-k` option already. However, the directory is shared for the same testcase built with different compile...

Currently, the temp directory is prefixed with the name of the binary only, so if the same binary is tested for different testcases, then it becomes difficult to tell them...