Skip to content

v21.x failing modules #1033

Closed
Closed

Description

@RafaelGSS

The last 3 runs failed on Node.js 21. I've run against v21.x just to confirm it's nothing related to the v21.3.0 proposal

Modules:

citgm.jest-v29.7.0 #1032
citgm.ember-cli-v5.4.1 - @stefanpenner, @rwjblue, @Turbo87, @kellyselden
citgm.yeoman-generator-v7.1.1 - @SBoudrias, @sindresorhus
citgm.nan-v2.18.0 - @nodejs/addon-api
citgm.q-v1.5.1 - @kriskowal

Activity

  1. ljharb commented on Nov 30, 2023

    @ljharb
    SponsorMember

    i believe maxogden → @max-mapper

  2. arcanis commented on Nov 30, 2023

    @arcanis
    Contributor

    How can we check the logs? The @yarnpkg/cli logs seem unrelated to Yarn (ConnectTimeoutError: Connect Timeout Error), but perhaps I'm looking at the wrong place.

  3. RafaelGSS commented on Nov 30, 2023

    @RafaelGSS
    MemberAuthor

    @arcanis some of them might be related to the machine, yeah. I just want to make sure these timeouts aren't flaky on yarnpkg/cli but something with our machine

    The ci.nodejs.org links are the ones with logs.

  4. novemberborn commented on Nov 30, 2023

    @novemberborn
    Contributor

    AVA's failure is (most likely) a known issue, fixed in main but not yet released.

  5. mourner commented on Dec 3, 2023

    @mourner

    I tried looking into what might be the problem in binary-split, but it seems to work fine with Node v21.3. The logs for the failure above also says ConnectTimeoutError: Connect Timeout Error, so perhaps it's just a flaky test and not something that needs fixing?

  6. RafaelGSS commented on Dec 3, 2023

    @RafaelGSS
    MemberAuthor

    Timeout errors are usually machine issues since we run tests in parallel and the CPU can get stale causing timeouts. If this persists we can reduce/remove the concurrency - but it might affect the time elapsed of CITGM, which is undesirable.

  7. lpinca commented on Dec 3, 2023

    @lpinca
    Member

    The ws failure is the same and on the same platform for all runs. On macOS, that test also fails on GHA sometimes. I would prefer not to do it, but I think I can skip it on macOS.

  8. RafaelGSS commented on Dec 4, 2023

    @RafaelGSS
    MemberAuthor

    I've just removed for the issue description the modules where the authors/maintainers confirmed the issues aren't related to the package itself. Thank you!

    I'll wait maintainers' input for the other ones.

  9. pinned this issue on Dec 6, 2023
  10. RafaelGSS commented on Dec 12, 2023

    @RafaelGSS
    MemberAuthor

    I've read all the lists again and removed the ones failing with timeout, which tends to be a machine issue and I've created a PR to skip the non-machine-related failing on Node.js 21. #1035

  11. added a commit that references this issue on Dec 14, 2023
  12. RafaelGSS commented on May 22, 2024

    @RafaelGSS
    MemberAuthor

    Closing in favour of #1060

  13. unpinned this issue on May 22, 2024
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

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions