Repository navigation
tests: Prevent gcov warnings spuriously failing test-history.sh - #6742
Merged
Merged
Conversation
If flatpak is built with code coverage enabled, libgcov sometimes helpfully emits messages in the output from programs under test. If we’re strictly comparing the whole output of a program to an expected string, as `test-history.sh` does in these two places, this can cause spurious test failures. Temporarily tell it to send its error messages to `/dev/null` as we don’t care about them for those tests. Signed-off-by: Philip Withnall <[email protected]>
pwithnall
force-pushed
the
test-gcov-fail
branch
from
July 27, 2026 16:28
856d4ab to
634d743
Compare
smcv
approved these changes
Jul 27, 2026
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
3 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.
If flatpak is built with code coverage enabled, libgcov sometimes helpfully emits messages in the output from programs under test.
If we’re strictly comparing the whole output of a program to an expected string, as
test-history.shdoes in these two places, this can cause spurious test failures.Temporarily tell it to send its error messages to
/dev/nullas we don’t care about them for those tests.