OpenLiberty / OpenLiberty/open-liberty
MVT Server start process management problem
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.3k
- Forks
- 673
- Avg merge
- 3d 18h
- Merged PRs (30d)
- 90
Description
Test debt of #20215
The server start process may need to be terminated. This changes the process result code from 0 to 1.
A temporary code change was made to ignore the return code when the process was terminated.
open-liberty/dev/openliberty.build.image_fat/fat/src/com/ibm/ws/test/image/util/ProcessRunner.java
See com.ibm.ws.test.image.util.ProcessRunner.Result.validate
com.ibm.ws.test.image.util.ProcessRunner.run
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
Read openliberty.build.image_fat/fat/src/com/ibm/ws/test/image/util/ProcessRunner.java, starting with ProcessRunner.run and ProcessRunner.Result.validate. Trace how termination affects the process result code in the MVT server-start flow. Done means an intentionally terminated server-start process is handled with the expected result while genuine failures remain detectable.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- testing
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100