Test failure: Select_datetime_TimeOfDay_component

[ryanbrandenburg]

This test fails occasionally with the following error:

Assert.Equal() Failure
                                 ↓ (pos 41)
Expected: ···rftime('%H:%M:%f', "o"."OrderDate"), '0'), '.')\r\nFROM "Orders···
Actual:   ···rftime('%H:%M:%f', "c"."OrderDate"), '0'), '.')\r\nFROM "Orders···
                                 ↑ (pos 41)
   at Microsoft.EntityFrameworkCore.TestUtilities.TestSqlLoggerFactory.AssertBaseline(String[] expected, Boolean assertOrder)
   at Microsoft.EntityFrameworkCore.Query.SimpleQuerySqliteTest.AssertSql(String[] expected)
   at Microsoft.EntityFrameworkCore.Query.SimpleQuerySqliteTest.<Select_datetime_TimeOfDay_component>d__67.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)

Other tests within that build may have failed with a similar message, but they are not listed here. Check the link above for more info.

CC @ajcvickers

This issue was made automatically. If there is a problem contact @ryanbrandenburg.

[ryanbrandenburg]

Select_datetime_TimeOfDay_component failed with about the same error.
Please use this workflow to address this flaky test issue, including checking applicable checkboxes and filling in the applicable "TODO" entries:

• Is this actually a flaky test?

  • No, this is a regular test failure, fix the test/product (TODO: Link to commit/PR)
  • Yes, proceed below...

• Is this test failure caused by product code flakiness? (Either this product, or another product this test depends on.)

  • File a bug against the product (TODO: Link to other bug)
  • Is it possible to change the test to avoid the flakiness?
    • Yes? Go to the "Change the test!" section.
    • No?
      • Disable the test (TODO: Link to PR/commit)
      • Wait for other bug to be resolved
      • Wait for us to get build that has the fix
      • Re-enable our test (TODO: Link to PR/commit)
      • Close this bug

• Is it that the test itself is flaky? This includes external transient problems (e.g. remote server problems, file system race condition, etc.)

  • Is there is a way to change our test to avoid this flakiness?
    • Yes? Change the test!
      • Change the test to avoid the flakiness, for example by using a different test strategy, or by adding retries w/ timeouts (TODO: Link to PR/commit)
      • Run the test 100 times locally as a sanity check.
      • Close this bug
    • No?
      • Is there any logging or extra information that we could add to make this more diagnosable when it happens again?
        • Yes?
          • Add the logging (TODO: Link to PR/commit)
        • No?
          • Delete the test because flaky tests are not useful (TODO: Link to PR/commit)

This comment was made automatically. If there is a problem contact @ryanbrandenburg.

[ajcvickers]

@maumar to disable, or adapt the checking to allow either, based on idea that this happens based on order of test execution.

[smitpatel]

Fixed by #12971