Joe Duffy cdb2c79e8e Exit with an error code in the face of unhandled errors (#495) ... As part of fixing the exit bug recently, we accidentally made errors lead to zero exit codes. As a result, the Pulumi CLI thought the prgoram exited ordinarily, and proceeded to do its usual planning and deployment, rather than terminating abruptly. This is a byproduct of how Node's process.uncaughtException handler works. It hijacks and replaces all usual error logic, including the process.exit part. This change simply adds back the non-zero exit. I also added a test (and fixed one other that began failing afterwards), so that we can prevent regressions down the road.		2017-10-28 17:05:05 -07:00
..
000.empty	Implement free variable calculations	2017-09-04 11:35:21 -07:00
001.one_resource	Add auto-parenting	2017-10-15 04:38:26 -07:00
002.ten_resources	Add auto-parenting	2017-10-15 04:38:26 -07:00
003.one_complex_resource	Add auto-parenting	2017-10-15 04:38:26 -07:00
004.ten_complex_resources	Add auto-parenting	2017-10-15 04:38:26 -07:00
005.resource_thens	Add auto-parenting	2017-10-15 04:38:26 -07:00
006.asset	Add auto-parenting	2017-10-15 04:38:26 -07:00
007.promises_io	Add auto-parenting	2017-10-15 04:38:26 -07:00
008.ten_depends_on_resources	Add auto-parenting	2017-10-15 04:38:26 -07:00
009.invoke	Add a simple invoke test case	2017-09-30 14:53:27 -04:00
010.runtime_settings	Exit with an error code in the face of unhandled errors (#495)	2017-10-28 17:05:05 -07:00
011.unhandled_error	Exit with an error code in the face of unhandled errors (#495)	2017-10-28 17:05:05 -07:00