Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Monitoring] Adding test case reproducibility metric #4358

Merged
merged 4 commits into from
Nov 4, 2024

Conversation

vitorguidi
Copy link
Collaborator

@vitorguidi vitorguidi commented Oct 24, 2024

Motivation

The Chrome team has no easy visibility into how many manually uploaded test cases flake or successfully reproduce. This PR implements a counter metric to track that.

There are three possible outcomes, each represented by a string label: 'reproduces', 'one_timer' and 'does_not_reproduce'

Part of #4271

@@ -2045,8 +2045,7 @@ def _to_engine_output(output: str, return_code: int,
def _upload_engine_output_log(engine_output):
timestamp = uworker_io.proto_timestamp_to_timestamp(engine_output.timestamp)
testcase_manager.upload_log(engine_output.output.decode(),
engine_output.return_code,
timestamp)
engine_output.return_code, timestamp)
Copy link
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is a linter complaint

Copy link
Collaborator

@jonathanmetzman jonathanmetzman left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@vitorguidi vitorguidi merged commit 74797c2 into master Nov 4, 2024
7 checks passed
@vitorguidi vitorguidi deleted the feature/flakyness-metrics branch November 4, 2024 23:49
@vitorguidi vitorguidi changed the title Adding test case reproducibility metric [Monitoring] Adding test case reproducibility metric Nov 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants