Uploaded image for project: 'Core Server'
  1. Core Server
  2. SERVER-42753

Ensure libfuzzer evergreen tasks always upload their corpus

    XMLWordPrintable

    Details

    • Type: Improvement
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 4.3.1
    • Component/s: None
    • Labels:
      None
    • Backwards Compatibility:
      Fully Compatible
    • Sprint:
      Security 2019-08-12, Security 2019-08-26

      Description

      Currently the libfuzzer task uploads its corpus as a normal function in the task rather than part of the teardown tasks in the task group. This means that if libfuzzer fails, it doesn't upload its corpus to s3 afterwards - loosing all the information it gained during the failed run.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              jonathan.reams Jonathan Reams
              Reporter:
              jonathan.reams Jonathan Reams
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: