Expensify / App

Welcome to New Expensify: a complete re-imagination of financial collaboration, centered around chat. Help us build the next generation of Expensify by sharing feedback and contributing to the code.
https://new.expensify.com
MIT License
3.48k stars 2.83k forks source link

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

Closed github-actions[bot] closed 1 month ago

github-actions[bot] commented 1 month ago

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

arosiclair commented 1 month ago

I see

Run cat "./Host_Machine_Files/\$WORKING_DIRECTORY/output.md"
  cat "./Host_Machine_Files/\$WORKING_DIRECTORY/output.md"
  shell: /usr/bin/bash -e {0}
  env:
    AWS_DEFAULT_REGION: us-west-[2](https://github.com/Expensify/App/actions/runs/10579805709/job/29316543748#step:18:2)
    AWS_REGION: us-west-2
    AWS_ACCESS_KEY_ID: ***
    AWS_SECRET_ACCESS_KEY: ***
cat: './Host_Machine_Files/$WORKING_DIRECTORY/output.md': No such file or directory
Error: Process completed with exit code 1.

Seems like a configuration issue. Definitely not related to the PR.

arosiclair commented 1 month ago

Looks like this should be caused by another issue per this slack convo.. Closing this out.