Dealing with the `needsTuning` occurrences

Open
#307 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
haskell
Domain
testing

Research direction

Search the test suite for all needsTuning occurrences and inspect the tests excluded from certain runs. Reproduce the intermittent failures to determine their causes, then verify the affected tests are reliable and no longer need precautionary exclusion.

Written by the indexing model from the issue text.

Description

petri testing

There are currently tests that sometimes fail for so far unknown reasons. They are excluded from certain test runs as a precautionary measure. It would be better to address them heads on.

Dominant language
Haskell
Stars
0
Forks
3
Avg merge
2d 16h
Merged PRs (30d)
5

Getting set up

  • No Dockerfile or Docker Compose file
  • Has a pull request template
  • No 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 fmidue/modelling-tasks

All issues in fmidue/modelling-tasks

Similar issues

More Haskell issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.