openorienteering-mapper FTBFS

Niko Tyni ntyni at debian.org
Tue Jul 7 05:57:13 UTC 2020


On Sun, Jul 05, 2020 at 10:45:45AM +0200, Graham Inggs wrote:

> Any ideas why openorienteering-mapper FTBFS on the reproducible build
> infrastructure [1]?  It builds fine for me locally and on the buildds
> [2].  It's also had some recent binNMUs.

> 2: WARNING: PolygonTest::testJoins(simple joins) testdata
> data/PolygonTest1-sample.png could not be located!
> 2:    Loc: [./3rd-party/cove/tests/PolygonTest.cpp(75)]
> 2: QWARN  : PolygonTest::testJoins(simple joins) QFSFileEngine::open:
> No file name specified
> 2: FAIL!  : PolygonTest::testJoins(simple joins)
> 'sampleImage.load(QFINDTESTDATA(imageFile))' returned FALSE. ()
> 2:    Loc: [./3rd-party/cove/tests/PolygonTest.cpp(75)]

My guess is that this is an instance of

 https://tests.reproducible-builds.org/debian/issues/unstable/ftbfs_due_to_f-file-prefix-map_issue.html

  An example of failure related to this are programs that expect
  __FILE__ to expand to some absolute path, but instead finding themselves
  a relative one.

as QFINDTESTDATA() uses __FILE__:

 https://sources.debian.org/src/qtbase-opensource-src/5.14.2+dfsg-4/src/testlib/qtestcase.h/?hl=215#L216

   #ifdef QT_TESTCASE_BUILDDIR
   # define QFINDTESTDATA(basepath)\
       QTest::qFindTestData(basepath, __FILE__, __LINE__, QT_TESTCASE_BUILDDIR)
   #else
   # define QFINDTESTDATA(basepath)\
       QTest::qFindTestData(basepath, __FILE__, __LINE__)
   #endif

-- 
Niko Tyni       ntyni at debian.org


More information about the rb-general mailing list