Codec.Compression.Zlib: premature end of compressed data stream #1814

Closed
asr opened this Issue Feb 2, 2016 · 4 comments

Comments

Projects
None yet
2 participants
@asr
Member

asr commented Feb 2, 2016

I have seen the error

agda: Codec.Compression.Zlib: premature end of compressed data stream

associated with different files in some Travis builds. After restarting the builds, the error disappears.

Right now, the error is in https://travis-ci.org/agda/agda/jobs/106551279.

Do we need to pay attention to this problem? (self-question)

@asr asr added the type: bug label Feb 2, 2016

@asr

This comment has been minimized.

Show comment
Hide comment
@asr

asr Feb 2, 2016

Member

Cabal also generates the same error (see haskell/cabal#2001).

Member

asr commented Feb 2, 2016

Cabal also generates the same error (see haskell/cabal#2001).

@andreasabel

This comment has been minimized.

Show comment
Hide comment
@andreasabel

andreasabel Feb 3, 2016

Contributor

Mmh, I wondered myself what is the cause. Could it be that too many files are open on travis, so it refuses to open one more instance of Common/Prelude.agda or what ever it is? Are the tests in the testsuite run in parallel? (Just a shot in the dark.)

Contributor

andreasabel commented Feb 3, 2016

Mmh, I wondered myself what is the cause. Could it be that too many files are open on travis, so it refuses to open one more instance of Common/Prelude.agda or what ever it is? Are the tests in the testsuite run in parallel? (Just a shot in the dark.)

@asr

This comment has been minimized.

Show comment
Hide comment
@asr

asr Feb 3, 2016

Member

Are the tests in the testsuite run in parallel?

Yes.

Member

asr commented Feb 3, 2016

Are the tests in the testsuite run in parallel?

Yes.

@asr asr added the zlib label Feb 4, 2016

asr added a commit that referenced this issue Feb 22, 2016

[ #1814 ] Using `j2` option with `succeed` test-suite in Travis.
Some figures from `make succeed` using the `-j` option in GHC 7.8.4:

j time (sec)
1 91
2 72
@asr

This comment has been minimized.

Show comment
Hide comment
@asr

asr Feb 22, 2016

Member

After ea14381 I'm closing the issue.

If it is necessary to reopen the issue, please report the test-suite (succeed, fail, etc.) where the issue occurred again.

Member

asr commented Feb 22, 2016

After ea14381 I'm closing the issue.

If it is necessary to reopen the issue, please report the test-suite (succeed, fail, etc.) where the issue occurred again.

@asr asr closed this Feb 22, 2016

@asr asr added this to the 2.5.1 milestone Feb 22, 2016

@asr asr self-assigned this Feb 22, 2016

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment