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

[github-actions[bot]]

🚨 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: @JKobrynski
• 🤝 Merged by: @flodnv
• 🐛 Error Message: warning: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: actions/cache@v3, actions/download-artifact@e9ef242655d12993efdcda9058dee2db83a2cb9b, realm/aws-devicefarm/test-application@7b9a91236c456c97e28d384c9e476035d5ea686b. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/. warning: No matching artifact of type LOG found for debug.log, skipping failure: Test run failed after 895 seconds with: undefined. Timeout is set to 5400 failure: Process completed with exit code 1.

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

[flodnv]

Weird, can you look into this please @JKobrynski @fabioh8010 @c3024 @filip-solecki ?

[c3024]

That mock is used only in storybook webpack config. I don't understand why this failed. 🤔

[fabioh8010]

@flodnv Do you know if it's possible to reproduce those e2e tests locally?

[c3024]

Are these the same tests?

[jjcoffee]

Note that this is a new automation, so the workflow failure hasn't necessarily been triggered by the linked PR - it could have been failing for a while before, so might require some digging to figure out the original source!

[flodnv]

@jjcoffee who added this automation and where? Can we have them investigate it if they caused this problem?

[jjcoffee]

@flodnv The automation was implemented in https://github.com/Expensify/App/issues/34110 to catch main silently failing. This is expected behaviour on the first run, so not a problem they've caused as such :smile:

[flodnv]

Looks like this is being handled elsewhere, as it should be: https://github.com/Expensify/App/issues/36240#issuecomment-1936105461

[jjcoffee]

@flodnv Is there an issue that's tracking where it's being handled? The way the automation works it will keep opening a new issue if there isn't already an open issue with the failing job in the title :sweat_smile:

[flodnv]

Looks like the PR has been merged: https://github.com/Expensify/App/issues/36240#issuecomment-1936105461