Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Full tests and robustnes against frame ID wrapping for packet decoding #19

Open
wants to merge 7 commits into
base: k2is
Choose a base branch
from

Conversation

uellue
Copy link
Member

@uellue uellue commented Jun 23, 2021

Contributor Checklist:

  • I have added or updated my entry in the creators.json file
  • I have added a changelog entry for my contribution
  • I have added/updated documentation for all user-facing changes
  • I have added/updated test cases

Reviewer Checklist:

  • /azp run libertem.libertem-live-data passed

Do different partition and dataset scenarios that trigger carry situations
…f packets in wrapup

Make sure we catch near-range stragglers if there is unfinished work. That way we
"survive" massive scrambling within the range of one tile.

Adapt test cases accordingly; also test dups which is trivial.
Use a "virtual corrected frame ID" and correct wrap already during decoding.
Wrapping is detected directly after processing packets and is corrected as early as possible.

To not get mixed up in "old" and "new" epoch, the decoded header is stored
in the carry buffers.
@uellue
Copy link
Member Author

uellue commented Jun 23, 2021

/azp run libertem.libertem-live-data

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@uellue uellue requested a review from sk1p June 23, 2021 17:55
Test for wrapping was flaky for 128 scrambling,
test it only for less aggressive scrambling.

In reality, inconsistencies in the data stream are rare,
and the packets are almost always in order, so jump
detection will work with high reliablity.
Also fix comments from before

The tests are still flaky sometimes, more work to be done
@sk1p
Copy link
Member

sk1p commented Jul 19, 2021

As a note, there is still a flaky test in this PR which we want to fix before it can be merged.

@sk1p sk1p changed the title Full tests and robustnes against frame ID wrapping for packet decoding WIP: Full tests and robustnes against frame ID wrapping for packet decoding Jul 19, 2021
* Account for stragglers in test
* Refine test matrix to exclude combinations that can "trip"
  the packet reordering. The test is already much harder than the actual data stream,
  which is almost always in order and complete with only very few
  missing, scrambled or duplicate packets.
@uellue uellue changed the title WIP: Full tests and robustnes against frame ID wrapping for packet decoding Full tests and robustnes against frame ID wrapping for packet decoding Jul 22, 2021
@uellue
Copy link
Member Author

uellue commented Jul 22, 2021

/azp run libertem.libertem-live-data

@azure-pipelines
Copy link

Azure Pipelines could not run because the pipeline triggers exclude this branch/path.

@uellue
Copy link
Member Author

uellue commented Jul 22, 2021

The k2is branch should be rebased to current master for tests to work -- setup.py is broken, etcetc

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants