You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The cabal binary passes a relative log pathname to Distribution.Simple.Test.stubMain via stdin, stubMain runs the tests, then Test.stubWriteLog fails to write the results because the relative path is no longer valid. Cabal fails to read the log and gives the "no parse" error as below.
In this example, tests contains the setCurrentDirectory call, but it could just as easily be within a returned TestInstance.
module Fail where
import System.Directory
import Distribution.TestSuite
tests :: IO [Test]
tests = do
setCurrentDirectory ".."
return []
$ cabal test
Running 1 test suites...
Test suite fail: RUNNING...
cabal: Prelude.read: no parse
$ cabal -V
cabal-install version 1.16.0.2
using version 1.16.0.3 of the Cabal library
The text was updated successfully, but these errors were encountered:
The cabal binary passes a relative log pathname to
Distribution.Simple.Test.stubMain
via stdin,stubMain
runs the tests, thenTest.stubWriteLog
fails to write the results because the relative path is no longer valid. Cabal fails to read the log and gives the "no parse" error as below.In this example,
tests
contains thesetCurrentDirectory
call, but it could just as easily be within a returnedTestInstance
.$ cabal test
Running 1 test suites...
Test suite fail: RUNNING...
cabal: Prelude.read: no parse
$ cabal -V
cabal-install version 1.16.0.2
using version 1.16.0.3 of the Cabal library
The text was updated successfully, but these errors were encountered: