This is an archive of the discontinued LLVM Phabricator instance.

Handle CalledProcessError without a Python stack
ClosedPublic

Authored by rnk on Feb 6 2019, 1:24 PM.

Details

Summary

When a child process exits with a non-zero return code, an exception is
generated. Catch the exception near the top level, print the exit code,
and don't print a Python stack trace, since this is expected behavior
when SVN isn't up or the test suite fails.

Diff Detail

Repository
rL LLVM

Event Timeline

rnk created this revision.Feb 6 2019, 1:24 PM
inglorion added inline comments.Feb 6 2019, 3:15 PM
zorg/buildbot/builders/annotated/annotated_builder.py
44 ↗(On Diff #185627)

Did you mean "subprocess" instead of "subprojects"?

inglorion requested changes to this revision.Feb 7 2019, 10:14 AM

See earlier comment.

This revision now requires changes to proceed.Feb 7 2019, 10:14 AM
rnk marked an inline comment as done.Feb 7 2019, 10:18 AM
rnk added inline comments.
zorg/buildbot/builders/annotated/annotated_builder.py
44 ↗(On Diff #185627)

Editing code without tests is scary. :) Even to test this manually, I have to find a way to set up a failing build.

rnk updated this revision to Diff 185811.Feb 7 2019, 10:19 AM
  • fix typo
This revision is now accepted and ready to land.Feb 7 2019, 11:06 AM
This revision was automatically updated to reflect the committed changes.
Herald added a project: Restricted Project. · View Herald TranscriptFeb 7 2019, 11:11 AM