-
Notifications
You must be signed in to change notification settings - Fork 29.7k
Description
As part of upgrading the Chrome package in #98278, a Chromium cipd package G-lZgp8TuOPH0ndPr62HLAzRTWcFV3RRvFjOYyPZq_4C was uploaded that was malformed somehow that flutter couldn't detect the browser as a valid device. A new one was uploaded today that tests passed with.
The engine roll #99362 failed on a Mac web_tool_tests with a cache hit with the malformed package:
https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20web_tool_tests/12828/overview
[P19159 15:21:32.857 action_plan.go:160 I] In root:
[P19159 15:21:32.857 action_plan.go:172 I] to update:
[P19159 15:21:32.857 action_plan.go:174 I] flutter_internal/browsers/chrome/mac-amd64 (Qe3INUxKmaLOB1bDUu7ZD8otihLlr3k4mFVuFq8R97kC -> G-lZgp8TuOPH0ndPr62HLAzRTWcFV3RRvFjOYyPZq_4C)
[P19159 15:21:32.857 instancecache.go:187 I] Using instance cache at /opt/s/cipd_cache/cache/instances
[P19159 15:21:32.858 instancecache.go:409 I] [fetch] Cache hit for flutter_internal/browsers/chrome/mac-amd64:G-lZgp8TuOPH0ndPr62HLAzRTWcFV3RRvFjOYyPZq_4C
[P19159 15:21:32.860 deployer.go:294 I] [unzip] Deploying flutter_internal/browsers/chrome/mac-amd64:G-lZgp8TuOPH0ndPr62HLAzRTWcFV3RRvFjOYyPZq_4C into /opt/s/w/ir/cache/chrome/chrome(/)
Does build843-m9 need its chrome cache cleared? Do any other builders have the wrong one cached?
Here's one that's passing that used BlBCql9ZngKYkn_tiqUUCnZKtZtbbCnsP0RgmLIn2ZwC https://ci.chromium.org/p/flutter/builders/prod/Mac%20web_tool_tests/5090?