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

Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm #43026

Closed
github-actions bot opened this issue Jun 4, 2024 · 9 comments
Assignees

Comments

@github-actions
Copy link
Contributor

github-actions bot commented Jun 4, 2024

🚨 Failure Summary 🚨:

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named e2ePerformanceTests / Run E2E tests in AWS device farm.
This issue has been automatically created and labeled with Workflow Failure for investigation.

👀 Please look into the following:

  1. Why the PR caused the job to fail?
  2. Address any underlying issues.

🐛 We appreciate your help in squashing this bug!

@grgia
Copy link
Contributor

grgia commented Jun 4, 2024

@kosmydel any ideas what triggered this?

@kosmydel
Copy link
Contributor

kosmydel commented Jun 4, 2024

@kosmydel any ideas what triggered this?

I'm mostly OOO today, I will ask someone from SWM to have a look at this.

@blazejkustra
Copy link
Contributor

I don't think it's related to Kuba's PR @grgia.

warning: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20

From the error message Node v16 is deprecated. Same for AWS Node v16 will be deprecated in a week - that might be the real cause

@melvin-bot melvin-bot bot added the Overdue label Jun 6, 2024
@grgia
Copy link
Contributor

grgia commented Jun 12, 2024

@melvin-bot melvin-bot bot removed the Overdue label Jun 12, 2024
@mountiny
Copy link
Contributor

@kirillzyusko This was fixed already in main right, its just that the offending PR was not up to date with main when it was merged

@kirillzyusko
Copy link
Contributor

This was fixed already in main right,

@mountiny right. Was it one time CI failure and it didn't appear anymore since that time?

@mountiny
Copy link
Contributor

I think I havent seen it since

@mountiny
Copy link
Contributor

Cool yeah closing for now and we can investigate if we see it on newer PRs

@dangrous
Copy link
Contributor

oh hi there - I got this as well - the PR was raised 6/12 so not sure if it's due to it not being up to date? #43941

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants