Skip to content

test-crypto-secure-heap fails on IBM i #36929

Closed as not planned
Closed as not planned
test-crypto-secure-heap fails on IBM i#36929
Assignees
ThePrez
Labels
flaky-testIssues and PRs involving tests that fail intermittently in CI.ibm iIssues and PRs related to the IBM i platform.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@richardlau
richardlau
opened on Jan 14, 2021
  • Test: parallel/test-crypto-secure-heap
  • Platform: IBM i
  • Console Output:
09:04:30 not ok 525 parallel/test-crypto-secure-heap
09:04:30   ---
09:04:30   duration_ms: 3.340
09:04:30   severity: fail
09:04:30   exitcode: 1
09:04:30   stack: |-
09:04:30     node:assert:119
09:04:30       throw new AssertionError(obj);
09:04:30       ^
09:04:30     
09:04:30     AssertionError [ERR_ASSERTION]: Expected values to be strictly equal:
09:04:30     
09:04:30     null !== 0
09:04:30     
09:04:30         at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-ibmi/nodes/ibmi72-ppc64/test/parallel/test-crypto-secure-heap.js:59:10)
09:04:30         at ChildProcess.<anonymous> (/home/iojs/build/workspace/node-test-commit-ibmi/nodes/ibmi72-ppc64/test/common/index.js:377:15)
09:04:30         at ChildProcess.emit (node:events:379:20)
09:04:30         at Process.ChildProcess._handle.onexit (node:internal/child_process:285:12) {
09:04:30       generatedMessage: true,
09:04:30       code: 'ERR_ASSERTION',
09:04:30       actual: null,
09:04:30       expected: 0,
09:04:30       operator: 'strictEqual'
09:04:30     }
09:04:30   ...

This test was newly added earlier in the week by 03c0564 and has been intermittently failing on IBM i (the CI for which is only run on the daily CI run) since.

Activity

  1. richardlau
    added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    ibm iIssues and PRs related to the IBM i platform.
    on Jan 14, 2021

  2. richardlau commented on Jan 14, 2021

    @richardlau
    richardlau
    on Jan 14, 2021
    MemberAuthor

    cc @nodejs/platform-ibmi

  3. ThePrez commented on Jan 14, 2021

    @ThePrez
    ThePrez
    on Jan 14, 2021
    Contributor

    Can you please assign this to @dmabupt and me?
    This might be due to some differences in the openssl build between the IBM distribution and the CI, since the IBM distribution uses the system-provided openssl that may have IBM patches. I haven't done debug/investigation, just a hunch.

  4. richardlau
    assigned
    ThePrez
    and unassigned
    ThePrez
    on Jan 14, 2021

  5. richardlau commented on Jan 14, 2021

    @richardlau
    richardlau
    on Jan 14, 2021
    MemberAuthor

    Can you please assign this to @dmabupt and me?

    I've assigned to you. I can't seem to assign to @dmabupt, probably because he's not in the nodejs org (that will happen as part of #36569).

  6. jasnell commented on Jan 14, 2021

    @jasnell
    jasnell
    on Jan 14, 2021
    Member

    Would be good to go ahead and open a PR marking it flaky on that platform (if you haven't done so already :-) ...)

  7. targos commented on Jan 14, 2021

    @targos
    targos
    on Jan 14, 2021
    Member

    probably because he's not in the nodejs org

    I think it's possible to assign external people after they commented on the thread.

  8. richardlau commented on Jan 18, 2021

    @richardlau
    richardlau
    on Jan 18, 2021
    MemberAuthor

    Would be good to go ahead and open a PR marking it flaky on that platform (if you haven't done so already :-) ...)

    Opened #36986.

  9. Trott
    added a commit that references this issue on Jan 19, 2021

    test: mark flaky tests on IBM i

    863ec7d
  10. ruyadorno
    added 2 commits that reference this issue on Jan 22, 2021

    test: mark flaky tests on IBM i

    3a122aa

    test: mark flaky tests on IBM i

    7acea78
  11. targos
    added a commit that references this issue on May 1, 2021

    test: mark flaky tests on IBM i

    5408f51

  12. 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.

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

  14. 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.

  15. github-actions
    closed this as not plannedon Jul 28, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

flaky-testIssues and PRs involving tests that fail intermittently in CI.ibm iIssues and PRs related to the IBM i platform.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