Grind deterministically in tests

Author: jotabulacios

crypto/stark/src/grinding.rs

@@ -55,10 +55,26 @@ pub fn generate_nonce(seed: &[u8; 32], grinding_factor: u8) -> Option<u64> {
         is_valid_nonce_for_inner_hash(&inner_hash, candidate_nonce, limit)
     });
 
-    #[cfg(feature = "parallel")]
+    #[cfg(all(feature = "parallel", not(test)))]
     return (0..u64::MAX).into_par_iter().find_any(|&candidate_nonce| {
         is_valid_nonce_for_inner_hash(&inner_hash, candidate_nonce, limit)
     });
+
+    // Tests that compare two proofs byte for byte — `retire_lde_proof_is_byte_identical`
+    // is the one — are comparing two grindings as much as two provers, and
+    // `find_any` returns an arbitrary valid nonce of the many that exist. The
+    // nonce reaches the transcript, so a different one moves every challenge and
+    // query index after it: the proofs differ with nothing wrong. The serial
+    // search returns the smallest, which is stable across runs.
+    //
+    // Deliberately not `find_first` in production: which nonce comes back is not
+    // a contract (see `generate_nonce_maybe_gpu`), and this search is the
+    // prover's dominant CPU cost — ordering it would be paying for a property
+    // only the tests want.
+    #[cfg(all(feature = "parallel", test))]
+    return (0..u64::MAX).find(|&candidate_nonce| {
+        is_valid_nonce_for_inner_hash(&inner_hash, candidate_nonce, limit)
+    });
 }
 
 /// Checks if the leftmost 8 bytes of `Hash(inner_hash || candidate_nonce)` are less than `limit`