Start jobs in their own processes
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 20
- Forks
- 17
- PR merge metrics
- No merged PRs in 30d
Description
_Saturday Mar 07, 2020 at 02:41 GMT_
_Originally opened as https://github.com/facebookincubator/contest/issues/71_
----
Each jobs has its own process. This has the following benefits:
* **Failure isolation**: If a test panics unexpectedly (for example it runs out of memory), only that test is affected and not the whole system.
* **Cancel jobs**: Allow jobs to be force cancelled simply by killing the process.
* **Resource limits**: Each job can have its own limits on memory, fds, cpu, etc...
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
No files, tests, or entry points are named. Start by tracing how jobs are currently started and managed, then determine the process-isolation design needed for failure handling, cancellation, and per-job resource limits; done means each job runs independently with those capabilities.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- testing
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100