-
Notifications
You must be signed in to change notification settings - Fork 51
Fix erroneous exit code not propagating for BatchJob #36
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
base: master
Are you sure you want to change the base?
Changes from 1 commit
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| <?php | ||
|
|
||
| namespace Spork\Test\Batch; | ||
|
|
||
| class BatchJobTest extends \PHPUnit_Framework_TestCase | ||
| { | ||
| public function testErrorPropagation() | ||
| { | ||
| $manager = new \Spork\ProcessManager(); | ||
| $batch = $manager->createBatchJob(range(1, 5)); | ||
|
|
||
| $expectedExitStatus = 20; | ||
|
|
||
| $failingClosure = function ($data) use ($expectedExitStatus) { | ||
| // Simple condition to simulate only one point of failure | ||
| if (3 === $data) { | ||
| exit($expectedExitStatus); | ||
|
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. shouldn't we rather have a case throwing an exception in the closure ? This seems a more sensible use case.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Exceptions are indeed more sensible use cases. But this way we cannot test the correctness of the exit status.
Author
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. @stof I just added a new test case when the closure throws an exception. |
||
| } | ||
|
|
||
| exit(0); | ||
| }; | ||
|
|
||
| $promise = $batch->execute($failingClosure); | ||
|
|
||
| $promise->wait(); | ||
|
|
||
| $success = null; | ||
|
|
||
| $promise->done(function () use (& $success) { | ||
| $success = true; | ||
| }); | ||
|
|
||
| $promise->fail(function () use (& $success) { | ||
| $success = false; | ||
| }); | ||
|
|
||
| $this->assertFalse($success, 'Promise should fail'); | ||
|
|
||
| $actualExitStatus = $promise->getExitStatus(); | ||
|
|
||
| $this->assertEquals($expectedExitStatus, $actualExitStatus, 'Parent process exit status should match the child one'); | ||
| } | ||
|
|
||
| public function testExitStatusIsZeroOnSuccess() | ||
| { | ||
| $manager = new \Spork\ProcessManager(); | ||
| $batch = $manager->createBatchJob(range(1, 5)); | ||
|
|
||
| $simpleClosure = function () { | ||
| exit(0); | ||
| }; | ||
|
|
||
| $promise = $batch->execute($simpleClosure); | ||
|
|
||
| $promise->wait(); | ||
|
|
||
| $success = null; | ||
|
|
||
| $promise->done(function () use (& $success) { | ||
| $success = true; | ||
| }); | ||
|
|
||
| $promise->fail(function () use (& $success) { | ||
| $success = false; | ||
| }); | ||
|
|
||
| $this->assertTrue($success, 'Promise should be successful'); | ||
|
|
||
| $actualExitStatus = $promise->getExitStatus(); | ||
|
|
||
| $this->assertEquals(0, $actualExitStatus, 'When the promise is successful the exit status should be zero'); | ||
| } | ||
| } | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The state is indeed propagated but what happens if a child fork throws an exception? Would be very nice to know what exactly went wrong. Or do child forks in that case print the message to stderr?