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

Evergreen interprets adding a new test as deleting a new test and doesn't generate burn in tests

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Duplicate
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: Testing Infrastructure
    • Labels:
    • Operating System:
      ALL

      Description

      In this patch build I added a new jstest which I would expect to get run in burn_in_tests, but it seems like burn_in_tests_gen interpreted it as removing the test instead of adding it:

      [2020/03/31 20:07:34.537] [2020-03-31 20:07:34,537 - buildscripts.patch_builds.change_data - DEBUG] 2020-03-31 20:07.34 deleted files                  diff=index diff files={'jstests/sharding/shard_removal_triggers_catalog_cache_invalidation.js'}
      

      Which led to no burn_in_tests getting run.

      Note that this was in 4.2, I don't know if the issue is on all branches.

        Attachments

          Activity

            People

            Assignee:
            backlog-server-dag Backlog - Decision Automation Group (DAG)
            Reporter:
            matthew.saltz Matthew Saltz
            Participants:
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Dates

              Created:
              Updated:
              Resolved: