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.

Sign up for GitHub

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

Jump to bottom

CI failing due to vmmeter port not found #32324

Closed
codeboten opened this issue Apr 11, 2024 · 4 comments
Closed

CI failing due to vmmeter port not found #32324

codeboten opened this issue Apr 11, 2024 · 4 comments
Labels
ci-cd CI, CD, testing, build issues closed as inactive flaky test a test is flaky Stale

Comments

@codeboten
Copy link
Contributor

Component(s)

No response

Describe the issue you're reporting

Have seen a few intermittent failures with the following message:

Screenshot 2024-04-11 at 9 35 21 AM

https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8649717519/job/23716914434?pr=32267
@codeboten codeboten added the needs triage New item requiring triage label Apr 11, 2024
@crobert-1 crobert-1 added ci-cd CI, CD, testing, build issues flaky test a test is flaky labels Apr 11, 2024
@crobert-1
Copy link
Member

crobert-1 commented Apr 11, 2024 •
edited
Loading

For some context, the vmmeter-action was added recently as a part of #32135, which added support for ARM-based testing.

@crobert-1
Copy link
Member

I've filed self-actuated/vmmeter-action#1 as this may be an issue in the GitHub action itself.

@atoulme atoulme mentioned this issue Apr 11, 2024
Merged
codeboten pushed a commit that referenced this issue Apr 11, 2024
@atoulme
[chore] Remove vmmeter to fix flaky build step (#32329)
adae336 
Comment out vmmeter while
self-actuated/vmmeter-action#1 is ongoing

**Link to tracking Issue:** #32324
@crobert-1 crobert-1 removed the needs triage New item requiring triage label Apr 15, 2024
@github-actions github-actions bot mentioned this issue Apr 16, 2024
Closed
@github-actions GitHub Actions
Copy link
Contributor

This issue has been inactive for 60 days. It will be closed in 60 days if there is no activity. To ping code owners by adding a component label, see Adding Labels via Comments, or if you are unsure of which component this issue relates to, please ping @open-telemetry/collector-contrib-triagers. If this issue is still relevant, please ping the code owners or leave a comment explaining why it is still relevant. Otherwise, please close it.

@github-actions github-actions bot added the Stale label Jun 17, 2024
@adrielp adrielp mentioned this issue Jul 10, 2024
Closed
@github-actions GitHub Actions
Copy link
Contributor

This issue has been closed as inactive because it has been stale for 120 days with no activity.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Aug 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
ci-cd CI, CD, testing, build issues closed as inactive flaky test a test is flaky Stale
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@codeboten @crobert-1