Package-lock-related Travis CI failures #3
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
rodentrabies
force-pushed
the
travis-build-failures
branch
5 times, most recently
from
42114a1
to
5e83dfe
Compare
Test system run is enabled (as opposed to test system build only). Running the tests revealed several issues on AllegroCL (free edition heap limit) and CLISP (weird octet stream error), so they are marked as allowed to fail.
rodentrabies
force-pushed
the
travis-build-failures
branch
from
5e83dfe
to
2595340
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes the package-lock related failures from #2 and enables the test runs (previously only the build of the test system was tested). The actual test runs reveal other problems with several Lisp implementations, so those are moved to
allow_failures.