Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
Description
Big thanks to https://github.com/PuspenduBanerjee for identifying the issue.
This test is creating a 100MB file then scanning it in a java executable that is fired up with whatever the environ default heap sizing/etc.. is. In some environments, notably Travis-CI, this is creating build stability problems.
There is no apparent reason to match against such a large file.
Attachments
Attachments
Issue Links
- relates to
-
NIFI-1455 TestExecuteStreamCommand can experience issues in the Travis environment
- Resolved
GitHub user joewitt opened a pull request:
https://github.com/apache/nifi/pull/198
NIFI-1456reduced tests to 10MB instead of 100MB datasets and resolve……d IO issues which impact test stability
Signed-off-by: joewitt <joewitt@apache.org>
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/joewitt/incubator-nifi master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/nifi/pull/198.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #198
commit 072486942140121571f5340220c22c60ebf378b5
Author: joewitt <joewitt@apache.org>
Date: 2016-02-01T02:00:38Z
NIFI-1456reduced tests to 10MB instead of 100MB datasets and resolved IO issues which impact test stabilitySigned-off-by: joewitt <joewitt@apache.org>