dashorst opened a new issue, #1923:
URL: https://github.com/apache/wicket/issues/1923

   `CryptoMapperTest.pageInstanceDecryptMultipleCryptoMapper` failed in CI on 
the `wicket-10.x` branch for #1917, a Dependabot PR that only bumps 
`build-helper-maven-plugin` from 3.7.0 to 3.8.0. The same bump passed on 
`master` (#1909) and `wicket-11.x` (#1919), so the change itself is an unlikely 
cause.
   
   Failing run: https://github.com/apache/wicket/actions/runs/43666967893 (job 
`build (25)`; the `build (17)` and `build (21)` jobs were cancelled by 
fail-fast, not failed on their own)
   
   ```
   [ERROR] Tests run: 26, Failures: 1, Errors: 0, Skipped: 0 -- in 
org.apache.wicket.core.request.mapper.CryptoMapperTest
   [ERROR] 
org.apache.wicket.core.request.mapper.CryptoMapperTest.pageInstanceDecryptMultipleCryptoMapper
 <<< FAILURE!
   org.opentest4j.AssertionFailedError: expected: not <null>
   [ERROR]   CryptoMapperTest.pageInstanceDecryptMultipleCryptoMapper:324 
expected: not <null>
   ```
   
   To investigate:
   
   - Whether the test is nondeterministic: random keys or salts, ordering 
between the two `CryptoMapper` instances, shared or static state, or a 
dependency on test execution order. Try to reproduce by running it repeatedly 
on `wicket-10.x` with Java 25.
   - Whether it also fails on `master` and `wicket-11.x`, and how often it has 
failed in recent CI history.
   - Whether the CI infrastructure contributes: the Java 25 runner/JDK build, 
the GitHub Actions setup, or the fail-fast matrix cancelling the other jobs and 
hiding whether they would pass.
   
   The fix goes on `master` first and is cherry-picked to the maintenance lines 
where it applies.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to