Skip to content

test-process-uid-gid failures in ASAN GitHub Actions builds #43082

Description

@richardlau

Test

test-process-uid-gid

Platform

Ubuntu 20.04, ASAN build

Console output

=== release test-process-uid-gid ===
Path: parallel/test-process-uid-gid
Error: --- stderr ---
Tracer caught signal 11: addr=0x0 pc=0xb04af4 sp=0x7fdc48672d40
==116787==LeakSanitizer has encountered a fatal error.
==116787==HINT: For debugging, try setting environment variable LSAN_OPTIONS=verbosity=1:log_threads=1
==116787==HINT: LeakSanitizer does not work under ptrace (strace, gdb, etc)
Command: out/Release/node /home/runner/work/node/node/test/parallel/test-process-uid-gid.js

===
=== 1 tests failed
===

Build links

Additional information

This appears to happening quite often, and I think is relatively recent as I don't recall seeing this test fail in this way before (ASAN builds have been flaky with other tests).

Activity

  1. added
    flaky-testIssues and PRs involving tests that fail intermittently in CI.
    on May 13, 2022
  2. targos commented on May 13, 2022

    @targos
    Member

    It looks like an asan bug. I don't know if we can find out whether it was recently updated in GH runners

  3. targos commented on May 13, 2022

    @targos
    Member

    It seems that the first occurence if the failure was on May 08: https://github.com/nodejs/node/actions/runs/2290808251/attempts/1

    This corresponds to an update of the ubuntu 20.04 image: actions/runner-images@6c66ae2

  4. added a commit that references this issue on May 15, 2022
  5. added a commit that references this issue on May 16, 2022
  6. added a commit that references this issue on May 31, 2022
  7. added a commit that references this issue on Jun 27, 2022
  8. added a commit that references this issue on Jul 12, 2022
  9. added a commit that references this issue on Jul 31, 2022
  10. added a commit that references this issue on Oct 10, 2022
  11. github-actions commented on Jun 25, 2026

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

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

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

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

    flaky-testIssues and PRs involving tests that fail intermittently in CI.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