Save every run beside its zip - #41
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Every ticket writes its tests before its code, and its pull request reports a run over a target set or a corpus folder with the number of flagged fields. See docs/plan.md. Write every run's output to a file under out/ before reading it.
convertprints its report and discards route A's reply. Writereport.txt(the printed report),reply-a.json(route A's reply),reply-b.json(route B's, where it ran) andflags.jsonbeside the zip in the out directory, so that no model call's output is lost and a run can be compared or replayed later. The ticket is done when the ME2 pair leaves those four files inout/.Workbench ticket t46.