Is the grinder doing more work than required?
- Dominant language
- HTML
- Stars
- 155
- Forks
- 346
- Avg merge
- 2d 9h
- Merged PRs (30d)
- 36
Description
**Describe the bug**
I started a grinder using "NodesByIterations" on 5 machines. The parent job loads all the repos and downloads the JVM, only to create 5 child jobs that actually runs the testing. It seems loading the repos and downloading the JVM in the parent job is a waste of time.
https://openj9-jenkins.osuosl.org/job/Grinder/1292/console
**To Reproduce**
Steps to reproduce the behavior (or Grinder rerun link):
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Additional context**
Add any other context about the problem here.
Contributor guide
Research direction
Start with the linked Grinder/1292 console log and trace how NodesByIterations creates the parent and five child jobs. Compare the setup work performed in each job, especially repository loading and JVM download. Done means the redundant parent setup is removed or avoided while the child jobs still run their tests correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100