NIFI-7751 - fix for TestExecuteStreamCommand unit tests#4483
NIFI-7751 - fix for TestExecuteStreamCommand unit tests#4483pvillard31 wants to merge 1 commit intoapache:mainfrom
Conversation
|
+1, any idea why this was coming up now? |
|
it seems to be related to a JDK upgrade in the Github actions but could not reproduce locally |
|
not about a JDK upgrade. or Maven. Or even the linux platform itself. See below of a run that passes and another that fails FAILS PASSES Build with Maven48m 45s ....so there is something else different in the config of the systems. |
|
good and likely relevant find by @kevdoran actions/runner-images#1437 |
… unit tests Signed-off-by: Joe Witt <joewitt@apache.org>
… unit tests Signed-off-by: Joe Witt <joewitt@apache.org>
Thank you for submitting a contribution to Apache NiFi.
Please provide a short description of the PR here:
Description of PR
Enables X functionality; fixes bug NIFI-YYYY.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:
Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?
Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
Has your PR been rebased against the latest commit within the target branch (typically
main)?Is your initial contribution a single, squashed commit? Additional commits in response to PR reviewer feedback should be made on this branch and pushed to allow change tracking. Do not
squashor use--forcewhen pushing to allow for clean monitoring of changes.For code changes:
mvn -Pcontrib-check clean installat the rootnififolder?LICENSEfile, including the mainLICENSEfile undernifi-assembly?NOTICEfile, including the mainNOTICEfile found undernifi-assembly?.displayNamein addition to .name (programmatic access) for each of the new properties?For documentation related changes:
Note:
Please ensure that once the PR is submitted, you check GitHub Actions CI for build issues and submit an update to your PR as soon as possible.