Uploaded image for project: 'Data Management'
  1. Data Management
  2. DM-11692

artifact stack-os-matrix build .log files

    XMLWordPrintable

    Details

    • Type: Story
    • Status: Done
    • Resolution: Done
    • Fix Version/s: None
    • Component/s: Continuous Integration
    • Labels:
      None

      Description

      Post merger of DM-11612, junit xml files have been recorded with a non-zero failure count even though the build completed successfully. There is concern that there is a failure mode in which pytest observes a test failure but exists 0 (confirmed in DM-11693).

      As the build is successful, lsstswBuild.sh's log printing is not triggered. It would be useful for debugging purposes to unconditionally artifact all of the build's *.log files. Tangentially, saving all of the log files would mean that lsstswBuild.sh's could be invoked without the --print-fail, possibly removing the need to address DM-5887.

        Attachments

          Issue Links

          is triggered by

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-11612 add junit test reporting to jenkins stack-os-matrix job

          • Done
          is triggering

          Bug - A problem which impairs or prevents the functions of the product. DM-11734 last step in finally block incorrectly reported as failed

          • To Do
          relates to

          Bug - A problem which impairs or prevents the functions of the product. DM-11693 Rebuild runs pytest tests twice for every product

          • Done

          Story - Created by Jira Software - do not edit or delete. Issue type for a user story. DM-5887 lsstswBuild.sh --print-fail flag broken

          • Done

            Activity

            Ascending order - Click to sort in descending order
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment -

            While tracking down a problem with the first archiving attempt, I discovered that pipeline will incorrectly label the last step in a finally block as failed if an exception is raised in the try block.

            https://issues.jenkins-ci.org/browse/JENKINS-46551

            Show
            jhoblitt Joshua Hoblitt added a comment - While tracking down a problem with the first archiving attempt, I discovered that pipeline will incorrectly label the last step in a finally block as failed if an exception is raised in the try block. https://issues.jenkins-ci.org/browse/JENKINS-46551
            Hide
            Permalink
            jhoblitt Joshua Hoblitt added a comment -

            The third attempt (exception handling needed to be reworked twice) appears to be working as expected in the production jenkins instance.

            Show
            jhoblitt Joshua Hoblitt added a comment - The third attempt (exception handling needed to be reworked twice) appears to be working as expected in the production jenkins instance.

              People

              Assignee:
              jhoblitt Joshua Hoblitt
              Reporter:
              jhoblitt Joshua Hoblitt
              Watchers:
              Joshua Hoblitt, Tim Jenness
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved:

                  Jenkins

                  No builds found.