Skip to content

request-ci fails without error when CI is locked down #39746

Closed as not planned
Closed as not planned
request-ci fails without error when CI is locked down#39746
Labels
buildIssues and PRs related to Node.js builds or CI infrastructure.metaIssues and PRs related to the general management of the project.staleIssues and PRs marked stale due to inactivity and scheduled for automatic closure.

Description

@targos
targos
opened on Aug 12, 2021

See #39725 (comment)

The request-ci label was removed but the request-ci-failed label was not added.

I don't know what the Jenkins API responds in this case, but it doesn't seem like we handle it.

Workflow run: https://github.com/nodejs/node/runs/3296324085?check_suite_focus=true

Activity

  1. targos
    added
    buildIssues and PRs related to Node.js builds or CI infrastructure.
    metaIssues and PRs related to the general management of the project.
    on Aug 12, 2021

  2. targos commented on Aug 12, 2021

    @targos
    targos
    on Aug 12, 2021
    MemberAuthor

    @nodejs/actions

  3. richardlau commented on Aug 12, 2021

    @richardlau
    richardlau
    on Aug 12, 2021
    Member

    We should handle the error but during a CI lockdown I think it's expected that request-ci would not start CI's.

  4. targos commented on Aug 12, 2021

    @targos
    targos
    on Aug 12, 2021
    MemberAuthor

    during a CI lockdown I think it's expected that request-ci would not start CI's

    agreed

  5. richardlau commented on Oct 12, 2021

    @richardlau
    richardlau
    on Oct 12, 2021
    Member

    I'm fairly certain this is a node-core-utils issue.

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

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

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

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

No one assigned

    Labels

    buildIssues and PRs related to Node.js builds or CI infrastructure.metaIssues and PRs related to the general management of the project.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