Hoogle test suite fails in container environment about hoogle HOT 8 CLOSED

There are ways to run the tests that don't need internet access. Unfortunately the cabal test support doesn't seem to be able to pass arguments to the executable, as far as I could tell? I guess I can add checking an environment variable to find out I am under a non-internet VM? Any suggestions?

from hoogle.

I believe that these options could be used to pass flags to the test executables during cabal test:

--test-options=TEMPLATES give extra options to test executables (name
                         templates can use $pkgid, $compiler, $os, $arch,
                         $test-suite)
--test-option=TEMPLATE   give extra option to test executables (no need to
                         quote options containing spaces, name template can
                         use $pkgid, $compiler, $os, $arch, $test-suite)

Alternatively, the test suite could be split into two (or more) executables, and then we run only those executables that don't need Internet access during cabal test. We've used that option with good success in the dns library.

from hoogle.

It seems like --test-option= is the best approach. Any suggestions on what is easy to integrate on your side?

Given that hoogle-test is really just a 3 line program that calls the real hoogle, and I'm somewhat bitter that I can't just declare my test suite to be hoogle test (e.g. the normal binary with a command line), I'd rather stay away from adding more test binaries.

from hoogle.

How about calling the test program with --no-net to disable net work access? I don't feel strongly about the name of tha flag, though. Any choice is fine.

from hoogle.

I'll add a --no-net flag. Given the spate of Hoogle releases to fix .cabal issues, and my plans for some real upcoming changes, I'll probably leave this a few weeks. Shout if you think it should be more important.

from hoogle.

I've added the feature with --no-net flag. I'll close the bug once it's released on Hackage.

from hoogle.

Thank you for your help!

from hoogle.

Fixed in 4.2.27 - let me know if you have any issues with it. I really appreciate the help, testing and notifications I get from the NixOS packagers (and all the packagers in general) - it helps ensure my packages are "right" in all the ways it's easy to forget when just releasing to Hackage.

from hoogle.