[WIP] Further identifiers in tests #56
Closed
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the ✨ Finishing Touches🧪 Generate unit tests
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
SupportNeed help? Create a ticket on our support page for assistance with any issues or questions. CodeRabbit Commands (Invoked using PR/Issue comments)Type Other keywords and placeholders
CodeRabbit Configuration File (
|
lawrence-forooghian
force-pushed
the
ECO-5465-enable-disabled-integration-tests
branch
from
e2a78f7 to
c4bab5f
Compare
Base automatically changed from
ECO-5465-enable-disabled-integration-tests
to
main
August 13, 2025 10:56
lawrence-forooghian
changed the base branch from
main
to
ECO-5535-remove-batch-api
lawrence-forooghian
force-pushed
the
further-identifiers-in-tests
branch
from
ae9d9aa to
f3011cf
Compare
This allows us to use "run repeatedly" without the runs interfering with each other. wip adding test UUID to logs this isn't quite right — we need to be able to do client2 and have the ID there too (probably should bake the test into the context) also Test overlaps with Swift Testing terminology now
lawrence-forooghian
force-pushed
the
further-identifiers-in-tests
branch
2 times, most recently
from
33e2edf to
08639a8
Compare
lawrence-forooghian
force-pushed
the
further-identifiers-in-tests
branch
from
08639a8 to
e21ad82
Compare
- number of concurrent Realtime instances - when monitorConnectionThenCloseAndFinishAsync fails (to see whether it's actually failing the test when it should be)
asked Cursor to write this trait that limits concurrency this is because there seem to be issues with running concurrent tests (hangs, and failures that I think are because of it exercising edge cases in the tests, but also Realtime's "Error 40111 - account restricted (connection limit exceeded)" and connection timeouts) my logging suggests that we have up to 100 Realtime instances active at a time I was going to just make things .serialized for now but that makes the test suite really slow (like 4 minutes) so I hoped we could find a middle ground I tried making it a suite trait that has isRecursive: true (which I thought was the default which is why I made those earlier changes to the fixtures trait) but it doesn't seem to be. I've however observed this hanging at least once locally so won't be taking this forward for now (need to get the test suite fixed and have a time pressure)
Mistake in 70306a0. Correct approach copied from "Objects.createCounter sends COUNTER_CREATE operation" test.
Wait until we're sure that GC of an entry should have occurred, regardless of clock skew. Also fix what may have been a bug in 792683d where we may not wait for as many GC cycles as we intended to (because of counting AsyncStream buffered values).
lawrence-forooghian
force-pushed
the
further-identifiers-in-tests
branch
from
e21ad82 to
478f957
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Some handy stuff for debugging tests; needs tidying up