Hey, I have no real idea why we see only a problem in the chat_server test. It is a problem in the shutdown... I can mark it as superficial so the failing test does not block the CI. But is only a workaround. Can you enable the verbose flag by hand, so we can see what function triggers this segmentation fault?
Test-Command: XDG_CONFIG_HOME="$AUTOPKGTEST_TMP" onionshare-cli -v --local- only --chat --auto-stop-timer 2 Or can you give me the the back trace of the segmentation fault? On my system, I don't see the segmentation fault, so hard to taggle down. Properly it is https://github.com/onionshare/onionshare/issues/1408#issuecomment-908150292 and it is harmless. But without verbose log I cannot be sure. > The autopkgtests from onionshare are flaky and have been failing roughly > half the time over the last couple of weeks. Does that mean, that it run successfully before? Regards, hefee -- On Freitag, 21. April 2023 20:53:03 CEST Sebastian Ramacher wrote: > Source: onionshare > Version: 2.6-1 > Severity: serious > > > https://ci.debian.net/data/autopkgtest/testing/amd64/o/onionshare/32901091/l > og.gz > > Give this address and private key to the recipient: > http://127.0.0.1:17632 > Private key: E2GOT5LTUTP3OAMRCRXO4GSH6VKJEUOXZQUC336SRKAHTTT5OVSA > > Press Ctrl+C to stop the server > Stopped because auto-stop timer ran out > Segmentation fault > autopkgtest [22:20:10]: test chat_server: -----------------------] > autopkgtest [22:20:10]: test chat_server: - - - - - - - - - - results - - - > - - - - - - - chat_server FAIL non-zero exit status 139
signature.asc
Description: This is a digitally signed message part.
