-
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
[HOLD for payment 2024-06-28] [HOLD for payment 2024-06-13] Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm #42987
Comments
The PR in question changed 1 boolean condition which affects some edge case whether ProfilePage shows up or NotFound page. |
@Kicu yeah, you are right - these failures are not related to these changes. I already foudn a root cause and will submit a fix soon 🤞 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.79-11 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-13. 🎊 |
|
The solution for this issue has been 🚀 deployed to production 🚀 in version 1.4.85-7 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue: If no regressions arise, payment will be issued on 2024-06-28. 🎊 |
🚨 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 1775 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: