Conversation
| ); | ||
| if !execution.success { | ||
| let setup_hint = if phase == "baseline" { | ||
| " A fresh parallel worktree has no existing build directory; use \ |
There was a problem hiding this comment.
Every baseline failure returns
this error
*** No errors detected
Traceback (most recent call last):
File "/tmp/bcore-mutation-workers-KSJzCG/worker-0/./build/test/functional/test_runner.py", line 962, in <module>
main()
File "/tmp/bcore-mutation-workers-KSJzCG/worker-0/./build/test/functional/test_runner.py", line 464, in main
os.makedirs(tmpdir)
File "/home/ubuntu/.pyenv/versions/3.10.14/lib/python3.10/os.py", line 225, in makedirs
mkdir(name, mode)
FileExistsError: [Errno 17] File exists: '/tmp/test_runner_₿_🏃_20260817_212053'
Error: InvalidInput("baseline command failed in worker 0. A fresh parallel worktree has no existing build directory; use --setup-command if the test command does not configure it.")
analysis command had --setup-command, the error message is misleading
bcore-mutation analyze --sqlite mutation.db --run-id=2 --parallel 2 --file-path="src/net_processing.cpp" --setup-command 'cmake -B build && cmake --build build -j4 --target bitcoind test_bitcoin' -c 'cmake --build build -j4 --target bitcoind test_bitcoin && ./build/bin/test_bitcoin --run_test=denialofservice_tests,peerman_tests,net_tests,txdownload_tests && ./build/test/functional/test_runner.py --failfast p2p_handshake.py p2p_leak.py p2p_sendtxrcncl.py p2p_tx_download.py p2p_blocksonly.py p2p_addrv2_relay.py p2p_node_network_limited.py'
the actual error was from test_runner , got the error after the analysis had run for about 50 minutes
|
Not sure if i am testing this right But i generated mutants for verack message and then started analysis with this command Observation both workers were visibly running I could see them in the process list and the build directories growing. Then, roughly 45 minutes in,output stopped and never resumed. From the terminal I had no way to tell whether the build was still progressing, the baseline was running, a mutant was executing normally, or something had deadlocked. All four states look identical: no output. While looking at /proc from a second shell the two in-flight mutants had:
I think it makes sense to me now that i would experience more timeouts I stopped the run at ~100 minutes with zero mutant results recorded. Maybe we can add a periodic [worker N] mutant 53, 12m elapsed i am still testing using verack I’ll see how long this it takes probably more than 4 hours |
|
This time, I only had 2 mutants. |
No description provided.