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

[chore]Use Right file name for the prometheus compliance tests #24729

Merged
merged 8 commits into from
Sep 6, 2023

Conversation

vasireddy99
Copy link
Contributor

@vasireddy99 vasireddy99 commented Jul 31, 2023

Description:

This PR fixes the right file name for running the prometheus compliance tests.
The actual name of downloaded artifact as part of the test is otelcol_0.42.0_linux_amd64. when we place the collector contrib artefact under the same name in the bin folder with the name otelcol_linux_amd64 the tests will still be run on otelcol_0.42.0_linux_amd64 artefact. so by changing the name of the artefact, the tests will run on top of that.

Additional Context :

We shall need to track this issue prometheus/compliance#97 as the naming conventions of the artefacts used in the target could be changed upon the issue resolution

No ChangeLog entry is needed.

@vasireddy99 vasireddy99 marked this pull request as ready for review July 31, 2023 18:42
@vasireddy99 vasireddy99 requested review from a team and evan-bradley July 31, 2023 18:42
@vasireddy99 vasireddy99 changed the title [chore]Use Right file name for the compliance [chore]Use Right file name for the prometheus compliance tests Jul 31, 2023
@github-actions
Copy link
Contributor

This PR was marked stale due to lack of activity. It will be closed in 14 days.

@@ -45,9 +45,10 @@ jobs:
with:
repository: prometheus/compliance
path: compliance
Copy link
Contributor

Choose a reason for hiding this comment

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

should we checkout a specific commit/tag?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

oh, I am not sure if we need to checkout specific tag. Since I see the tests are stable now at the main/recent commit.

@codeboten codeboten merged commit de60682 into open-telemetry:main Sep 6, 2023
95 of 96 checks passed
@github-actions github-actions bot added this to the next release milestone Sep 6, 2023
@vasireddy99 vasireddy99 deleted the fixcom branch September 7, 2023 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ready to merge Code review completed; ready to merge by maintainers
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants