Skip to content

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

Closed

Description

@github-actions

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

Activity

  1. grgia commented on Jun 4, 2024

    @grgia
    Contributor

    @kosmydel any ideas what triggered this?

  2. kosmydel commented on Jun 4, 2024

    @kosmydel
    Contributor

    @kosmydel any ideas what triggered this?

    I'm mostly OOO today, I will ask someone from SWM to have a look at this.

  3. blazejkustra commented on Jun 4, 2024

    @blazejkustra
    Contributor

    I don't think it's related to Kuba's PR @grgia.

    warning: Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20

    From the error message Node v16 is deprecated. Same for AWS Node v16 will be deprecated in a week - that might be the real cause

  4. grgia commented on Jun 12, 2024

    @grgia
    Contributor
  5. mountiny commented on Jun 12, 2024

    @mountiny
    Contributor

    @kirillzyusko This was fixed already in main right, its just that the offending PR was not up to date with main when it was merged

  6. kirillzyusko commented on Jun 12, 2024

    @kirillzyusko
    Contributor

    This was fixed already in main right,

    @mountiny right. Was it one time CI failure and it didn't appear anymore since that time?

  7. mountiny commented on Jun 12, 2024

    @mountiny
    Contributor

    I think I havent seen it since

  8. mountiny commented on Jun 12, 2024

    @mountiny
    Contributor

    Cool yeah closing for now and we can investigate if we see it on newer PRs

  9. dangrous commented on Jun 18, 2024

    @dangrous
    Contributor

    oh hi there - I got this as well - the PR was raised 6/12 so not sure if it's due to it not being up to date? #43941

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions