See:
The buildable should move to the failed state instead.
hach-que | |
Dec 2 2015, 9:50 AM |
F1010752: pasted_file | |
Dec 2 2015, 9:50 AM |
F1010754: pasted_file | |
Dec 2 2015, 9:50 AM |
See:
The buildable should move to the failed state instead.
I don't know how to reproduce the behavior this report describes. See Contributing Bug Reports.
This happens after upgrading Phabricator and having a build step implementation no longer exist; when the build plan runs you get an unexpected error. Getting the unexpected error isn't what's wrong - but that the buildable doesn't get marked as failed is incorrect.
You can replicate this issue by making a build plan and deleting one of the build step implementations it uses.