Repository navigation
fix: preserve coverage failure diagnostics - #22
Closed
AlbertoCentonze wants to merge 1 commit into
Closed
AlbertoCentonze wants to merge 1 commit into
AlbertoCentonze wants to merge 1 commit into
Conversation
AlbertoCentonze
added this pull request to stack #18
September 14, 2026 15:00
AlbertoCentonze
removed this pull request from stack #18
September 14, 2026 15:06
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
1 participant
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.
Coverage failures currently hide Forge stdout inside a truncated Node Buffer. In aave-helpers #806, all 311 ordinary tests passed before coverage failed, but 36,520 bytes of its stdout were omitted, leaving the cause unknown.
Run coverage directly in a Bash step so complete stdout and stderr reach the job log and a nonzero status fails the step. Disable the formatter action's embedded coverage command to avoid running coverage twice. Diagnostics stay in GitHub-masked job logs rather than unmasked raw-log artifacts.