ci: skip flaky Arbitrum fork test that fails due to inconsistent RPC … #11942
+4
−1
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.
found this while #11939 —the
repros::issue_4640
test keeps failing all 3 retry attempts in CI.Turns out it relies on Arbitrum RPC returning
l1BlockNumber
in the block response, but the endpoint doesn't always include it. When it's missing, we get L2 block 75219831 instead of the expected L1 block 16939475.can't depend on that field being there. Ignoring it like
issue_3703
for flaky Polygon RPCs.