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: @brandonhenry
• 🤝 Merged by: @shawnborton
• 🐛 Error Message:
  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 1475 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!

[shawnborton]

@allroundexperts do you know what this stuff means exactly? I'm not an engineer, so I'm not sure how to be helpful for this one.

[brandonhenry]

definitely an odd one 🤔

[allroundexperts]

I'm not sure myself. Looks like something related to our backend infrastructure. Only an internal engineer can investigate this.

[melvin-bot]

Auto-assigning issues to engineers is no longer supported. If you think this issue should receive engineering attention, please raise it in #whatsnext.

[shawnborton]

Hmm I'm just going to close. Tagging @AndrewGable for visibility since it seems node related, but I don't think there is much we need to do here?

[AndrewGable]

This is not a backend issue, it's an issue telling you that the PR you merged had failing E2E tests: https://github.com/Expensify/App/actions/runs/9098195241/job/25009718389

While this one doesn't look like it was due to this PR, we should still investigate these. I think @hannojg is looking into this one.