fix : Fix test non-determinism:

[arekay-nv]

What does this PR do?

The probe command truncates the responses to the probe requests and only keeps the first 10 responses. This can cause test failures as the responses are out of order and particularly in CI the probe-0 would be missing in the first 10 requests.
The fix is to not truncate the responses which can be verbose but it prevents failures such as this one from creeping.

Closes #47

TODO

Type of change

• Bug fix
• New feature
• Documentation update
• Refactor/cleanup

Related issues

Testing

• Tests added/updated
• All tests pass locally
• Manual testing completed

Checklist

• Code follows project style
• Pre-commit hooks pass
• Documentation updated (if needed)

[github-actions]

MLCommons CLA bot All contributors have signed the MLCommons CLA ✍️ ✅

[gemini-code-assist]

Summary of Changes

Hello @arekay-nv, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on improving the debugging process for test non-determinism. It achieves this by adjusting the probe.py command to log all sample responses, providing a more thorough output that should aid in pinpointing the root causes of inconsistent test results.

Highlights

• Enhanced Debugging Visibility: The probe.py command has been modified to display all collected sample responses during probing, rather than just the first ten. This change aims to provide a more comprehensive view for debugging.
• Addressing Test Non-Determinism: This modification is specifically intended to assist in diagnosing and resolving non-deterministic test failures by offering a complete log of responses, which can help uncover subtle inconsistencies.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[Copilot]

Pull request overview

This PR addresses test non-determinism by modifying how probe responses are displayed. The change removes the artificial limit of showing only the first 10 responses, instead displaying all collected responses to aid in debugging.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[gemini-code-assist]

Code Review

This pull request aims to fix test non-determinism by changing how sample responses are logged. The current change removes the limit on the number of logged responses, which can lead to excessive output. I've suggested an alternative approach that sorts the responses before logging a subset, which fixes the non-determinism while keeping the logs concise.