[
https://issues.apache.org/jira/browse/NIFI-8465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17331010#comment-17331010
]
Paul Grey commented on NIFI-8465:
---------------------------------
options:
# accept infrequent failures of test case (1/256 odds)
# remove test case (test coverage hole of retry logic)
# a new/modified PasswordBasedEncryptor that allows its client to make a call
to attempt a legacy retry (e.g. "processLegacy(in, out)")
# a new/modified PasswordBasedEncryptor that allows its client to pass in a
hint that can be used to signal a retry within the call (knowledge of expected
recover text length, which could be used by "shouldAttemptLegacyDecrypt()")
> Correct intermittent failures in PasswordBasedEncryptorGroovyTest
> -----------------------------------------------------------------
>
> Key: NIFI-8465
> URL: https://issues.apache.org/jira/browse/NIFI-8465
> Project: Apache NiFi
> Issue Type: Bug
> Reporter: David Handermann
> Assignee: Paul Grey
> Priority: Minor
> Labels: encryption, security
>
> {{PasswordBasedEncryptorGroovyTest}} can fail intermittently during automated
> builds. A recent failure occurred when comparing encrypted and plaintext
> results:
> {quote}Error: Failures:
> Error:
> PasswordBasedEncryptorGroovyTest.testBcryptDecryptShouldSupportLegacyKeyDerivationProcess:445
> assert recovered == PLAINTEXT{quote}
> The test class should be evaluated to determine the source of the problem and
> refactored to avoid potential failures. It is also worth evaluating the
> opportunity to refactor the test into more discrete test classes.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
