Open
Description
The FlutterFire CI (using GitHub Action) has sometimes the problem that the analysis crashes:
The analysis server timed out while shutting down.
No issues found!
The analysis server shut down unexpectedly.
Please report this at dartbug.com.
Running dart analyze . --fatal-infos
in the monorepo not concurrently (melos exec -c 1 -- dart analyze . --fatal-infos
) has a chance of 0.1% - 1% of getting this issue. Increasing the concurrently
parameter also increases the chance of crashing the analysis server dramatically. Using melos exec -c 5 -- dart analyze . --fatal-infos
has a 10% chance of getting this error.
- Output running
melos exec -c 5 -- dart analyze . --fatal-infos
(failed 10x of 100 runs): https://github.com/nilsreichardt/flutterfire/runs/6887637357?check_suite_focus=true - Output running
melos exec -c 1 -- dart analyze . --fatal-infos
(failed 2x of 240 runs): https://github.com/nilsreichardt/flutterfire/runs/6913924337?check_suite_focus=true
The FlutterFire CI is running with GitHub Action on ubuntu-latest
. The Dart version is v2.17.3
.
Metadata
Metadata
Assignees
Labels
A bug or feature request we're likely to work onFor issues related to conformance to the language spec in the parser, compilers or the CLI analyzer.Process exits with SIGSEGV, SIGABRT, etc. An unhandled exception is not a crash.Issues related to the 'dart analyze' toolIncorrect behavior (everything from a crash to more subtle misbehavior)