Menu

#1564 Test failures (lilypond export options)

None
closed
nobody
None
1
2021-06-27
2018-12-27
No

Hi!

I tried enabled build-time tests for 18.12 to be used as part of the Debian package builds. Currently all the lilypond exports fail with the following message:

FAIL! : TestLilypondExport::testExamples(stormy-riders) Compared values are not the same
Actual (QString(line)) : "#(set-global-staff-size 32)\n"
Expected (QString(expectedLine)): "#(set-global-staff-size 18)\n"
Loc: [/<<pkgbuilddir>>/test/lilypond/lilypond_export_test.cpp(63)]</pkgbuilddir>

The tests try to set the staff size for export but, since in the restricted build environment HOME is not writable, setting the value fails. The failure to write the settings should probably result in the test failing at that point and not later.

(I will set HOME to a writable temporary directory for the purpose of running the tests.)

Discussion

  • Ted Felix

    Ted Felix - 2021-06-27
    • status: open --> closed
     
  • Ted Felix

    Ted Felix - 2021-06-27

    Looks like we updated this at some point. It's working fine now. Closing. Please re-open if this is still a problem.

     
  • Ted Felix

    Ted Felix - 2021-06-27

    I take that back. Yeah, we need to write to HOME. We will be doing that now for three of the test cases. QSettings::setValue() doesn't tell us when it fails, so we can't detect this problem earlier. Let me know if this is still a problem and if you have a suggested fix. Making HOME writable sounds like a good fix. What are the downsides?

     

Log in to post a comment.