markap14 commented on PR #11164:
URL: https://github.com/apache/nifi/pull/11164#issuecomment-4443129299

   [claude-opus-4.7] CI failure on `macos-15 Java 25` (system-tests) — 
classified as pre-existing flake; failed shard rerun.
   
   **Failed check:** `macos-15 Java 25` — 
https://github.com/apache/nifi/actions/runs/25806807059/job/75811748202
   **Failing test:** 
`org.apache.nifi.tests.system.state.ClusterStateKeyDropIT.testCanDropSpecificStateKey`
   
   ```
   [ERROR] 
org.apache.nifi.tests.system.state.ClusterStateKeyDropIT.testCanDropSpecificStateKey
 -- Time elapsed: 1.662 s <<< FAILURE!
   org.opentest4j.AssertionFailedError: expected: <{c=1, b=1, a=1}> but was: 
<{}>
       at org.junit.jupiter.api.Assertions.assertEquals(Assertions.java:1188)
       at 
org.apache.nifi.tests.system.state.ClusterStateKeyDropIT.testCanDropSpecificStateKey(ClusterStateKeyDropIT.java:124)
   ```
   
   **Why this is unrelated to the PR:**
   - `ClusterStateKeyDropIT` is known-flaky on macOS shards. NIFI-15763 
(#11070) previously added retry logic to this class for transient cluster 
errors. The same class flaked on `main` run 
https://github.com/apache/nifi/actions/runs/25457358299 (May 6) on `macos-15 
Java 21` for a sibling test method 
(`testCannotDropStateKeyWithLocalAndClusterState`), so the test class flakiness 
is independent of this PR.
   - This PR does not touch cluster state management, state providers, the 
coordinator, or anything `ClusterStateKeyDropIT` exercises. It only affects 
scheduling (virtual vs. timer-driven thread agents).
   - All other shards passed on this PR: `ubuntu-24.04 Java 21`, `ubuntu-24.04 
Java 25`, and `macos-15 Java 21`. Only `macos-15 Java 25` flaked.
   
   **Action taken:** Reran only the failed `macos-15 Java 25` shard via `gh run 
rerun 25806807059 --failed --repo apache/nifi`. Will continue to monitor.


-- 
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