Uploaded image for project: 'Apache Arrow'
  1. Apache Arrow
  2. ARROW-4009

[CI] Run Valgrind and C++ code coverage in different bulds

    XMLWordPrintableJSON

Details

    Description

      Currently, we run Valgrind on a coverage-enabled C++ build on Travis-CI. This means the slowness of Valgrind acts as a multiplier of the overhead of outputting coverage information using the instrumentation added by the compiler.

      Instead we should probably emit C++ (and Python) coverage information in a different Travis-CI build without Valgrind enabled.

      Attachments

        Issue Links

          Activity

            People

              apitrou Antoine Pitrou
              apitrou Antoine Pitrou
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Time Tracking

                  Estimated:
                  Original Estimate - Not Specified
                  Not Specified
                  Remaining:
                  Remaining Estimate - 0h
                  0h
                  Logged:
                  Time Spent - 1h 20m
                  1h 20m