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

Fix timeseries tests that rely on specific _id ordering

    • Type: Icon: Bug Bug
    • Resolution: Fixed
    • Priority: Icon: Major - P3 Major - P3
    • 8.2.0-rc0
    • Affects Version/s: None
    • Component/s: None
    • None
    • Storage Execution
    • Fully Compatible
    • ALL
    • Storage Execution 2025-03-17
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Initial list, searching failing timeseries tests for "control.*_id":

      • jstests/concurrency/fsm_workloads/random_moveChunk/random_moveChunk_timeseries_inserts.js
      • jstests/core/timeseries/ddl/bucket_timestamp_rounding.js
      • jstests/core/timeseries/ddl/timeseries_index.js
      • jstests/core/timeseries/query/timeseries_explain_delete.js
      • jstests/core/timeseries/query/timeseries_explain_update.js
      • jstests/core/timeseries/query/timeseries_lastpoint.js
      • jstests/core/timeseries/query/timeseries_lastpoint_common_sort_key.js
      • jstests/core/timeseries/write/timeseries_bucket_limit_count.js
      • jstests/core/timeseries/write/timeseries_bucket_limit_time_range.js
      • jstests/core/timeseries/write/timeseries_metadata.js
      • jstests/core/timeseries/write/timeseries_min_max.js
      • jstests/core/timeseries/write/timeseries_sparse.js
      • jstests/noPassthrough/timeseries/data_integrity/timeseries_partial_compressed_bucket.js
      • jstests/noPassthrough/timeseries/write/timeseries_large_measurements.js
      • jstests/noPassthrough/timeseries/write/timeseries_large_measurements_max_size.js

            Assignee:
            matt.kneiser@mongodb.com Matt Kneiser
            Reporter:
            matt.kneiser@mongodb.com Matt Kneiser
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved:
              None
              None
              None
              None