-
Notifications
You must be signed in to change notification settings - Fork 2.9k
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
Comments
@kosmydel any ideas what triggered this? |
I'm mostly OOO today, I will ask someone from SWM to have a look at this. |
I don't think it's related to Kuba's PR @grgia.
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 |
Posting in slack https://expensify.slack.com/archives/C03TQ48KC/p1718202204055039 |
@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 |
@mountiny right. Was it one time CI failure and it didn't appear anymore since that time? |
I think I havent seen it since |
Cool yeah closing for now and we can investigate if we see it on newer PRs |
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 |
🚨 Failure Summary 🚨:
warning: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: realm/aws-devicefarm@7b9a912. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
failure: Process completed with exit code 1.
warning: No matching artifact of type LOG found for debug.log, skipping
failure: Test run failed after 1805 seconds with: undefined. Timeout is set to 5400
🛠️ 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:
🐛 We appreciate your help in squashing this bug!
The text was updated successfully, but these errors were encountered: