Ubuntu
slic3r-prusa package

slic3r-prusa autopkgtest flaky

Bug #2031340 reported by Gunnar Hjalmarsson
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
fontconfig (Ubuntu)
Fix Released
Undecided
Unassigned
gmp (Ubuntu)
Fix Released
Undecided
Unassigned
nlopt (Ubuntu)
Fix Released
Undecided
Unassigned
slic3r-prusa (Ubuntu)
New
Undecided
Unassigned

Bug Description

autopkgtest was added to slic3r-prusa as late as last April. They have never let version 2.6.0 of slic3r-prusa migrate to Debian testing, and seemingly need more work. slic3r-prusa 2.6.0+dfsg-2 was uploaded to unstable on July 27 but hasn't migrated to testing yet due to failing autopkgtest.

In Ubuntu the flaky tests currently prevent fontconfig and nlopt (in addition to slic3r-prusa itself) from migrating to mantic-release. Probably some kind of hint is motivated.

Related branches

~vpa1977/ubuntu/+source/slic3r-prusa:verbose_tests
git-ubuntu import: Pending requested
Diff: 42 lines (+10/-2)
3 files modified
debian/changelog (+6/-0)
debian/control (+2/-1)
debian/rules (+2/-1)
Gunnar Hjalmarsson (gunnarhj)
no longer affects: glib2.0 (Ubuntu)
Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

It looks like the slic3r-prusa tests are less inclined to pass when fontconfig 2.14.2 is loaded into the test environment. I can't tell why/how, though.

fontconfig 2.14.2 is now in Debian testing, so I suppose the slic3r-prusa maintainers will attend to it sooner or later.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Suddenly it run the ppc64el test successfully with fontconfig as trigger (and with the -release version of slic3r-prusa). So marking the fontconfig task "fixed".

Changed in fontconfig (Ubuntu):
status: New → Fix Released
Revision history for this message
Zixing Liu (liushuyu-011) wrote (last edit ):

I have re-run that test, and the issue indeed exists.

There is a race condition inside the GUI program where if you quit the program too quickly, there is a chance that the update function will be unable to shut down cleanly due to its need to show a dialogue window to the user. This will cause the program to crash.

It was just that I was lucky, and the runner was busy at the time, so the script was delayed and the program did not crash.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

Part of your luck was that it tested with slic3r-prusa 2.5.2 from mantic-release.

Maybe it's good that slic3r-prusa 2.6.0 keeps being stuck in -proposed (it's not in Debian testing either). Don't know about nlopt.

Revision history for this message
Gunnar Hjalmarsson (gunnarhj) wrote :

It also run the ppc64el and s390x tests successfully with gmp and nlopt as triggers and with the -release version of slic3r-prusa.

Changed in gmp (Ubuntu):
status: New → Fix Released
Changed in nlopt (Ubuntu):
status: New → Fix Released
Revision history for this message
Mitchell Dzurick (mitchdz) wrote (last edit ):

Just adding that I tried rebuilding the package and tests are still failing 2.6.1+dfsg-3

https://launchpad.net/~mitchdz/+archive/ubuntu/slic3r-prusa-mantic/+builds?build_text=&build_state=all

Revision history for this message
Vladimir Petko (vpa1977) wrote :

I have added a build watch script to output to the terminal, but s390x still failed:
https://launchpad.net/~vpa1977/+archive/ubuntu/plusone/+sourcepub/15186846/+listing-archive-extra
Looks like one of the tests is getting stuck, I will try to debug it.

Revision history for this message
Vladimir Petko (vpa1977) wrote (last edit ):

The tests use boost background worker and are prone to race conditions. Increasing verbosity of the test runner provides a band-aid by shifting the test timings.

Revision history for this message
Vladimir Petko (vpa1977) wrote :
Revision history for this message
Vladimir Petko (vpa1977) wrote (last edit ):

Submitted:

https://github.com/prusa3d/PrusaSlicer/issues/11429

While I have a MP that hides the problem by making tests verbose, I do not want to proceed with it unless absolutely necessary as this is a quite breaking bug for the GUI.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.