Repository navigation
AmberCtlException internal error causes flakes on Fuchsia LUCI workers. #50249
Description
An example of one such exception is here.
The specific issue is
AmberCtlException, cause: "amberctl get_up -n flutter_aot_runner failed, aborting.", underlying exception: OperationResult{failure, info: "Update failed with error fetch: Resolve status: ErrInternal, retrying...
Update failed with error fetch: Resolve status: ErrInternal, retrying...
Update failed with error fetch: Resolve status: ErrInternal, retrying...
", error: "2020/02/05 21:39:29 error getting an update: fetch: Resolve status: ErrInternal
Activity
godofredoc commentedon Feb 6, 2020
I'd recommend to try to find an owner for this on the fuchsia side. This error is happening because the amberctl is not able to serve the content of flutter_aot_runner
godofredoc commentedon Apr 18, 2020
Several teams are getting the same problem and fuchsia team is helping to triage. We need to collect verbose logs from the pm server and syslog to identify where the problems are.
Some pointers:
godofredoc commentedon Apr 19, 2020
Actually this is because amber_ctl initializes and empty repository that only have access to the packages included in the test far file. To fix this we actually need to serve the packages coming with the core image in addition to the far file.
Pass amber-files directory to tests. (#17815)
lock commentedon May 6, 2020
This thread has been automatically locked since there has not been any recent activity after it was closed. If you are still experiencing a similar issue, please open a new bug, including the output of
flutter doctor -vand a minimal reproduction of the issue.