-
Notifications
You must be signed in to change notification settings - Fork 52
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
Fix erroneous exit code not propagating for BatchJob #36
Open
taueres
wants to merge
2
commits into
kriswallsmith:master
Choose a base branch
from
taueres:fix-batch-job-error-status-code
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,112 @@ | ||
<?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); | ||
} | ||
|
||
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'); | ||
|
||
$this->assertNull($promise->getError(), 'Child process did not throw and exception so error should be null'); | ||
|
||
$actualExitStatus = $promise->getExitStatus(); | ||
|
||
$this->assertEquals($expectedExitStatus, $actualExitStatus, 'Parent process exit status should match the child one'); | ||
} | ||
|
||
public function testErrorMessagePropagation() | ||
{ | ||
$manager = new \Spork\ProcessManager(); | ||
$batch = $manager->createBatchJob(range(1, 5)); | ||
|
||
$expectedErrorMessage = 'This is a test message'; | ||
|
||
$failingClosure = function ($data) use ($expectedErrorMessage) { | ||
// Simple condition to simulate only one point of failure | ||
if (3 === $data) { | ||
throw new \InvalidArgumentException($expectedErrorMessage); | ||
} | ||
|
||
exit(0); | ||
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. do we absolutely need to exit here ? It would be great if this example could match what people will probably do, i.e. not using |
||
}; | ||
|
||
$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'); | ||
|
||
$this->assertNotNull($promise->getError(), 'Since child process thrown an exception, parent process should have an error'); | ||
|
||
$this->assertEquals($expectedErrorMessage, $promise->getError()->getMessage(), 'Parent process error message 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'); | ||
} | ||
} |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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.
shouldn't we rather have a case throwing an exception in the closure ? This seems a more sensible use case.
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.
Exceptions are indeed more sensible use cases. But this way we cannot test the correctness of the exit status.
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.
@stof I just added a new test case when the closure throws an exception.