spawn_tests: failed: expected WIFEXITED(status) && WEXITSTATUS(status) == 0 #34975

1. 
   fanquake commented at 12:40 AM on April 1, 2026: member

   https://github.com/bitcoin/bitcoin/actions/runs/23707832716/job/69062601128?pr=34923#step:10:3349:

     3/157 Test   [#3](/bitcoin-bitcoin/3/): mptest ...............................***Failed    1.06 sec
   [ TEST ] spawn_tests.cpp:44: SpawnProcess does not run callback in child
   ./ipc/libmultiprocess/test/mp/test/spawn_tests.cpp:108: failed: expected exited; Timeout waiting for child process to exit
   stack: bf2ed1 cc4091 cc4545 d817f9 d82ba3 bf220b ee33f4b9 ee33f555
   ./ipc/libmultiprocess/test/mp/test/spawn_tests.cpp:109: failed: expected WIFEXITED(status) && WEXITSTATUS(status) == 0
   stack: bf2e03 cc4091 cc4545 d817f9 d82ba3 bf220b ee33f4b9 ee33f555
   [ FAIL ] spawn_tests.cpp:44: SpawnProcess does not run callback in child (1051610 μs)
   [ TEST ] test.cpp:124: Call FooInterface methods
   [ PASS ] test.cpp:124: Call FooInterface methods (3744 μs)
   [ TEST ] test.cpp:216: Call IPC method after client connection is closed
   [ PASS ] test.cpp:216: Call IPC method after client connection is closed (363 μs)
   [ TEST ] test.cpp:233: Calling IPC method after server connection is closed
   [ PASS ] test.cpp:233: Calling IPC method after server connection is closed (346 μs)
   [ TEST ] test.cpp:250: Calling IPC method and disconnecting during the call
   [ PASS ] test.cpp:250: Calling IPC method and disconnecting during the call (354 μs)
   [ TEST ] test.cpp:270: Calling IPC method, disconnecting and blocking during the call
   [ PASS ] test.cpp:270: Calling IPC method, disconnecting and blocking during the call (554 μs)
   [ TEST ] test.cpp:319: Make simultaneous IPC calls on single remote thread
   [ PASS ] test.cpp:319: Make simultaneous IPC calls on single remote thread (741 μs)
   6 test(s) passed 
   1 test(s) failed 
   
   

2. 
   fanquake commented at 12:40 AM on April 1, 2026: member

   cc @ryanofsky @Sjors

3. 
   ryanofsky commented at 1:56 AM on April 1, 2026: contributor

   Thanks for the report. This looks like a spurious test failure. This is from a test added in https://github.com/bitcoin-core/libmultiprocess/pull/237/changes/5205a87cd90e23f5aa2ae8503213dc90bd557bfd (https://github.com/bitcoin-core/libmultiprocess/pull/237, #34363) which has a short 1 second timeout which should be increased to be more reliable in CI.

4. maflcko added the label CI failed on Apr 1, 2026
5. 
   Sjors commented at 7:30 AM on April 1, 2026: member

   Commit ad75b147b5c3ab5eac268a1c1ced23894a8a79ba from #34727 used timeout factor for functional tests, we may need something similar for the unit tests.

6. Sjors referenced this in commit 09b0569385 on Apr 1, 2026
7. Sjors referenced this in commit ad6171d936 on Apr 1, 2026
8. 
   Sjors commented at 7:47 AM on April 1, 2026: member

   I just bumped it to 30 seconds here: https://github.com/bitcoin-core/libmultiprocess/pull/266

   Unfortunately this requires another subtree update: #34977

9. Sjors referenced this in commit dba3485c04 on Apr 1, 2026
10. fanquake added this to the milestone 31.0 on Apr 1, 2026
11. Sjors referenced this in commit 189fa1708a on Apr 3, 2026
12. Sjors referenced this in commit cc0b23fc32 on Apr 3, 2026
13. ryanofsky closed this on Apr 3, 2026

    ---

14. ryanofsky referenced this in commit 75c2a2764c on Apr 3, 2026
15. fanquake reopened this on Apr 4, 2026

    ---

16. fanquake closed this on Apr 4, 2026

    ---

Milestone
31.0