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 #42163

Closed
github-actions bot opened this issue May 14, 2024 · 8 comments
Assignees
Labels

Comments

@github-actions
Copy link
Contributor

🚨 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!

@mountiny
Copy link
Contributor

@WojtekBoman @kirillzyusko @hannojg can you please check this out?

@kirillzyusko
Copy link
Contributor

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:

image

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 👀

@melvin-bot melvin-bot bot added the Overdue label May 16, 2024
@mountiny
Copy link
Contributor

I see, thanks for digging @kirillzyusko

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 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

@melvin-bot melvin-bot bot removed the Overdue label May 19, 2024
@mountiny mountiny added Weekly KSv2 and removed Hourly KSv2 labels May 19, 2024
@melvin-bot melvin-bot bot added the Overdue label May 27, 2024
@mountiny
Copy link
Contributor

@kirillzyusko any updates here?

@melvin-bot melvin-bot bot removed the Overdue label May 27, 2024
@kirillzyusko
Copy link
Contributor

@mountiny not yet, switching to this issue as it's high priority 👀

Copy link

melvin-bot bot commented Jun 27, 2024

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!

@kirillzyusko
Copy link
Contributor

I think it can be closed now, because the fix was deployed and fixed the problem

@mountiny
Copy link
Contributor

Thank you!

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

No branches or pull requests

2 participants