Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

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

Closed
github-actions bot opened this issue Dec 26, 2024 · 1 comment
Assignees

Comments

@github-actions
Copy link
Contributor

🚨 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 2980 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 2930 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 : 16:48:11 GMT+0000 (Coordinated Universal Time)
    Attempt Fix spaces #2 started at : 17:40:06 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:

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

🐛 We appreciate your help in squashing this bug!

@iwiznia
Copy link
Contributor

iwiznia commented Dec 26, 2024

Dupe of #54542

@iwiznia iwiznia closed this as completed Dec 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant