-
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 #42163
Comments
@WojtekBoman @kirillzyusko @hannojg can you please check this out? |
I think it's a second time when I notice this issue 👀 The problem is that first time when we fetch data -> we can not fetch it in 5 minutes and we see such screen: After 5 minutes we close the app (we treat it as unresponsive). I've tested the same builds on my machine (I downloaded them from GitHub) and everything passes. Could it be because AWS device doesn't have internet connection (or maybe its wi-fi adapter is damaged/broken). @mountiny Is it possible for a failed flow to detect which device was used during the run? I want to compare devices which were used during failed workflows 👀 |
I see, thanks for digging @kirillzyusko
I have no idea specifically for these flows, but I would assume we can log the device specifics in the workflow. @hannojg should be able to help with this |
@kirillzyusko any updates here? |
@mountiny not yet, switching to this issue as it's high priority 👀 |
This issue has not been updated in over 15 days. @mountiny eroding to Monthly issue. P.S. Is everyone reading this sure this is really a near-term priority? Be brave: if you disagree, go ahead and close it out. If someone disagrees, they'll reopen it, and if they don't: one less thing to do! |
I think it can be closed now, because the fix was deployed and fixed the problem |
Thank you! |
🚨 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 1405 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: