#1140597 stimfit: autopkgtest failure

Package:
src:stimfit
Source:
src:stimfit
Submitter:
Adrian Bunk
Date:
2026-06-23 13:17:01 UTC
Severity:
normal
#1140597#5
Date:
2026-06-23 08:22:04 UTC
From:
To:
https://tracker.debian.org/pkg/stimfit

Issues preventing migration:
∙ ∙ Autopkgtest for stimfit/0.17.1-1: amd64: Failed ♻, arm64: Failed ♻, i386: Failed ♻, loong64: Failed ♻, ppc64el: Failed ♻, s390x: Failed ♻


...
166s autopkgtest [05:24:10]: test stimfit-help: [-----------------------
167s 05:24:11: Error: Unable to initialize GTK+, is DISPLAY set properly?
167s autopkgtest [05:24:11]: test stimfit-help: -----------------------]
167s autopkgtest [05:24:11]: test stimfit-help:  - - - - - - - - - - results - - - - - - - - - -
167s stimfit-help         FAIL stderr: 05:24:11: Error: Unable to initialize GTK+, is DISPLAY set properly?
...
167s autopkgtest [05:24:11]: @@@@@@@@@@@@@@@@@@@@ summary
167s python3-stfio-import PASS (superficial)
167s stimfit-help         FAIL stderr: 05:24:11: Error: Unable to initialize GTK+, is DISPLAY set properly?
#1140597#10
Date:
2026-06-23 08:32:45 UTC
From:
To:
Dear Adrian,

this bug has already been fixed in 0.17.1-2, which is waiting for sponsorship on Debian mentors.

https://mentors.debian.net/package/stimfit/

The failing test tried to run `stimfit --help`, which initializes the wx/GTK application and therefore fails in the headless ci.debian.net environment.

In 0.17.1-2 I replaced that test with a headless-safe test. The `python3-stfio` import autopkgtest remains unchanged.


Best wishes,
Christoph
#1140597#15
Date:
2026-06-23 08:32:45 UTC
From:
To:
Dear Adrian,

this bug has already been fixed in 0.17.1-2, which is waiting for sponsorship on Debian mentors.

https://mentors.debian.net/package/stimfit/

The failing test tried to run `stimfit --help`, which initializes the wx/GTK application and therefore fails in the headless ci.debian.net environment.

In 0.17.1-2 I replaced that test with a headless-safe test. The `python3-stfio` import autopkgtest remains unchanged.


Best wishes,
Christoph
#1140597#20
Date:
2026-06-23 13:14:55 UTC
From:
To:
This could be fixed by running inside xvfb-run.

The bigger problem is that "stimfit -h" returns 255,
which is likely the reason why "|| true" was added,
which would make the test pass despite certain errors.

If "stimfit -h" would return 0, then
  xvfb-run -a stimfit -h
should work as autopkgtest.[1]

cu
Adrian

[1] needs a xvfb test dependency, and might also need an allow-stderr
    autopkgtest restriction