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

Fix flakeguard aggregate cmds #1348

Merged
merged 1 commit into from
Nov 18, 2024
Merged

Fix flakeguard aggregate cmds #1348

merged 1 commit into from
Nov 18, 2024

Conversation

lukaszcl
Copy link
Contributor

@lukaszcl lukaszcl commented Nov 18, 2024


Below is a summarization created by an LLM (gpt-4-0125-preview). Be mindful of hallucinations and verify accuracy.

Why

The changes improve the flexibility and clarity of file paths and messages in the FlakeGuard tool. Setting default paths to empty allows users to specify paths more dynamically, while changing output messages enhances user understanding of the operations performed.

What

  • tools/flakeguard/cmd/aggregate_all.go
    • Renamed from aggregate.go to aggregate_all.go to presumably differentiate it from similar functionalities.
    • Modified default values for results-path, output-results, and output-logs flags to be empty or more specific, enhancing user control.
  • tools/flakeguard/cmd/aggregate_failed.go
    • Updated default values for results-path, output-results, and output-logs flags to be empty or include a specific path, aligning with changes in aggregate_all.go.
    • Added default values for threshold and min-pass-ratio flags, specifying conditions for test failure and flakiness.
  • tools/flakeguard/reports/reports.go
    • Altered confirmation messages for saving results and logs to be more concise and clear, removing the term "filtered" for straightforwardness.

@cl-sonarqube-production
Copy link

@lukaszcl lukaszcl merged commit 9c9821d into main Nov 18, 2024
50 of 53 checks passed
@lukaszcl lukaszcl deleted the fix-flakeguard branch November 18, 2024 14:21
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.

2 participants