investigate long running evergreen tasks

XMLWordPrintableJSON

    • Type: Improvement
    • Resolution: Gone away
    • Priority: Major - P3
    • None
    • Affects Version/s: None
    • Component/s: Testing Infrastructure
    • None
    • DAG 2022-04-18, DAG 2022-05-16
    • None
    • 3
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      I was investigating some timeouts in evergreen and noticed some pretty long running tasks. It would be nice to investigate if there is anything that can be done to reduce the runtime of these tasks.

      ubuntu1804-debug-asan:
      - multi_shard_local_read_write_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - multi_shard_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - aggregation_secondary_reads (4.6 hours)
      ubuntu1804-debug-asan-classic-engine:
      - multi_shard_local_read_write_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - multi_shard_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - aggregation_secondary_reads (4.6 hours)
      ubuntu1804-sbe-yielding-debug:
      - concurrency_replication_ubsan (2 hours)
      enterprise-windows-cxx20-debug-experimental:
      - causally_consistent_hedged_reads_jscore_passthrough (4.6 hours)
      - aggregation_secondary_reads (4.2 hours)
      - concurrency_replication (4.2 hours)
      ubuntu1804-debug-asan-all-feature-flags:
      - multi_shard_local_read_write_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - multi_shard_multi_stmt_txn_jscore_passthrough (5.5 hours)
      - aggregation_secondary_reads (4.6 hours)
      enterprise-rhel-80-64-bit-future-git-tag-multiversion:
      - replica_sets_multiversion (12 hours)
      

            Assignee:
            Robert Guo (Inactive)
            Reporter:
            David Bradford (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

              Created:
              Updated:
              Resolved: