Uploaded image for project: 'Evergreen'
  1. Evergreen
  2. EVG-13713

If evergreen version aborts without failing, status is pending

    XMLWordPrintable

Details

    • Bug
    • Status: Closed
    • Major - P3
    • Resolution: Won't Do
    • None
    • None
    • app

    Description

      https://spruce.mongodb.com/version/5fe3acf8d6d80a1047aebe18/tasks did not post some kind of status to the GitHub API. I suspect a subsequent version caught it in just the right state that nothing was aborted, causing nothing to fail, which caused the version to not be marked failed (which typically happens in an abort), which in turn caused that one status check to be perpetually in a pending state.

      This prevented the user from using the commit queue, because they have branch protection set for "evergreen", and that check was perpetually in the pending state. Should we mark a version failed when it aborts regardless of whether any individual task fails?

      Attachments

        Issue Links

          Activity

            People

              backlog-server-evg Backlog - Evergreen Team
              brian.samek@mongodb.com Brian Samek
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: