Laplace tests taking too long in `develop` Jenkins runs
Open
Nobody has claimed this yet.
continuous integration
- Dominant language
- C++
- Stars
- 839
- Forks
- 220
- Avg merge
- 2d 4h
- Merged PRs (30d)
- 14
Description
Nearly 10 hours in just that one step. They only take 30 minutes for PRs, because we don't run ASAN.
For develop, should we:
- not run ASAN?
- Split across more than one executor?
I don't believe it was this bad before #3250 cc @SteveBronder
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the linked Jenkins develop build 405/pipeline/198 and compare its ASAN Laplace step with a PR run; inspect the change in #3250 for context. Done means an agreed CI configuration that avoids the roughly 10-hour step without dropping required validation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- ci-cd, performance, testing-qa
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100