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

Closed
github-actions bot opened this issue Feb 22, 2024 · 5 comments
Assignees

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!

@srikarparsi
Copy link
Contributor

Will take a look at this tomorrow

@melvin-bot melvin-bot bot removed the Overdue label Feb 26, 2024
@srikarparsi
Copy link
Contributor

Not sure what's going on, the performance tests seemed to have passed when I merged. @hannojg do you have any thoughts on this, it seems like it could be related to this message?

@hannojg
Copy link
Contributor

hannojg commented Feb 27, 2024

(Copied from slack)

last week we merged a PR #29991 that changes the navigation to use the native platform navigation components (better native like performance for navigation).
However, it seems like it introduced a regression. That regression is currently also failing the e2e tests (thats how we detected the regression actually):

Issue: #37156
PR mitigating the issue: #37155

@hannojg
Copy link
Contributor

hannojg commented Feb 27, 2024

So the mentioned PR hasn't anything todo with the failed tests

@srikarparsi
Copy link
Contributor

Cool sounds good. In that case I'll close out this issue

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

2 participants