Skip to content

investigate flaky test-fs-utimes in CI on Pi2 #37692

Closed as not planned
Closed as not planned
investigate flaky test-fs-utimes in CI on Pi2#37692
Labels
armIssues and PRs related to the ARM architecture.flaky-testIssues and PRs involving tests that fail intermittently in CI.fsIssues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@Trott
Trott
opened on Mar 10, 2021

Originally posted by @mhdawson in #36591 (comment)

Failed in CI as well: https://ci.nodejs.org/job/node-test-binary-arm-12+/lastCompletedBuild/RUN_SUBSET=0,label=pi2-docker/testReport/(root)/test/parallel_test_fs_utimes/ although with different error:

ode:assert:399
    throw err;
    ^

AssertionError [ERR_ASSERTION]: FAILED: expect_errno [Arguments] {
  '0': 'futimesSync',
  '1': 22,
  '2': AssertionError [ERR_ASSERTION]: FAILED: expect_ok [Arguments] {
    '0': 'futimesSync',
    '1': 22,
    '2': undefined,
    '3': '123456',
    '4': -1
  }
       check_mtime: 2.3949999809265137
      at expect_ok (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:64:3)
      at syncTests (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:142:7)
      at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:120:11
      at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:377:15
      at FSReqCallback.oncomplete (node:fs:184:23) {
    generatedMessage: false,
    code: 'ERR_ASSERTION',
    actual: undefined,
    expected: true,
    operator: '=='
  },
  '3': 'ENOSYS'
}
    at expect_errno (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:56:3)
    at syncTests (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:144:7)
    at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:120:11
    at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:377:15
    at FSReqCallback.oncomplete (node:fs:184:23) {
  generatedMessage: false,
  code: 'ERR_ASSERTION',
  actual: false,
  expected: true,
  operator: '=='
}

Activity

  1. Trott commented on Mar 10, 2021

    @Trott
    Trott
    on Mar 10, 2021
    MemberAuthor

    CI failure again:

    https://ci.nodejs.org/job/node-test-binary-arm-12+/9681/RUN_SUBSET=3,label=pi2-docker/console

    00:39:33 not ok 229 parallel/test-fs-utimes
00:39:33   ---
00:39:33   duration_ms: 4.757
00:39:33   severity: fail
00:39:33   exitcode: 1
00:39:33   stack: |-
00:39:33     node:assert:402
00:39:33         throw err;
00:39:33         ^
00:39:33     
00:39:33     AssertionError [ERR_ASSERTION]: FAILED: expect_ok [Arguments] {
00:39:33       '0': 'futimes',
00:39:33       '1': 22,
00:39:33       '2': null,
00:39:33       '3': '123456',
00:39:33       '4': -1
00:39:33     }
00:39:33          check_mtime: 2.0460000038146973
00:39:33         at expect_ok (/home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:64:3)
00:39:33         at /home/iojs/build/workspace/node-test-binary-arm/test/parallel/test-fs-utimes.js:118:11
00:39:33         at /home/iojs/build/workspace/node-test-binary-arm/test/common/index.js:376:15
00:39:33         at FSReqCallback.oncomplete (node:fs:190:23) {
00:39:33       generatedMessage: false,
00:39:33       code: 'ERR_ASSERTION',
00:39:33       actual: null,
00:39:33       expected: true,
00:39:33       operator: '=='
00:39:33     }
00:39:33   ...
  2. Trott
    added
    armIssues and PRs related to the ARM architecture.
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    fsIssues and PRs related to file-system APIs and the fs module.
    on Mar 10, 2021

  3. anonrig commented on Sep 6, 2024

    @anonrig
    anonrig
    on Sep 6, 2024
    Member

    This is still flaky https://ci.nodejs.org/job/node-test-commit-plinux/55201/nodes=rhel8-ppc64le/testReport/junit/(root)/parallel/test_fs_utimes/

  4. aduh95 commented on Sep 6, 2024

    @aduh95
    aduh95
    on Sep 6, 2024
    Contributor

    Cannot reproduce on macOS

    $ tools/test.py --repeat 9999 test/parallel/test-fs-utimes.js -t 9 
[07:05|% 100|+ 9999|-   0]: Done                  

All tests passed.

  5. jasnell commented on Sep 8, 2024

    @jasnell
    jasnell
    on Sep 8, 2024
    Member

    I was able to reproduce on ubuntu by testing a theory... I ran a couple other parallel processes to stress the host and then ran the test. The flake here may be caused by too much running in parallel. I suggest we try moving the test to sequential and see if that helps.

  6. nodejs-github-bot
    added a commit that references this issue on Apr 7, 2026

    test: capture negative utimes mtime at call time

    efa05f2
  7. aduh95
    added 2 commits that reference this issue on May 5, 2026

    test: capture negative utimes mtime at call time

    4097fb9

    test: capture negative utimes mtime at call time

    7b1211f

  8. github-actions commented on Jun 27, 2026

    @github-actions
    github-actionsbot
    on Jun 27, 2026 – with GitHub Actions
    Contributor

    This issue has been marked as stale due to 210 days of inactivity.
    It will be automatically closed in 30 days if no further activity occurs. If this is still relevant, please leave a comment or update it to keep it open.

  9. github-actions
    added
    staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.
    on Jun 27, 2026

  10. github-actions commented on Jul 28, 2026

    @github-actions
    github-actionsbot
    on Jul 28, 2026 – with GitHub Actions
    Contributor

    This issue has been automatically closed after 30 days of inactivity following its stale status (no activity for a total of 120 days).
    If this is still relevant, feel free to reopen it or leave a comment with additional details so we can continue the discussion.

  11. github-actions
    closed this as not plannedon Jul 28, 2026
  12. marco-ippolito
    added a commit that references this issue on Jul 29, 2026

    test: capture negative utimes mtime at call time

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    armIssues and PRs related to the ARM architecture.flaky-testIssues and PRs involving tests that fail intermittently in CI.fsIssues and PRs related to file-system APIs and the fs module.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions