-
Notifications
You must be signed in to change notification settings - Fork 28.6k
flutter_plugins analyze fails with ProcessException: fatal: Not a valid object name FETCH_HEAD #89805
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
/cc @stuartmorgan flutter/plugins#4303 Picked up with roll #89803. |
Turned the test off, reducing priority. |
I suspect this was an infrastructure change since I don't think we've changed anything about how we are using FETCH_HEAD recently (I thought this might be due to my recent refactoring, but I don't think that should have changed this). But it's probably better to just always do the full analysis re-run when rolling into flutter/flutter rather than doing the PR-style incremental run anyway, so I'll re-write the test. |
(Although my refactor is in that delta, so maybe I'm missing a side-effect.) |
Oh, it was me. I missed that I still think moving off of tool_runner.sh is the better option though, since having external uses of tool_runner,sh that don't match the repo uses is, as demonstrated by my mistake, fragile. |
Updates the test to use the repository tooling directly rather than using tool_runner.sh in a way that flutter/plugins never calls it (and thus was broken accidentally), and re-enaables it. Using tool_runner.sh used to be necessary since there was non-trivial logic in it, but that's no longer the case. Fixes flutter#89805
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 |
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8836524695632600385/+/u/run_test.dart_for_flutter_plugins_shard_and_subshard_analyze/test_stdout
The text was updated successfully, but these errors were encountered: