Windows compilation failures in flutter/packages tests hang LUCI

This issue has been tracked since 2022-11-23.

I wasted a lot of time debugging a hang in CI in the Windows LUCI tests in a flutter/packages PR, and eventually discovered that it was because I forgot to update some #includes for a file rename (and missed it locally because I still had the file in the old location). This should have failed with a clear error message in CI after a couple of minutes; instead it hung for an hour and a half and provided no useful output.


  • Make a branch from 3b311692c8bb234b9efd7426d3e61aff2bd88d8e in flutter/packages#2823
  • Run Windows custom_package_tests master - packages against that branch

Having CI hang with missing log output instead of failing immediately with errors is a huge productivity drain when things go wrong.

stuartmorgan wrote this answer on 2022-11-23

/cc @godofredoc This isn't something that's queue-worthy, since it doesn't actively block current work, but it would be really good if we could prioritize this to reduce future loss of engineering time.

More Details About Repo
Owner Name flutter
Repo Name flutter
Full Name flutter/flutter
Language Dart
Created Date 2015-03-06
Updated Date 2022-12-07
Star Count 147031
Watcher Count 3560
Fork Count 23915
Issue Count 11300


Issue Title Created Date Updated Date