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

@iwiznia

🚨 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: @christianwen
🤝 Merged by: @iwiznia
🐛 Error Message:
warning: No matching artifact of type LOG found for debug.log, skipping
failure: Test run failed after 3090 seconds with: undefined. Timeout is set to 7200
warning: No matching artifact of type LOG found for debug.log, skipping
failure: Test run failed after 2915 seconds with: undefined. Timeout is set to 7200
failure: Process returned exit code 1
Launched as "/home/runner/runners/2.321.0/externals/node20/bin/node /home/runner/work/_actions/Wandalen/wretry.action/v3.5.0_js_action/src/Runner.mjs /home/runner/work/_actions/Wandalen/aws-devicefarm/test-application/dist/index.js"
Launched at "/home/runner/work/App/App"
Attempts exhausted, made 2 attempts :
Attempt Some initial fixes and code style updates #1 started at : 18:06:37 GMT+0000 (Coordinated Universal Time)
Attempt Fix spaces #2 started at : 18:59:47 GMT+0000 (Coordinated Universal Time)
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:

Why the PR caused the job to fail?
Address any underlying issues.

🐛 We appreciate your help in squashing this bug!

@DylanDylann

@christianwen @DylanDylann got this issue assigned, should I have not merged the PR #51172?

@iwiznia

@iwiznia I think the error log here is unrelated to my PR and I can run this job on my local device.

Warning: No matching artifact of type LOG found for debug.log, skipping
Error: Test run failed after 2915 seconds with: undefined. Timeout is set to 7200

I see there're 2 PRs that fails job:

And re-run successfully. Should we give it another try?

📣 @christianwen! 📣
Hey, it seems we don’t have your contributor details yet! You'll only have to do this once, and this is how we'll hire you on Upwork.
Please follow these steps:

Make sure you've read and understood the contributing guidelines.
Get the email address used to login to your Expensify account. If you don't already have an Expensify account, create one here. If you have multiple accounts (e.g. one for testing), please use your main account email.
Get the link to your Upwork profile. It's necessary because we only pay via Upwork. You can access it by logging in, and then clicking on your name. It'll look like this. If you don't already have an account, sign up for one here.
Copy the format below and paste it in a comment on this issue. Replace the placeholder text with your actual details.

Format:

Contributor details
Your Expensify account email: <REPLACE EMAIL HERE>
Upwork Profile Link: <REPLACE LINK HERE>

And re-run successfully. Should we give it another try?

It failed again https://github.com/Expensify/App/actions/runs/12484590267/job/34890814512

@DylanDylann

@christianwen @DylanDylann can you take a look please?

@DylanDylann

Bump @christianwen @DylanDylann

I just checked it but still struggle with this one. @christianwen Do you have any input on it?

@iwiznia

I have no idea about this job, can we run it locally @iwiznia ?

@iwiznia

@iwiznia Do we have any document/guideline for e2ePerformanceTests jobs? It seems we need to simulate an environment on AWS to run it locally

@christianwen Do you have any update here?

@kirillzyusko

@kirillzyusko I noticed you already worked on this area recently #51182. Could you help on this one?

@DylanDylann

@DylanDylann @kirillzyusko I'm stuck on the way to simulate this test on local machine. It would be great if we have the instruction for this.

@iwiznia

@iwiznia Do we have any document/guideline for e2ePerformanceTests jobs? It seems we need to simulate an environment on AWS to run it locally

Not really, but I assume someone must have it, post it in the public slack channel (and then post the link to that here) and I bet someone that knows this will help you out.

The Slack link: https://expensify.slack.com/archives/C01GTK53T8Q/p1736483119612509

I think the problem is solved in #55000 right?

@iwiznia

@iwiznia Could you please run this job again?

Re-run here https://github.com/Expensify/App/actions/runs/12484590267 but not sure if that's what we want since I think that will run it with the old code... 🤔

It failed, but I think it run the old code, since it is the same job. Not sure what exactly we need to do.

@kirillzyusko

@kirillzyusko Could you please give your thoughts on this problem? Many thanks

@DylanDylann

@DylanDylann @iwiznia yes, it will fail because it's old code. I think we should simply close the issue - as a proof that it works we can attach a screenshot from main branch that it works 👀

Navigation Menu

Repository navigation

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

9 remaining items

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

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

Description

Activity

iwiznia commented on Dec 24, 2024

zzz0108 commented on Dec 25, 2024

melvin-bot commented on Dec 25, 2024

iwiznia commented on Dec 26, 2024

iwiznia commented on Jan 3, 2025

iwiznia commented on Jan 6, 2025

DylanDylann commented on Jan 7, 2025

zzz0108 commented on Jan 8, 2025

9 remaining items

DylanDylann commented on Jan 16, 2025

DylanDylann commented on Jan 16, 2025

zzz0108 commented on Jan 16, 2025

iwiznia commented on Jan 16, 2025

DylanDylann commented on Jan 17, 2025

kirillzyusko commented on Jan 17, 2025

DylanDylann commented on Jan 17, 2025

iwiznia commented on Jan 17, 2025

iwiznia commented on Jan 20, 2025

DylanDylann commented on Jan 21, 2025

kirillzyusko commented on Jan 21, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions