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

Fix to #27155 - Average_Grouped_from_LINQ_101 is non-deterministic #28650

Merged
merged 1 commit into from
Aug 11, 2022

Conversation

maumar
Copy link
Contributor

@maumar maumar commented Aug 10, 2022

Added custom asserter that checks results within range, rather than adding sql server specific expected query.
For the second test, added proper collection asserter so we can impose the order within nested collection.

Fixes #27155

@maumar maumar requested review from a team and roji August 10, 2022 06:15
@ghost
Copy link

ghost commented Aug 10, 2022

Hello @maumar!

Because this pull request has the auto-merge label, I will be glad to assist with helping to merge this pull request once all check-in policies pass.

p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (@msftbot) and give me an instruction to get started! Learn more here.

@ghost
Copy link

ghost commented Aug 10, 2022

Apologies, while this PR appears ready to be merged, I've been configured to only merge when all checks have explicitly passed. The following integrations have not reported any progress on their checks and are blocking auto-merge:

  1. Azure Pipelines

These integrations are possibly never going to report a check, and unblocking auto-merge likely requires a human being to update my configuration to exempt these integrations from requiring a passing check.

Give feedback on this
From the bot dev team

We've tried to tune the bot such that it posts a comment like this only when auto-merge is blocked for exceptional, non-intuitive reasons. When the bot's auto-merge capability is properly configured, auto-merge should operate as you would intuitively expect and you should not see any spurious comments.

Please reach out to us at fabricbotservices@microsoft.com to provide feedback if you believe you're seeing this comment appear spuriously. Please note that we usually are unable to update your bot configuration on your team's behalf, but we're happy to help you identify your bot admin.

@roji roji removed the auto-merge label Aug 10, 2022
elementAsserter: (e, a) =>
{
AssertEqual(e.Category, a.Category);
Assert.InRange(a.AveragePrice, e.AveragePrice - 0.00005m, e.AveragePrice + 0.00005m);
Copy link
Member

Choose a reason for hiding this comment

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

Good solution, though xunit has Assert.Equal over double with an additional precision parameter we can use.

Added custom asserter that checks results within range, rather than adding sql server specific expected query
For the second test, added proper collection asserter so we can impose the order within nested collection.

Fixes #27155
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Average_Grouped_from_LINQ_101 is non-deterministic
2 participants