Uploaded image for project: 'Parquet'
  1. Parquet
  2. PARQUET-1385

[C++] bloom_filter-test is very slow under valgrind

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Resolved
    • Major
    • Resolution: Duplicate
    • None
    • None
    • parquet-cpp

    Description

      This test takes ~5 minutes to run under valgrind in Travis CI

      1: [==========] Running 6 tests from 6 test cases.
      1: [----------] Global test environment set-up.
      1: [----------] 1 test from Murmur3Test
      1: [ RUN      ] Murmur3Test.TestBloomFilter
      1: [       OK ] Murmur3Test.TestBloomFilter (19 ms)
      1: [----------] 1 test from Murmur3Test (34 ms total)
      1: 
      1: [----------] 1 test from ConstructorTest
      1: [ RUN      ] ConstructorTest.TestBloomFilter
      1: [       OK ] ConstructorTest.TestBloomFilter (101 ms)
      1: [----------] 1 test from ConstructorTest (101 ms total)
      1: 
      1: [----------] 1 test from BasicTest
      1: [ RUN      ] BasicTest.TestBloomFilter
      1: [       OK ] BasicTest.TestBloomFilter (49 ms)
      1: [----------] 1 test from BasicTest (49 ms total)
      1: 
      1: [----------] 1 test from FPPTest
      1: [ RUN      ] FPPTest.TestBloomFilter
      1: [       OK ] FPPTest.TestBloomFilter (308731 ms)
      1: [----------] 1 test from FPPTest (308741 ms total)
      1: 
      1: [----------] 1 test from CompatibilityTest
      1: [ RUN      ] CompatibilityTest.TestBloomFilter
      1: [       OK ] CompatibilityTest.TestBloomFilter (62 ms)
      1: [----------] 1 test from CompatibilityTest (62 ms total)
      1: 
      1: [----------] 1 test from OptimalValueTest
      1: [ RUN      ] OptimalValueTest.TestBloomFilter
      1: [       OK ] OptimalValueTest.TestBloomFilter (27 ms)
      1: [----------] 1 test from OptimalValueTest (27 ms total)
      1: 
      1: [----------] Global test environment tear-down
      1: [==========] 6 tests from 6 test cases ran. (309081 ms total)
      1: [  PASSED  ] 6 tests.
      

      Either we should change the FPPTest parameters to be faster, or we should not run that test when using valrind

      Attachments

        Issue Links

          Activity

            People

              Unassigned Unassigned
              wesm Wes McKinney
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: