Alexander Thomas

While they still run against whatever project, they do warn if the current project is not staging. Therefore not a P1. I would actually prefer if those tests would use...

The logs show up now that the change was landed. I'm pretty sure this is because it was a new config. That's not a very common case, so I'm reducing...

The documentation there is right now is [go/dart-status-file-free-workflow](https://goto.google.com/dart-status-file-free-workflow) which links to [go/dart-test-approval](https://goto.google.com/dart-test-approval) which links to the [results feed UI](https://dart-ci.firebaseapp.com/).

> I don't understand how the test filters on https://dart-ci.firebaseapp.com/ work at all, I can't get anything I want to show up. Example of a search with results (the problem...

It's probably a P2 (depending on the effort needed to fix it), impact is: - Introduces risk in the release process: re-running Windows builds doesn't work if they flake at...

Another possible solution (via @jonasfj): * Have a simple 404 page that redirects to the proper 404 page with javascript which then gets served from the expected location.

> @athomas I think this is specific to `api.dart.dev`, not something that needs to be done in `dartdoc`. > > Since the GCS serving setup for `api.dart.dev` basically has a...

> > The single file that handles all 404s is currently part of the dartdoc output, though. > > Yeah, but your bucket contains output from any different versions of...

This is actually a flutter build issue. The output doesn't appear on standalone Dart builds. The difference is in the clang version. Dart has clang pinned at [1] and flutter...

@zanderso FYI, seems clang is behind in Flutter Engine causing warnings. https://autoroll.skia.org/r/clang-flutter-engine seems blocked on formatting issues.