Test suite failures about pandoc-ruby HOT 2 CLOSED

Hi @Apteryks!

The first one appears to be the custom pandoc path tripping up the test, which expects just the executable name.

The conversion-related test failures appear to be due to the version of pandoc the tests are running with, version 2.7.3. The conversion test files work with pandoc version 2.9.2+ (though might need updates for the recently-released 2.10). You can see in the last change for the test files, c0b68df, that the changes were the same strings causing these test failures.

I recommend updating pandoc to the latest version. However, since these are the only failures, it looks like pandoc is working properly and these failures are just artifacts of the testing configuration, so pandoc-ruby should work fine your configuration even with the test failures.

Let me know if you run into any other issues or have any other questions related to this!

from pandoc-ruby.

Hi @xwmx, thanks for the prompt response! I've added a note in the package definition so that the current disabling of some tests can be cleaned up after the Guix ghc-pandoc package gets upgraded to 2.9.2+.

Thanks!

from pandoc-ruby.