Missing info about downstream breakages for a new incompatible flag

[brandjon]

In yesterday's bazelisk + incompatible change nightly, the flag --incompatible_use_python_toolchains is tested according to the logs of the builds, but it has no corresponding summary annotation telling me which projects failed the flag.

Is this because 0.25 was just released and the pipeline grabbed the list of flags in an inconsistent way? Does it have to do with the labels attached to the flag's migration bug?

[philwo]

@meteorcloudy @fweikert Any idea?

[meteorcloudy]

The CI is somehow one step slower, the result is now in the latest run:
https://buildkite.com/bazel/bazelisk-plus-incompatible-flags/builds/99

[philwo]

Is this still an issue?

[meteorcloudy]

I think it's fine to close it.