Open alaendle opened 1 year ago
How did you test this @alaendle ?
It works for me on Debian Bullseye with nightly-2023-06-25:
stack test --resolver nightly-2023-06-25
or cabal with index-state 2023-06-25T07:15:04Z
and ghc from ghcup.
% cabal test -w ghc-9.6.2
Resolving dependencies...
Build profile: -w ghc-9.6.2 -O1
In order, the following will be built (use -v for more details):
- tar-conduit-0.3.2.1 (lib) (configuration changed)
- tar-conduit-0.3.2.1 (test:tests) (configuration changed)
- tar-conduit-0.3.2.1 (test:space) (configuration changed)
Configuring library for tar-conduit-0.3.2.1..
Preprocessing library for tar-conduit-0.3.2.1..
Building library for tar-conduit-0.3.2.1..
Configuring test suite 'tests' for tar-conduit-0.3.2.1..
Configuring test suite 'space' for tar-conduit-0.3.2.1..
Preprocessing test suite 'tests' for tar-conduit-0.3.2.1..
Building test suite 'tests' for tar-conduit-0.3.2.1..
Preprocessing test suite 'space' for tar-conduit-0.3.2.1..
Building test suite 'space' for tar-conduit-0.3.2.1..
Running 1 test suites...
Test suite space: RUNNING...
Running 1 test suites...
Test suite tests: RUNNING...
Test suite space: PASS
Test suite logged to:
/home/janus/flipstone/tar-conduit/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/space/test/tar-conduit-0.3.2.1-space.log
1 of 1 test suites (1 of 1 test cases) passed.
Test suite tests: PASS
Test suite logged to:
/home/janus/flipstone/tar-conduit/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/tests/test/tar-conduit-0.3.2.1-tests.log
1 of 1 test suites (1 of 1 test cases) passed.
Previous results were from git. But pulling from Hackage yields the same results:
janus@janus-ux305ca /tmp % cabal get tar-conduit
Downloading tar-conduit-0.3.2.1
Downloaded tar-conduit-0.3.2.1
Unpacking to tar-conduit-0.3.2.1/
[...]
cabal test -w ghc-9.6.2
[...]
Test suite space: RUNNING...
[2 of 2] Linking /tmp/tar-conduit-0.3.2.1/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/tests/build/tests/tests
Test suite space: PASS
Test suite logged to:
/tmp/tar-conduit-0.3.2.1/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/space/test/tar-conduit-0.3.2.1-space.log
1 of 1 test suites (1 of 1 test cases) passed.
Running 1 test suites...
Test suite tests: RUNNING...
Test suite tests: PASS
Test suite logged to:
/tmp/tar-conduit-0.3.2.1/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/tests/test/tar-conduit-0.3.2.1-tests.log
1 of 1 test suites (1 of 1 test cases) passed.
For posterity, the contents of tar-conduit-0.3.2.1-tests.log on my system:
Test suite tests: RUNNING...
tar/untar
content [✔]
tar/untar/tar
structure [✔]
untar
create-intermediate [✔]
ustar
minimal [✔]
long file name <255 [✔]
GNUtar
LongLink - a file with long file name [✔]
LongLink - multiple files with long file names [✔]
Large User Id [✔]
All Large Numeric Values [✔]
Negative Values [✔]
Negative Size [✔]
tar/untar Property [✔]
+++ OK, passed 100 tests.
unsupported headers
associated payload is discarded [✔]
Finished in 1.0023 seconds
13 examples, 0 failures
Test suite tests: PASS
Test suite logged to: /tmp/tar-conduit-0.3.2.1/dist-newstyle/build/x86_64-linux/ghc-9.6.2/tar-conduit-0.3.2.1/t/tests/test/tar-conduit-0.3.2.1-tests.log
@ysangkok - I also wasn't able to reproduce this on my machine; I've only encountered this on the stackage build server - so it might be a strange onetime occurrence - or it might have to do with the way stackage builds the packages: https://github.com/commercialhaskell/stackage/blob/b760495570e8e3dd72330fa0bb32439eaacb07f6/automated/build.sh#L136 - also I'm not really sure if it is worth to invest time to fully analyze this thing; it was more my attention to maybe revisit the (test) code and reconsider if something is wrong; if it is o.k. for you that we didn't expect test case success during stackage build, feel free to simple close the issue.
Disabled tests for stackage build.