You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardexpand all lines: README.md
+16
Original file line number
Diff line number
Diff line change
@@ -186,6 +186,22 @@ Some results are displayed at the command line, or alternatively written as JSON
186
186
187
187
Note: On macOS you need `gtime` (`brew install gnu-time`), as the built in `time` command is not enough.
188
188
189
+
## Regression Testing
190
+
191
+
Within the `filecoin-proofs` crate there is a regression suite. The idea is to record some generated proofs at various proof release versions, so that future versions/revisions can always ensure that it can properly verify historical proofs as expected.
192
+
193
+
By default, there is a test that verifies all known regression records that exist within the source tree.
194
+
195
+
In order to generate a new set of regression records, the feature flag `persist-regression-proofs` must be used.
196
+
197
+
When the feature is used and all of the `filecoin-proofs` tests are run (including the ignored tests), the following files are written to disk:
Once the new files are generated with a given proof version, they should be renamed appropriately and added to the repository and then referenced for verification during routine testing in the `filecoin-proofs/tests/regression.rs` source (see the `const` values at the top and go from there).
204
+
189
205
## Logging
190
206
191
207
For better logging with backtraces on errors, developers should use `expects` rather than `expect` on `Result<T, E>` and `Option<T>`.
0 commit comments