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

release-22.2: changefeedccl: fix flakey tests #92716

Closed

Conversation

blathers-crl[bot]
Copy link

@blathers-crl blathers-crl bot commented Nov 30, 2022

Backport 1/1 commits from #92341 on behalf of @HonoreDB.

/cc @cockroachdb/release


Our test SQL connection doesn't always read its own writes: it can use different connections for different queries. So

INSERT INTO foo;
feed(CREATE CHANGEFEED FOR foo)

is a race condition. This just doesn't matter for most tests because if the insert happens after the initial scan, it creates the same payload. But tests with initial_scan='only' won't see it at all.

Fixes #92211

Release note: None


Release justification: Test-only change.

Our test SQL connection doesn't always read its own writes:
it can use different connections for different queries.
So
```
INSERT INTO foo;
feed(CREATE CHANGEFEED FOR foo)
```
is a race condition. This just doesn't matter for most tests
because if the insert happens after the initial scan, it creates
the same payload. But tests with initial_scan='only' won't see it
at all.

Fixes #92211

Release note: None
@blathers-crl blathers-crl bot requested a review from a team as a code owner November 30, 2022 02:31
@blathers-crl blathers-crl bot requested review from stevendanna and removed request for a team November 30, 2022 02:31
@blathers-crl blathers-crl bot force-pushed the blathers/backport-release-22.2-92341 branch from adb7f35 to bfba8f7 Compare November 30, 2022 02:31
@blathers-crl
Copy link
Author

blathers-crl bot commented Nov 30, 2022

Thanks for opening a backport.

Please check the backport criteria before merging:

  • Patches should only be created for serious issues or test-only changes.
  • Patches should not break backwards-compatibility.
  • Patches should change as little code as possible.
  • Patches should not change on-disk formats or node communication protocols.
  • Patches should not add new functionality.
  • Patches must not add, edit, or otherwise modify cluster versions; or add version gates.
If some of the basic criteria cannot be satisfied, ensure that the exceptional criteria are satisfied within.
  • There is a high priority need for the functionality that cannot wait until the next release and is difficult to address in another way.
  • The new functionality is additive-only and only runs for clusters which have specifically “opted in” to it (e.g. by a cluster setting).
  • New code is protected by a conditional check that is trivial to verify and ensures that it only runs for opt-in clusters.
  • The PM and TL on the team that owns the changed code have signed off that the change obeys the above rules.

Add a brief release justification to the body of your PR to justify this backport.

Some other things to consider:

  • What did we do to ensure that a user that doesn’t know & care about this backport, has no idea that it happened?
  • Will this work in a cluster of mixed patch versions? Did we test that?
  • If a user upgrades a patch version, uses this feature, and then downgrades, what happens?

@blathers-crl blathers-crl bot added blathers-backport This is a backport that Blathers created automatically. O-robot Originated from a bot. labels Nov 30, 2022
@cockroach-teamcity
Copy link
Member

This change is Reviewable

@github-actions
Copy link

Reminder: it has been 3 weeks please merge or close your backport!

@HonoreDB
Copy link
Contributor

HonoreDB commented Jan 9, 2023

bors retry

@github-actions
Copy link

Reminder: it has been 3 weeks please merge or close your backport!

@stevendanna
Copy link
Collaborator

Taking the liberty to close.

@stevendanna stevendanna closed this Oct 3, 2023
@rafiss rafiss deleted the blathers/backport-release-22.2-92341 branch December 11, 2023 16:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blathers-backport This is a backport that Blathers created automatically. no-backport-pr-activity O-robot Originated from a bot.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants