Bots are not analyzing code in strong mode. #28013
Labels
area-test
Cross-cutting test issues (use area- labels for specific failures; not used for package:test).
legacy-area-analyzer
Use area-devexp instead.
P2
A bug or feature request we're likely to work on
type-bug
Incorrect behavior (everything from a crash to more subtle misbehavior)
Comments
stereotype441
added
legacy-area-analyzer
bwilkerson
added
P2
|
I believe they are now. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
test.py currently runs all analyzer tests from the root directory of the SDK repo. Analyzer CLI looks for the
.analysis_optionsfile in the directory analyzer was run from (not in the directory of the file being analyzed). Since there is no .analysis_options file at the root of the SDK repo, this means that all analyzer tests run by the analyzer bot are run in spec mode, even when analyzing a package whose.analysis_optionsfile indicates that it should be analyzed in strong mode.Note: a clumsy workaround is to put the string
// SharedOptions=--strongat the top of the test file. This is not a great workaround, though, since we would have to remember to do it every time a test file is added.The text was updated successfully, but these errors were encountered: