Investigate workflow job failing on main: e2ePerformanceTests / Run E2E tests in AWS device farm

[github-actions]

🚨 Failure Summary 🚨:

• 📋 Job Name: e2ePerformanceTests / Run E2E tests in AWS device farm
• 🔧 Failure in Workflow: Process new code merged to main
• 🔗 Triggered by PR: PR Link
• 👤 PR Author: @grgia
• 🤝 Merged by: @dangrous
• 🐛 Error Message:
  warning: The following actions uses Node.js version which is deprecated and will be forced to run on node20: realm/aws-devicefarm@7b9a912. For more info: https://github.blog/changelog/2024-03-07-github-actions-all-actions-will-run-on-node20-instead-of-node16-by-default/
  failure: Process completed with exit code 1.
  warning: No matching artifact of type LOG found for debug.log, skipping
  failure: Test run failed after 2545 seconds with: undefined. Timeout is set to 5400

⚠️ 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!

[dangrous]

ugggh this is that same one. Checking with margelo to see if they have ideas

[dangrous]

Forgot to link: https://expensify.slack.com/archives/C035J5C9FAP/p1720107180975539?thread_ts=1718788565.696269&cid=C035J5C9FAP

Given that this has come up a number of times and we've closed each time, I'm going to demote to daily, but continue to investigate.

[dangrous]

As per Slack, there's not really enough evidence here to find a cause/solution. We're going to wait for additional similar issues to crop up and then keep on from there! Demoting to weekly while we wait.

[dangrous]

Looks like we got at least one more - #45223

[dangrous]

This might be the same as the one I just linked - #46129 - and if so the solution to that should fix both!

[dangrous]

Checking whether the solution for #46129 will also fix this.

[dangrous]

Sounds like it's a different solution - #46129 (comment) - but has been merged! I'm going to close this out.