Rerun flaky test in vpe_circuits_test.py

[arettig]

This test was causing intermittent failures of the CI in the 5% of runs where the measured value is outside 2 standard deviations from the expected value. The built in @cirq.testing.retry_once_with_later_random_values decorator will now rerun the test with a new random seed.

[gemini-code-assist]

Code Review

This pull request adds the @cirq.testing.retry_once_with_later_random_values decorator to the test_single_timestep test in src/openfermion/circuits/vpe_circuits_test.py to mitigate potential test flakiness due to random values. There are no review comments, and I have no feedback to provide.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

[arettig]

Looks like @cirq.testing.retry_once_with_later_random_values was added in cirq v1.5.0 but our ci.yaml uses v1.4.1:

OpenFermion/.github/workflows/ci.yaml

Line 203 in efaadae

cirq-version: [ 1.4.1 ]

@mhucka Is continuing support for 1.4.1 a hard requirement, or is it ok to bump that up in the CI?

[mhucka]

@mhucka Is continuing support for 1.4.1 a hard requirement, or is it ok to bump that up in the CI?

It is probably not a hard requirement, and now that you mention it, we should upgrade it to support the latest Cirq version if possible.

The pin in dev_tools/requirements/deps/runtime is actually a bit wider:

cirq-core>=1.4.1,<1.6.0

It ends up being 1.4.1 when pip-compile processes all the transitive dependencies, but I can no longer remember what the problem was the last time I tried to go higher than 1.6.

I'll open an issue about this.