Hi Olivier, Maybe this helps. You can run build in debug mode in travis. I usually just make a private repo with a minimum script to run that said tests. Then you can ssh into the build. But this doesn't work in windows type build.
One other workaround I can think of is to just send the output file somewhere. When you run your travis job from your own repo, you can set the environment variable yourself. You can put secrets there in the environment in your repo's Travis settings (not in the repo, because the repo is public, I assume). For example, in the past I have tried to put my docker credentials to push the built image and have it sent to docker hub with all necessary build output inside, so I can look it up later. If you just need the output, maybe sending the files over ssh/rsync will do. Regards, -- Rizky Maulana Nugraha Kartoza ri...@kartoza.com On Mon, Jun 29, 2020 at 10:06 PM Olivier Dalang <olivier.dal...@gmail.com> wrote: > Dear list, > > I'm struggling a little bit with tests using QgsMultiRenderChecker. > > 1/ Running the tests *on Windows*, I get some small rendering differences > with fonts that make tests fail. I'm getting the warnings below, both with > the font installed in my system or not. It seems to load the font with a > different size (20.1429 instead of 20) and as normal instead of bold, which > would explain why the test fail. Any idea why this happens, and how to fix > it ? > > > ..\src\core\qgsfontutils.cpp(311) : (QgsFontUtils::getStandardTestFont) > [1372ms] Inexact font match - consider installing the QGIS Vera Sans font. > > ..\src\core\qgsfontutils.cpp(312) : (QgsFontUtils::getStandardTestFont) [0ms] > Requested: QGIS Vera Sans,20,-1,5,75,0,0,0,0,0,Bold > > ..\src\core\qgsfontutils.cpp(314) : (QgsFontUtils::getStandardTestFont) [2ms] > Replaced: QGIS Vera Sans,20.1429,47,5,75,0,0,0,0 > > 2/ The QgsLayoutChecker tests outputs some HTML view of the failing tests, > allowing for a nice comparison of expected vs rendered images. When I run > the tests locally, I can redirect the output to a report.html file, then > see it in the browser (rather hacky, as all the test output goes in the > file, so it's not at all a proper html file, but it works). > Is it possible to somehow retrieve these results *from Travis *runs ? > That would be very helpful to workaround 1/. > > Thanks !! > > Olivier > > > _______________________________________________ > QGIS-Developer mailing list > QGIS-Developer@lists.osgeo.org > List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer > Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer
_______________________________________________ QGIS-Developer mailing list QGIS-Developer@lists.osgeo.org List info: https://lists.osgeo.org/mailman/listinfo/qgis-developer Unsubscribe: https://lists.osgeo.org/mailman/listinfo/qgis-developer