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

test(MR): run the fancier queue compatibility checks against mainnet #1149

Closed
wants to merge 3 commits into from

Conversation

oggy-dfin
Copy link
Member

No description provided.

@github-actions github-actions bot added the test label Aug 26, 2024
@oggy-dfin oggy-dfin marked this pull request as ready for review August 26, 2024 15:58
@oggy-dfin oggy-dfin requested review from a team as code owners August 26, 2024 15:58
TestCase::new(
TestType::Bidirectional {
published_binary: "replicated-state-test".to_string(),
mainnet_version: v.clone(),
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Merged this into my alin/MR-523-response-deduplication branch (#1071) and it fails in the same way it failed before #1105, because mainnet master still doesn't have that last change.

I would wait with this until #1105 is on mainnet master.

Otherwise LGTM, thanks for following up.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Ah. Let's not postpone your PR for 2 more weeks :)
But it is a maintenance burden that I didn't foresee with these comatibility tests, it takes a long time to get rid of mistakes in test cases.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yeah, turns out they're not only backward compatibility, but also forward compatibility tests. (o:

In this case because all the tests / test fixtures we wrote so far never bothered with unique CallbackIds. But in the future, it may also be the case that we expect canister queues to have certain properties (e.g. some field populated) before we can safely upgrade them. So not only an annoyance.

Copy link
Contributor

@nmattia nmattia left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Rubber stamp

@oggy-dfin
Copy link
Member Author

Already implemented by Alin at some point

@oggy-dfin oggy-dfin closed this Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants