You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Investigate workflow job failing on main: test / test (job 8) #85841
🐛 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 8).
🔍 This issue has been automatically created and labeled with Workflow Failure for investigation.
These are all related to odometer image encoding (Base64/JPEG MIME type fix). None of them touch or affect the canEditFieldOfMoneyRequest logic.
The failing tests are:
canEditFieldOfMoneyRequest › move expense › type is expense › should return true for submitter of a distance request for amount and currency fields
canEditFieldOfMoneyRequest › move expense › type is expense › should return true for submitter when there are multiple outstanding reports
These test money request field editing permissions — a completely separate code path from image encoding.
Likely cause: PR #84673 ("Remove ONYXKEYS.COLLECTION.REPORT_VIOLATIONS") which modified ReportUtils.ts and CONST/index.ts and was the last PR to affect canEditFieldOfMoneyRequestTest.ts. That PR's removal of report violation logic likely affected the conditions checked by canEditFieldOfMoneyRequest.
Closing this issue as the failure is unrelated to the triggering PR.
Activity
Julesssss commentedon Mar 19, 2026
@MelvinBot investigate and close this issue if it is not related to our change
MelvinBot commentedon Mar 19, 2026
🔍 Investigation Result
The test failure is NOT related to PR #85574 (the odometer image fix).
Evidence
PR #85574 changed only these files:
src/CONST/index.tssrc/libs/fileDownload/FileUtils.tssrc/libs/stitchOdometerImages/index.native.tssrc/pages/iou/request/step/IOURequestStepDistanceOdometer.tsxsrc/pages/iou/request/step/IOURequestStepOdometerImage/index.native.tsxThese are all related to odometer image encoding (Base64/JPEG MIME type fix). None of them touch or affect the
canEditFieldOfMoneyRequestlogic.The failing tests are:
canEditFieldOfMoneyRequest › move expense › type is expense › should return true for submitter of a distance request for amount and currency fieldscanEditFieldOfMoneyRequest › move expense › type is expense › should return true for submitter when there are multiple outstanding reportsThese test money request field editing permissions — a completely separate code path from image encoding.
Likely cause: PR #84673 ("Remove ONYXKEYS.COLLECTION.REPORT_VIOLATIONS") which modified
ReportUtils.tsandCONST/index.tsand was the last PR to affectcanEditFieldOfMoneyRequestTest.ts. That PR's removal of report violation logic likely affected the conditions checked bycanEditFieldOfMoneyRequest.Closing this issue as the failure is unrelated to the triggering PR.