Win64 CI failure in feature_versionbits_warning.py #28115

1. 
   jonatack commented at 3:39 pm on July 20, 2023: contributor

   https://cirrus-ci.com/task/6148314429652992?logs=functional_tests#L2861

    0 test  2023-07-19T19:45:37.140000Z TestFramework (ERROR): Assertion failed 
    1                                   Traceback (most recent call last):
    2                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_framework.py", line 131, in main
    3                                       self.run_test()
    4                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\feature_versionbits_warning.py", line 89, in run_test
    5                                       self.restart_node(0)
    6                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_framework.py", line 578, in restart_node
    7                                       self.stop_node(i)
    8                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_framework.py", line 564, in stop_node
    9                                       self.nodes[i].stop_node(expected_stderr, wait=wait)
   10                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_node.py", line 360, in stop_node
   11                                       self.wait_until_stopped(expected_stderr=expected_stderr)
   12                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_node.py", line 394, in wait_until_stopped
   13                                       wait_until_helper(lambda: self.is_node_stopped(expected_ret_code=expected_ret_code, **kwargs), timeout=timeout, timeout_factor=self.timeout_factor)
   14                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\util.py", line 265, in wait_until_helper
   15                                       if predicate():
   16                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_node.py", line 394, in <lambda>
   17                                       wait_until_helper(lambda: self.is_node_stopped(expected_ret_code=expected_ret_code, **kwargs), timeout=timeout, timeout_factor=self.timeout_factor)
   18                                     File "C:\Users\ContainerAdministrator\AppData\Local\Temp\cirrus-ci-build\test\functional\test_framework\test_node.py", line 374, in is_node_stopped
   19                                       assert return_code == expected_ret_code, self._node_msg(
   20                                   AssertionError: [node 0] Node returned unexpected exit code (3) vs (0) when stopping
   21 test  2023-07-19T19:45:37.140000Z TestFramework (DEBUG): Closing down network thread 
   22 test  2023-07-19T19:45:37.202000Z TestFramework (INFO): Stopping nodes 
   23 test  2023-07-19T19:45:37.202000Z TestFramework.node0 (DEBUG): Stopping node 
   

2. 
   eval-exec commented at 11:36 am on July 23, 2023: none

   AssertionError: [node 0] Node returned unexpected exit code (3) vs (0) when stopping

   Hello, I think a clue to solve this issue is to find out where the exit code (3) is returned? But I didn’t find where the exit code (3) is returned in the source code. What do you think?

3. maflcko added the label Windows on Jul 24, 2023
4. 
   hebasto commented at 12:31 pm on September 25, 2023: member

   AssertionError: [node 0] Node returned unexpected exit code (3) vs (0) when stopping

   Hello, I think a clue to solve this issue is to find out where the exit code (3) is returned? But I didn’t find where the exit code (3) is returned in the source code. What do you think?

   From Microsoft docs:

   If the Windows error reporting handler is not invoked, then abort calls _exit to terminate the process with exit code 3 and returns control to the parent process or the operating system.

5. maflcko added the label CI failed on Jan 24, 2024
6. maflcko added the label Tests on Jan 24, 2024
7. 
   maflcko commented at 9:26 am on January 24, 2024: member

   Is this still an issue with a recent version of Bitcoin Core? Closing for now, but feel free to reopen if this happens again.
8. maflcko closed this on Jan 24, 2024

   ---

Contributors
jonatack eval-exec hebasto maflcko

Labels
Windows Tests CI failed