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

[antithesis] Ensure workload assertions compatible with successful execution #3102

Open
marun opened this issue Jun 10, 2024 · 2 comments
Open
Assignees
Labels
lifecycle/stale testing This primarily focuses on testing

Comments

@marun
Copy link
Contributor

marun commented Jun 10, 2024

#3059 added support for SDK assertions but the antithesis jobs are currently reporting errors. Need to get the jobs passing.

@marun marun self-assigned this Jun 10, 2024
@marun marun converted this from a draft issue Jun 10, 2024
@marun marun changed the title [antithesis] Complete transition to SDK assertions [antithesis] Ensure workload assertions compatible with successful execution Jun 10, 2024
@marun marun added the testing This primarily focuses on testing label Jun 10, 2024
@marun marun moved this from Researching 📚 to In Progress 🏗 in Platform Engineering Group Jun 12, 2024
@marun
Copy link
Contributor Author

marun commented Jun 20, 2024

Jobs are mostly passing with the merge of #3104, but in recent reports the following errors have occurred:

  • failure to see deleted UTXOs (local wallet issue?)
  • failed to calculate expected proposer (haven't seen this before)

@marun marun moved this from In Progress 🏗 to Backlog 🗄️ in Platform Engineering Group Jul 10, 2024
Copy link

github-actions bot commented Sep 1, 2024

This issue has become stale because it has been open 60 days with no activity. Adding the lifecycle/frozen label will cause this issue to ignore lifecycle events.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale testing This primarily focuses on testing
Projects
Status: Backlog 🗄️
Development

No branches or pull requests

1 participant