Closed carlsmedstad closed 11 months ago
Are these tests known to be flaky?
No, they are not. They run nightly and on every commit in CI.
A possible problem is that the system encoding is not set to UTF-8. If the tests fail in CI, then I will address it. Otherwise, I'm going to assume the problem is a misconfiguration with the system running the tests.
...upon further inspection, I may have another idea.
The path of the audio and video file is being inserted into the output. Since the path at which you are running the tests is so long, the path is getting wrapped. Hence, it's breaking the assertion of the test. I think the test may need to account for this situation.
Tests always have to make some assumptions, and thus far this assumption has held up. But if you take the test suite well outside of its context, then these kinds of discrepancies inevitably will appear.
Hey :wave:
I'm the maintainer of the asciidoctor-pdf package in the Arch User Repositories. Recently, I introduced running the test suite as part of the package build process and multiple users are reporting the same failing tests:
I've not been able to reproduce this on my system. Are these tests known to be flaky? I suspect something with the users environment causes the strings in the tests to be split differently, but I'm out-of-depth as to figure out what.
For now I have removed the tests from the package, but if you have any ideas on how to fix them that would be greatly appreciated. Thanks!