Datasets:
Datasheet: describe what the verifier does, and record the interpreter used
Browse files- DATASHEET.md +7 -2
DATASHEET.md
CHANGED
|
@@ -122,8 +122,13 @@ genuine defect.
|
|
| 122 |
|
| 123 |
**Independent re-verification.** `verify.py` re-clones each project from scratch,
|
| 124 |
checks out both commits, re-applies the fix commit's tests and runs them again. It
|
| 125 |
-
|
| 126 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 127 |
|
| 128 |
```bash
|
| 129 |
python3 verify.py --sample 20
|
|
|
|
| 122 |
|
| 123 |
**Independent re-verification.** `verify.py` re-clones each project from scratch,
|
| 124 |
checks out both commits, re-applies the fix commit's tests and runs them again. It
|
| 125 |
+
reads only the published record and the project it cites, and re-derives the
|
| 126 |
+
result from the upstream repository.
|
| 127 |
+
|
| 128 |
+
Old projects are run under an interpreter that can import them, so a record from
|
| 129 |
+
2016 is not judged by whether it works on a current Python. The interpreter used
|
| 130 |
+
is reported alongside the verdict. A record that cannot be run on a given machine
|
| 131 |
+
is reported as skipped, never as a failure.
|
| 132 |
|
| 133 |
```bash
|
| 134 |
python3 verify.py --sample 20
|