Verify that the scheduler releases simulation engines before they go out of scope

Open
#1,335 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
java
Domain
testing

Research direction

Start by reviewing issue #1237 and the scheduler tests that replaced the removed repeated-scheduling test. Trace how simulation engines are allocated and released, then restore coverage showing that repeated scheduling does not exceed the thread-allocation threshold. Done means the regression test passes and verifies engines are released before going out of scope.

Written by the indexing model from the issue text.

Description

scheduling

#1237 removes a test that would run scheduling repeatedly and assert that the number of allocated threads never exceeded a given threshold. This ticket is to track that gap in testing.

Dominant language
Java
Stars
128
Forks
33
Avg merge
1d 17h
Merged PRs (30d)
12

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from NASA-AMMOS/plandev

All issues in NASA-AMMOS/plandev

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.