Skip to content

Automatic CI does not always work #1833

Closed
Closed
Automatic CI does not always work#1833

Description

@BridgeAR
BridgeAR
opened on Jun 12, 2019

At the moment our CI often replies with Sadly, an error occurred when I tried to trigger a build. :(. If I am correct the lite CI job is not triggered anymore.

There was definitely a recent update to the bot since it now updates the latest post with the latest CI run instead of posting new entries every time. I guess that is related?

Activity

  1. BridgeAR commented on Jun 12, 2019

    @BridgeAR
    BridgeAR
    on Jun 12, 2019
    MemberAuthor

    Refs: nodejs/node#28181 (comment)

  2. richardlau commented on Jun 12, 2019

    @richardlau
    richardlau
    on Jun 12, 2019
    Member

    See nodejs/github-bot#235 for ongoing investigation.

  3. rvagg commented on Jun 12, 2019

    @rvagg
    rvagg
    on Jun 12, 2019
    Member

    closing in favour of nodejs/github-bot#235, I don't think we have anything new on it unfortunately

  4. rvagg
    closed this as completedon Jun 12, 2019
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