Source: con-duct Version: 0.17.0-1 Severity: serious Hi Maintainer
con-duct's autopkgtests are failing on riscv64 [1]. I've copied what I hope is the relevant part of the log below. Regards Graham [1] https://ci.debian.net/packages/c/con-duct/testing/riscv64/ 353s =================================== FAILURES =================================== 353s ____________________________ test_signal_int[None] _____________________________ 353s 353s temp_output_dir = '/tmp/pytest-of-debci/pytest-0/test_signal_int_None_0/' 353s fail_time = None 353s 353s @pytest.mark.parametrize("fail_time", [None, 0, 10, -1, -3.14]) 353s def test_signal_int(temp_output_dir: str, fail_time: float | None) -> None: 353s 353s wait_time = 0.3 353s proc = multiprocessing.Process( 353s target=_runner_for_signal_int, args=(temp_output_dir, fail_time) 353s ) 353s proc.start() 353s sleep(wait_time) 353s assert proc.pid is not None, "Process PID should not be None" # for mypy 353s os.kill(proc.pid, signal.SIGINT) 353s proc.join() 353s 353s # Once the command has been killed, duct should exit gracefully with exit code 0 353s > assert proc.exitcode == 0 353s E AssertionError: assert 1 == 0 353s E + where 1 = <Process name='Process-1' pid=6450 parent=5259 stopped exitcode=1>.exitcode 353s 353s test/test_execution.py:238: AssertionError
