-
-
Notifications
You must be signed in to change notification settings - Fork 7.5k
CI: reduce build time for Travis valgrind #1836
Copy link
Copy link
Closed
Labels
kind: bugstate: stalethe issue has not been updated in a while and will be closed automatically soon unless it is updatedthe issue has not been updated in a while and will be closed automatically soon unless it is updated
Description
Activity
Metadata
Metadata
Assignees
Labels
kind: bugstate: stalethe issue has not been updated in a while and will be closed automatically soon unless it is updatedthe issue has not been updated in a while and will be closed automatically soon unless it is updated
On Travis CI, the current build time for Valgrind job is ~45 minutes which is close to 50 min limit. Hence, a timeout can be triggered when build machines are on heavy load or more tests are added in future.
By skimming through the build log, these unit-tests are the major culprits by spending a lot of time:
The first three tests takes a long time only on their
*_valgrindbuild mode. This is probably due to high number of memory allocations which makes the job of valgrind harder to check for memory leaks.The
test-unicode_alltest however is infamous for taking lot of time to run.The build time for Valgrind job should be reduced to a reasonable value so it does't fail occasionally. This can be done by either skipping some redundant unit-tests, or optimizing them, or requesting a bigger time limit from Travis for this project.
Which compiler and operating system are you using? Is it a supported compiler?
Did you use a released version of the library or the version from the
developbranch?If you experience a compilation error: can you compile and run the unit tests?