-
Notifications
You must be signed in to change notification settings - Fork 29.8k
Description
We have a number of tests set up to fail when there is unexpected output on stderr. It looks like the flag to disable analytics was recently renamed, which is causing this to be printed to stderr:
[run_debug_test_linux] [STDOUT] run:stderr: `--[no-]analytics` is deprecated. Use `--suppress-analytics` to disable analytics for one run instead.
(From https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20run_debug_test_linux/421/overview).
It looks like the flag is not being passed, or the new misspelling is being ignored on the second run, so our CI is interpreting this as a test flake. Either the tool should be updated to pass the new flag, or the message should go on stdout instead of stderr.
It looks like this might have started with the Dart roll here flutter/engine#40455, so I'm guessing this is coming from the commit here:
cc @christopherfujino @eliasyishak @jcollins-g
P2 since the tree will stay open, but we are wasting CI time and resources by always running these tests twice, and this message is user visible, and should be addressed before we cut the branch soon.