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

Add metadata to Flakeguard report #1473

Merged
merged 3 commits into from
Dec 11, 2024
Merged

Add metadata to Flakeguard report #1473

merged 3 commits into from
Dec 11, 2024

Conversation

lukaszcl
Copy link
Contributor

@lukaszcl lukaszcl commented Dec 11, 2024


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

Why

The changes introduce metadata fields related to the repository and commit SHAs into the test report and aggregate results command. This enriches the test reports with crucial versioning and source information, making it easier to trace test results back to specific changes in the codebase.

What

  • tools/flakeguard/cmd/aggregate_results.go
    • Added new flag definitions for repo-url, head-sha, base-sha, and github-workflow-name. This allows users to specify repository details and commit SHAs when aggregating test results.
    • Included additional metadata (HeadSHA, BaseSHA, RepoURL, GitHubWorkflowName) in the aggregated test report. This ensures that the report contains detailed context about the source of the test results.
  • tools/flakeguard/reports/data.go
    • Modified the TestReport structure to include HeadSHA, BaseSHA, RepoURL, and GitHubWorkflowName fields alongside existing test report details. This update aligns the data structure with the new information being aggregated in the command changes.

@lukaszcl lukaszcl requested review from sebawo and a team as code owners December 11, 2024 16:48
@cl-sonarqube-production
Copy link

@lukaszcl lukaszcl merged commit d3bffaf into main Dec 11, 2024
46 of 49 checks passed
@lukaszcl lukaszcl deleted the flakeguard-metadata branch December 11, 2024 17:17
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