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

Add scan_start_where_left test to CI #8085

Closed
Tracked by #7728
oxarbitrage opened this issue Dec 11, 2023 · 0 comments · Fixed by #8172
Closed
Tracked by #7728

Add scan_start_where_left test to CI #8085

oxarbitrage opened this issue Dec 11, 2023 · 0 comments · Fixed by #8172
Assignees
Labels
A-blockchain-scanner Area: Blockchain scanner of shielded transactions

Comments

@oxarbitrage
Copy link
Contributor

In #8080 we are adding a test called scan_start_where_left. This test uses a synchronized state so it is marked as ignored. We want to run this test in the CI in a similar way we do with other ignored tests.

This is blocked until #8080 is merged.

@oxarbitrage oxarbitrage added S-blocked Status: Blocked on other tasks A-blockchain-scanner Area: Blockchain scanner of shielded transactions labels Dec 11, 2023
@mpguerra mpguerra added this to Zebra Dec 11, 2023
@github-project-automation github-project-automation bot moved this to 🆕 New in Zebra Dec 11, 2023
@mpguerra mpguerra removed the S-blocked Status: Blocked on other tasks label Jan 17, 2024
@mpguerra mpguerra moved this from New to Sprint Backlog in Zebra Jan 17, 2024
@upbqdn upbqdn self-assigned this Jan 18, 2024
@mpguerra mpguerra moved this from Sprint Backlog to Review/QA in Zebra Jan 19, 2024
@mergify mergify bot closed this as completed in #8172 Jan 23, 2024
@github-project-automation github-project-automation bot moved this from Review/QA to Done in Zebra Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-blockchain-scanner Area: Blockchain scanner of shielded transactions
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

3 participants