Skip to content

Investigate workflow job failing on main: test / test (job 7) #85128

Closed

Description

@github-actions

🚨 Failure Summary 🚨:

  • 📋 Job Name: test / test (job 7)
  • 🔧 Failure in Workflow: Process new code merged to main
  • 🔗 Triggered by PR: PR Link
  • 👤 PR Author: @imgyf
  • 🤝 Merged by: @yuwenmemon
  • 🐛 Error Message:
    warning: Node.js 20 actions are deprecated. The following actions are running on Node.js 20 and may not work as expected: actions/checkout@8ade135, SimenB/github-actions-cpu-cores@31e91de. Actions will be forced to run with Node.js 24 by default starting June 2nd, 2026. Please check if updated versions of these actions are available that support Node.js 24. To opt into Node.js 24 now, set the FORCE_JAVASCRIPT_ACTIONS_TO_NODE24=true environment variable on the runner or in your workflow file. Once Node.js 24 becomes the default, you can temporarily opt out by setting ACTIONS_ALLOW_USE_UNSECURE_NODE_VERSION=true. For more information see: https://github.blog/changelog/2025-09-19-deprecation-of-node-20-on-github-actions-runners/
    failure: Process completed with exit code 1.

⚠️ Action Required ⚠️:

🛠️ A recent merge appears to have caused a failure in the job named test / test (job 7).
🔍 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. yifangoh commented on Mar 13, 2026

    @yifangoh
    Contributor

    This test failure appears to be a CI infrastructure issue rather than a code regression from PR #83434.

    The error message is about Node.js 20 deprecation in GitHub Actions runners (actions/checkout and SimenB/github-actions-cpu-cores running on Node.js 20), not about the actual test code failing. PR #83434 only modified NetSuite credential handling logic and did not touch any test infrastructure, CI workflows, or dependencies that would cause this.

    The timing correlation (failure appearing after our merge) is likely coincidental — our PR was simply the commit that triggered the workflow run when this infrastructure deprecation warning started causing failures.

    This likely needs to be addressed by updating the affected GitHub Actions to versions that support Node.js 24.

  2. added
    ReviewingHas a PR in review
    Awaiting PaymentAuto-added when associated PR is deployed to production
    and removed on Mar 13, 2026
  3. changed the title [-]Investigate workflow job failing on main: test / test (job 7)[/-] [+][Due for payment 2026-03-24] Investigate workflow job failing on main: test / test (job 7)[/+] on Mar 17, 2026
  4. melvin-bot commented on Mar 17, 2026

    @melvin-bot

    Reviewing label has been removed, please complete the "BugZero Checklist".

  5. melvin-bot commented on Mar 17, 2026

    @melvin-bot

    The solution for this issue has been 🚀 deployed to production 🚀 in version 9.3.38-4 and is now subject to a 7-day regression period 📆. Here is the list of pull requests that resolve this issue:

    If no regressions arise, payment will be issued on 2026-03-24. 🎊

  6. melvin-bot commented on Mar 17, 2026

    @melvin-bot

    Triggered auto assignment to @mallenexpensify (Awaiting Payment)

  7. removed their assignment
    on Mar 24, 2026
  8. changed the title [-][Due for payment 2026-03-24] Investigate workflow job failing on main: test / test (job 7)[/-] [+]Investigate workflow job failing on main: test / test (job 7)[/+] on Mar 24, 2026
  9. mallenexpensify commented on Mar 24, 2026

    @mallenexpensify
    Contributor

    No contributors assigned, removing payment deets

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