fix(ci): add continue-on-error to tempo-foundry-test job#3398
Open
fix(ci): add continue-on-error to tempo-foundry-test job#3398
Conversation
tempo-foundry currently fails to build against latest tempo due to alloy-evm 0.29/0.30 incompatibility. The job is already listed in alls-green allowed-failures, but alls-green v1.2.2 has a known bug that still blocks the merge queue. continue-on-error works around this. Co-authored-by: Tanishk Goyal <64212892+legion2002@users.noreply.github.com> Amp-Thread-ID: https://ampcode.com/threads/T-019d43cc-1315-735a-b492-a8f9d349ec38
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
2 participants
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.
tempo-foundry fails to build against latest tempo (b6640b1) due to
alloy-evm0.29→0.30 incompatibility introduced by the reth deps update in #3332. Thetempo-foundry-testjob is already listed in alls-green'sallowed-failures, but alls-green v1.2.2 has a known bug that still blocks the merge queue.Adding
continue-on-error: trueat the job level is the GitHub-native workaround — it makes the job non-blocking for thespecs-successgate while keeping visibility.Root cause: tempo now uses
alloy-evm 0.30(which removed theopfeature), butalloy-op-evm 0.28(used by tempo-foundry) still requiresalloy-evmwithfeatures = ["op"]. No compatiblealloy-op-evmversion exists on crates.io yet.Prompted by: tanishk