| Summary: | Patches to let test suite run in parallel | ||
|---|---|---|---|
| Product: | [Developer tools] valgrind | Reporter: | Thomas Rast <trast> |
| Component: | general | Assignee: | Julian Seward <jseward> |
| Status: | REPORTED --- | ||
| Severity: | wishlist | CC: | mark, sam |
| Priority: | NOR | ||
| Version First Reported In: | 3.9.0.SVN | ||
| Target Milestone: | --- | ||
| Platform: | Compiled Sources | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
| Attachments: |
Mass-edit massif tests to use unique output names
{call,cache}grind/tests: use 'rm -f' to clean up Execute tests after scanning, from toplevel directory Implement threaded regression tests regtests: use forks instead of threads |
||
|
Description
Thomas Rast
2013-05-04 10:23:52 UTC
Created attachment 79692 [details]
Mass-edit massif tests to use unique output names
Created attachment 79693 [details]
{call,cache}grind/tests: use 'rm -f' to clean up
Created attachment 79694 [details]
Execute tests after scanning, from toplevel directory
Created attachment 79695 [details]
Implement threaded regression tests
Created attachment 79696 [details]
regtests: use forks instead of threads
PS: the third patch actually fixes a directory-changing related bug by no longer changing dirs. If you do this in the current test suite:
$ perl tests/vg_regtest none/tests/amd64 memcheck
it fails to run any memcheck tests:
-- Finished tests in none/tests/amd64 ----------------------------------
`memcheck' neither a directory nor a readable test file/name
This happens because the recursion code uses 'chdir("..")' to go back one level, which is not sufficient if it was called to go more than one level deep (as in the none/tests/amd64 case).
|