clang/test/Driver/autocomplete.c is a test for --autocomplete, and this
test might break if people add/modify flags or HelpText. So I've add
comment for future developers so that they can fix this file according
to the change they had made.
Details
Diff Detail
- Build Status
Buildable 8877 Build 8877: arc lint + arc unit
Event Timeline
I wonder if this test is actually fragile. How can you break this test by adding a new flag?
clang/test/Driver/autocomplete.c | ||
---|---|---|
4 | Keep it in 80 cols. |
So, does this comment actually make sense? Looks like you cannot break this test by adding or modifying flags or by changing HelpText. (Theoretically, it'll break if you remove -fsyntax-only, for example, but that is not realistic.)
@ruiu
This test will break for instance, when someone add new value to mrelocation-model because values has to be shown in row 78- 83 order, or when someone made a new flag which start with -Wno-invalid-pp- because in row 96 only -Wno-invalid-pp-token is expected for this prefix.
E.g. If you add a flag that lands in between the results it breaks. Add -Wmajor-new-feature and the test goes red. Same with the flag results or changing the help test for -std=.
We could fix that by making the test less aggressive but it's already too forgiving right now (It actually passes when you completely break the autocomplete filtering feature and just return everything).
Maybe we need a smart solution(TM) in the future where we solve this in a more stable way while still actually testing the shipped clang binaries autocomplete feature.
clang/test/Driver/autocomplete.c | ||
---|---|---|
3 | "test had broke" -> "test broke" |
"test had broke" -> "test broke"