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

Validation failure does not cause test to fail

    XMLWordPrintable

    Details

    • Backwards Compatibility:
      Fully Compatible
    • Operating System:
      ALL
    • Sprint:
      TIG 2018-09-24

      Description

      Here's an evergreen build from the waterfall:
      https://evergreen.mongodb.com/task/mongodb_mongo_master_enterprise_rhel_62_64_bit_noPassthroughWithMongod_67ab3ae97432353dea52c74fcc5982ea4d4d7ae6_18_09_18_17_22_50

      Take a look at the test all_paths_index_multikey.js

      The test passes:
      https://logkeeper.mongodb.org/lobster/build/d2e22b32dd16074741aac2c64787c330/test/5ba165d3be07c460f901a988#bookmarks=0%2C74

      But validation fails:
      https://logkeeper.mongodb.org/lobster/build/d2e22b32dd16074741aac2c64787c330/test/5ba165def84ae80c2001a1d6#bookmarks=0%2C124

      Yet the test is not marked as a failure. The same happens if you run it in resmoke locally (the test is marked as successful, but validation fails). This is a pretty serious problem because it means collection validation could be failing for more severe reasons without our knowing.

        Attachments

          Issue Links

            Activity

              People

              Assignee:
              max.hirschhorn Max Hirschhorn
              Reporter:
              ian.boros Ian Boros
              Participants:
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Dates

                Created:
                Updated:
                Resolved: