On Sat, Mar 11, 2017 at 08:17:18AM +0000, Ghislain Vaillant wrote: > A (potential) fix for this would be to try out testing with pytest-xvfb > (which I have recently packaged, so only in unstable for now), instead of > calling xvfb-run manually. > > pytest-xvfb is supposed to provide a more robust setup for tests requiring > xvfb. I have had successful results with packages such as > src:spyder-unittest. After the freeze (since pytest-xvfb will not be > available in Stretch), I intend to switch both src:python-qtpy and > src:python-qtawesome to using pytest-xvfb for testing. > > We'll see whether this addresses the problem you reported. Are you happy > with this plan?
It depends. This is a FTBFS problem, so it should be fixed in stretch. So, before trying what you describe I would ask Release Managers if they would allow pytest-xvfb in stretch as a way to fix this bug. BTW: The ri-li package used to fail 95% of the time in my autobuilders and also "often" in reproducible builds autobuilders. Somebody found a way to make this failure rate to decrease dramatically, maybe it may give you a hint. Thanks.
