On Fri, 1 May 2020 at 16:04, René-Luc D'Hont wrote:
>
> Hi Nyall,
>
> I have opened an issue about it and tried to fix it with no clue.
>
> https://github.com/qgis/QGIS/issues/35973
> https://github.com/qgis/QGIS/pull/35984
>
> The segfault appears randomly since I tried to fix a regression and ad
Hi Nyall,
I have opened an issue about it and tried to fix it with no clue.
https://github.com/qgis/QGIS/issues/35973
https://github.com/qgis/QGIS/pull/35984
The segfault appears randomly since I tried to fix a regression and added
more PyQgsServerWMSGetPrint tests.
Before deactivate the PyQgsS
On Fri, 1 May 2020 at 15:04, Alessandro Pasotti wrote:
>
> On Fri, May 1, 2020 at 3:35 AM Nyall Dawson wrote:
> >
> > Hi list,
> >
> > Just a heads up that unless someone fixes the recently flaky
> > PyQgsServerWMSGetPrint test I'll be adding this test to the travis
> > blacklist shortly.
> >
> >
On Fri, May 1, 2020 at 3:35 AM Nyall Dawson wrote:
>
> Hi list,
>
> Just a heads up that unless someone fixes the recently flaky
> PyQgsServerWMSGetPrint test I'll be adding this test to the travis
> blacklist shortly.
>
> This test is randomly crashing with no clues -- see e.g.
> https://cdash.or
Hi list,
Just a heads up that unless someone fixes the recently flaky
PyQgsServerWMSGetPrint test I'll be adding this test to the travis
blacklist shortly.
This test is randomly crashing with no clues -- see e.g.
https://cdash.orfeo-toolbox.org/testDetails.php?test=18996963&build=40255
I've spen
