Skip to content
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

Crashes from CompileLibraryResourcesAction are not logged #7442

Closed
jin opened this Issue Feb 15, 2019 · 2 comments

Comments

Projects
None yet
1 participant
@jin
Copy link
Member

commented Feb 15, 2019

As title, reported from Bazel Slack.

The error message is just (Exit 1): ResourceProcessorBusyBox failed: error executing command ..., with no other information to aid with debugging.

@jin jin self-assigned this Feb 15, 2019

@jin

This comment has been minimized.

Copy link
Member Author

commented Feb 15, 2019

Narrowed it down to at least IOExceptions.

@jin

This comment has been minimized.

Copy link
Member Author

commented Feb 15, 2019

Ok, it is just IOExceptions. Also replicated in internal Blaze.

@bazel-io bazel-io closed this in ae1e2be Feb 15, 2019

irengrig added a commit to irengrig/bazel that referenced this issue Feb 26, 2019

Properly throw exceptions in ResourceProcessorBusyBox, and log except…
…ions in CompileLibraryResourcesAction.

Fixes bazelbuild#7442

RELNOTES: Fixed issue where exceptions and stacktraces were silently swallowed in the Android resource processing pipeline.
PiperOrigin-RevId: 234224275

emusand added a commit to emusand/bazel that referenced this issue Apr 16, 2019

Properly throw exceptions in ResourceProcessorBusyBox, and log except…
…ions in CompileLibraryResourcesAction.

Fixes bazelbuild#7442

RELNOTES: Fixed issue where exceptions and stacktraces were silently swallowed in the Android resource processing pipeline.
PiperOrigin-RevId: 234224275
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.