Closed
Conversation
Contributor
Author
|
The issue was the foundry nightly warning. Disabling it fixed the problem. I used this action to create a CI job that would allow me to SSH into the box to debug things in an environment with the failure. Once in the box, I wrote a rust script similar to the one that was failing and cargo built it, then ran it to see what step was actually failing. It was the I've cherrypicked 385a775 onto #82 and will merge it there. Closing this out. |
This file contains hidden or 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
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.
Failing here #82
Trying to figure out why. Does CI fail on a ~clean branch off of master?