Closed sumitd2 closed 1 month ago
Yes, this test inspects the emitted warning message, which is a known source of flakiness.
libvips treats warnings more like a log rather than linking them to a particular image. sharp tries to improve this a little bit with a mutex, but you might still get the "wrong" warning when tests are run in parallel.
To make things a bit less flaky, perhaps the test could store all of the warnings received and verify at least one of them matches the expected message?
@lovell Thanks for the confirmation. You can close it from my side.
Hopefully made a bit less flaky by commit https://github.com/lovell/sharp/commit/f7ed9b7fb6a884bce4faacbbb46150d600eb4fff
I am building and testing the latest tagged version of sharp on IBM Power (ppc64le). This is the output of
npm test
:Is this test known to be flaky? Can you help me debug it? Thank you.