• Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Major Major
    • pipeline

      There are too many @RandomlyFails tests. SemaphoreStep should be used more consistently in place of WatchYourStep and waiting for the execution to suspend. (Already prototyped in WorkflowTest.env.)

      Also any build logs should be streamed immediately to stderr, rather than forcing the test to include the current log in every assertion message observed to fail. (In combination with SemaphoreStep, this should also more reliably flush recent output: WorkflowRun flushes logs when new steps are run.)

          [JENKINS-25975] More reliable test infrastructure

          Jesse Glick created issue -
          Jesse Glick made changes -
          Status Original: Open [ 1 ] New: In Progress [ 3 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 59 (Web Link)" [ 12125 ]
          Jesse Glick made changes -
          Remote Link New: This issue links to "PR 92 (Web Link)" [ 12166 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26398 [ JENKINS-26398 ]
          Jesse Glick made changes -
          Link New: This issue is related to JENKINS-26399 [ JENKINS-26399 ]
          SCM/JIRA link daemon made changes -
          Resolution New: Fixed [ 1 ]
          Status Original: In Progress [ 3 ] New: Resolved [ 5 ]
          R. Tyler Croy made changes -
          Workflow Original: JNJira [ 159963 ] New: JNJira + In-Review [ 196260 ]
          Andrew Bayer made changes -
          Component/s New: pipeline-general [ 21692 ]
          Andrew Bayer made changes -
          Component/s Original: workflow-plugin [ 18820 ]

            jglick Jesse Glick
            jglick Jesse Glick
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: