c5aa281171
On second thought, this check does not seem to be adding value. We can test that the phases are as we expect them for each analysis by adding yaml tests. Those would fail if we introduce new phases from c++ accidentally or without coordination. This would achieve the same thing. At the same time we would not have to comment out this code each time a new phase is introduced. Instead we can just temporarily mute those yaml tests. Note I will add those tests right after the imminent new phases are added to the c++ side. Backport of #55926 |
||
|---|---|---|
| .. | ||
| licenses | ||
| qa | ||
| src | ||
| build.gradle | ||