Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Desugaring for Android failed: Worker process did not return a WorkResponse
See original GitHub issueDescription of the problem:
While building an Android project, with Bazel from latest master, an error is thrown in Desugar worker log saying: Error parsing command line: Unrecognized option: --persistent_worker
Bugs: what’s the simplest, easiest way to reproduce this bug? Please provide a minimal example if possible.
Though I faced it in multiple projects, this project can be used for reproducing the issue: https://github.com/steelrooter/bazel-android-samples
Run: bazel build //app:app
What operating system are you running Bazel on?
macOS (darwin)
What’s the output of bazel info release?
development version
If bazel info release returns “development version” or “(@non-git)”, tell us how you built Bazel.
bazelisk build //src:bazel
What’s the output of git remote get-url origin ; git rev-parse master ; git rev-parse HEAD ?
git@github.com:bazelbuild/bazel.git
c063b5caf776dee665497b64c5c17d4ed7e6750a
4eee205df99e42922d0d658c7f41f72af2397895
Have you found anything relevant by searching the web?
No
Any other information, logs, or outputs that you want to share?
ERROR: /Users/sachin/PersonalProjects/samples-bazel-android/app/src/main/java/com/xachin/playground/BUILD.bazel:3:19: Desugaring app/src/main/java/com/xachin/playground/playground-app_kt.jar for Android failed: Worker process did not return a WorkResponse:
---8<---8<--- Start of log, file at /private/var/tmp/_bazel_sachin/6af8cdc15b57945be280298fb5d977c4/bazel-workers/worker-2-Desugar.log ---8<---8<---
Error parsing command line: Unrecognized option: --persistent_worker
Try --help.
---8<---8<--- End of log ---8<---8<---
Target //app:app failed to build
Issue Analytics
- State:
- Created 3 years ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I just got the same issue after upgrading to Bazel 3.3.0. I also don’t have the flag set in my
.bazelrcfile but I did use it few times in the same workspace by adding it manually to my build command.bazel clean --expungedoesn’t help.Created https://github.com/bazelbuild/bazel/issues/11618 with repro steps