DUNE-DAQ / DUNE-DAQ/integrationtest
Think about how `check_fragment_sizes` should work
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 0
- Forks
- 2
- Avg merge
- 1m
- Merged PRs (30d)
- 1
Description
Right now, check_fragment_sizes works by taking a minimum and maximum value for the Fragment size and making sure that the actual Fragment size is between those two values. It may make more sense to define it in terms of "expected_fragment_size", "chunk_size", and "chunk_tolerance", where the tolerance would default to one or two chunk(s) to account for trigger edge effects.
Contributor guide
No contributing guide indexed for this repository
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
Start by locating check_fragment_sizes and its pytest callers in the integration-test helpers. Clarify whether expected_fragment_size, chunk_size, and chunk_tolerance should replace the current minimum and maximum inputs, including the default tolerance; done means the intended semantics and edge-effect behavior are agreed and covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100