Uploaded image for project: 'WiredTiger'
  1. WiredTiger
  2. WT-5105

Valgrind takes too long on test_wt2535_insert_race

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major - P3
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: WT3.2.2
    • Component/s: None
    • Labels:
      None
    • Story Points:
      1
    • Sprint:
      Storage Engines 2019-09-09

      Description

      With the change for WT-4966, valgrind can now make progress beyond the test/csuite/import directory. It is currently hanging on test/csuite/wt2535_insert_race.

      Looking on tinderbox, the process has consumed a ton of time:

      jenkins  18768  102  2.3 1414808 1149160 ?     Sl   Sep04 601:43 valgrind --tool=memcheck --leak-check=full --num-callers=20 --undef-value-errors=yes --track-origins=yes --child-silent-after-fork=yes --fair-sched=try --xml=yes --xml-file=/home/jenkins/jenkins/workspace/wiredtiger-valgrind/%p.memcheck ./test_wt2535_insert_race
      

      Given it has run over 600 minutes, that test should be skipped for valgrind (similar to the way test/csuite/wt2853_perf/main.c and others skip with valgrind).

      Until that change is in, valgrind will continue to hang on that test.

        Attachments

          Activity

            People

            • Assignee:
              sue.loverso Susan LoVerso
              Reporter:
              sue.loverso Susan LoVerso
            • Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: