Open whesse opened 7 months ago
@elliette can you take a look at this debugger test flake?
The test is still failing on our builder, flakily, after we resume running it. The error is the same.
It could be that something is throwing an exception in the flutter code that is executed after the test runs, so that the async expect in the test is completing correctly, and waiting for the things it needs to, but there is still more happening in the app (maybe as part of shutdown?).
Builder that is failing is https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-linux-customer-testing/467/overview
Is there something that can be done to get more useful stack traces here. The stack trace is exactly the same as before. Shall we roll back the devtools tests in the customer test registry again? I think so.
Skipped the flaky test until we have a fix: https://github.com/flutter/tests/pull/344
The test "returns privates only from library" in packages/devtools_app/test/debugger/debugger_evaluation_test.dart is failing flakily on the builder https://ci.chromium.org/ui/p/dart/builders/ci.sandbox/flutter-linux-customer-testing
It is only this test that is failing, always with the same stack trace, and it is happening more than 10% of the time. The stack trace says that the test is failing and always has the message: "This test failed after it had already completed. | Make sure to use a matching library which informs the test runner | of pending async work."
This flakiness is affecting our CI, so if the problem with the test can't be fixed easily, it would be good to disable it until it can be fixed.
The full stack trace from the logs is: