-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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 Subquery_with_Distinct_Skip_FirstOrDefault_without_OrderBy is non-deterministic #26353
Labels
area-test
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
Milestone
Comments
makes sense |
We can still use AssertQuery for ease of writing and add element asserter to skip the check of elements inside collection. |
I was thinking that too @smitpatel |
maumar
added a commit
that referenced
this issue
Oct 15, 2021
…ut_OrderBy is non-deterministic added way to order on the client on the top level but don't actually verify the subquery result, because its not deterministic. Fixes #26353
maumar
added a commit
that referenced
this issue
Oct 15, 2021
…ut_OrderBy is non-deterministic added way to order on the client on the top level but don't actually verify the subquery result, because its not deterministic. Fixes #26353
ghost
pushed a commit
that referenced
this issue
Oct 15, 2021
This issue was closed.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area-test
closed-fixed
The issue has been fixed and is/will be included in the release indicated by the issue milestone.
type-bug
It seems this test generates non-deterministic results by design (omitting OrderBy), and ordering on the client isn't an option here. Should we convert this test to not use AssertQuery?
/cc @maumar @smitpatel
The text was updated successfully, but these errors were encountered: