VuMartin opened a new pull request, #8443:
URL: https://github.com/apache/texera/pull/8443

   ### What changes were proposed in this PR?
   
   Replace the unseeded global `scala.util.Random` usage in 
`IntervalOpExecSpec` with a local seeded random generator (`Random(42)`). This 
makes the test inputs deterministic and ensures test execution paths and JaCoCo 
branch coverage are reproducible across runs.
   
   Before:
   First Run:
   <img width="1345" height="62" alt="Screenshot 2026-09-06 at 3 09 28 AM" 
src="https://github.com/user-attachments/assets/104e9c24-0546-4127-adf7-33ad60b1e979";
 />
   
   Second Run:
   <img width="1345" height="60" alt="Screenshot 2026-09-06 at 3 10 29 AM" 
src="https://github.com/user-attachments/assets/cf28ce98-5fec-40d6-bddf-2f49c96330d8";
 />
   
   After:
   First Run:
   <img width="1345" height="60" alt="Screenshot 2026-09-06 at 3 14 59 AM" 
src="https://github.com/user-attachments/assets/9030d6f3-6777-4c5c-beaa-f0480acfd833";
 />
   
   Second Run:
   <img width="1345" height="60" alt="Screenshot 2026-09-06 at 3 15 07 AM" 
src="https://github.com/user-attachments/assets/bbd837e1-ad21-49fd-8e6d-8fa888be9091";
 />
   
   ### Any related issues, documentation, discussions?
   
   Closes #8150
   
   ### How was this PR tested?
   
   - Ran `IntervalOpExecSpec` successfully.
   - Reproduced the issue before the fix: `IntervalJoinOpExec.scala` branch 
coverage changed between runs (20 missed / 78 covered vs. 21 missed / 77 
covered).
   - Verified the test now uses a seeded local random generator for all random 
inputs.
   - Ran the JaCoCo coverage report multiple times and verified the branch 
coverage is consistent across runs.
   
   ### Was this PR authored or co-authored using generative AI tooling?
   
   Generated-by: ChatGPT (5.5 mini)


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