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

Code Coverage build variants in Evergreen still aren't archiving code coverage data

XMLWordPrintableJSON

    • Fully Compatible
    • ALL
    • Dev Platform 2022-05-30, Dev Platform 2022-06-13

      I looked over recent code coverage builds and didn't see a tarball containing the code coverage data being uploaded to S3. An error message in the task logs suggests at least some part of the issue is an Evergreen expansion not being set.

      [2022/05/01 05:29:40.175] Running command 'subprocess.exec' in "save code coverage data" (step 11.2 of 22)
[2022/05/01 05:29:40.176] No coverage tool defined. Set the gcov_tool expansion in evergreen.yml
[2022/05/01 05:29:40.176] Command failed: error waiting on process '7d86f7a4-6375-4466-9488-a43a1252029f': exit status 1

      However, even prior to the changes from 05ea833 as part of SERVER-63055, it doesn't look like there's a "gcov intermediate files" tarball. For some reason there's a "Hang Analyzer Output" tarball containing one of the .gcda files though.

      % tar -tf ~/Downloads/mongo-hanganalyzer-mongodb_mongo_master_enterprise_rhel_80_64_bit_coverage_v4gcc_57b670b4df8b5ad731306a811500b46c9e71a0e9_22_03_26_15_32_54-jsCore-0.tgz
debugger.gcda.gcov.json.gz

      https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_80_64_bit_coverage_v4gcc_jsCore_57b670b4df8b5ad731306a811500b46c9e71a0e9_22_03_26_15_32_54

            Assignee:
            ryan.egesdahl@mongodb.com Ryan Egesdahl (Inactive)
            Reporter:
            max.hirschhorn@mongodb.com Max Hirschhorn
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated:
              Resolved: