Source: notepadqq Version: 2.0.0~beta1-4.1 Severity: normal Hi,
I noticed that the notepaddqq gui autopkgtest failed after I uploaded uchardet: https://ci.debian.net/packages/n/notepadqq/testing/amd64/64046605/ It passed when I retried it: https://ci.debian.net/packages/n/notepadqq/testing/amd64/64097502/ So I think the test is flaky (rather than something I have done). If you look at the logs for amd64, there are some random failures (no logs though sadly): https://ci.debian.net/packages/n/notepadqq/unstable/amd64/ --- I don't know what the bug is, but this part is suspicious to me: > # Run nqq on a fake display > (QTWEBENGINE_CHROMIUM_FLAGS=--disable-gpu xvfb-run -a notepadqq &> ${k}) & > > # Give it some time to generate warnings > sleep 5 > > # Close it > kill -QUIT %1 > wait %1 2>/dev/null This is a non-interactive bash script, so job control is disabled. bash still allows you to use the %1 syntax, but critically background tasks are not placed in process groups. This means that the `kill -QUIT %1` line only kills the xvfb-run process, and does not kill notepadqq like it would do if you ran this in an interactive shell. That seems possibly unintentional to me? James
