content: the Vietnamese exercise and section lanes - #372
Open
tamnd wants to merge 136 commits into
Open
Conversation
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
140 builds of 44 volumes, 48,330 pages, up from 47,906. 115 of the 140 now pass all 33 checks, against 33 checks that include the Greek-label rule added this week. The Vietnamese gap-fill landed 149 of the 160 files that had no translation at all, and one volume crossed the text-length check with them: 25 builds now hold less text than the printing, against 26 before. The other standing failure is unchanged and is not a code fault either, Lie VII-IX in French missing chapter VIII.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
fvr VI § 2 exercise 6, which the third sweep landed after the control-word fix went in. 150 of the 160 files that had no Vietnamese translation now have one.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
False accept 0 of 10, against the target of under 5 per cent in spec 07 section 6. False reject 5 of 10, against the 30 per cent that is tolerated. Four of the five are the truth judge and one is the audit judge, and both have to pass, so the loss is almost all on the truth side.
The file the scorecard quotes was stale. This run is the whole built-in set, 20 cases over two hosts, nothing stopped early, so -write accepted it. false accept 0 of 10, 0.0%, against the 5% spec 07 6 holds it to false reject 1 of 10, 10.0%, against the 30% it holds that to The one differed case is ens-ii-s1-ex-2, read as accept and judged unverified, which is a right answer thrown out and the direction this is meant to fail in. No wrong answer was let through.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
Written by the running lanes since the last commit on this branch. The README blocks are regenerated in the same commit, so the numbers in it are the numbers of the tree it is committed with.
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
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.
What this is
The Vietnamese lanes, running against the fleet and committing as they go. This branch is open while they run rather than at the end, so the work is on the remote rather than on one laptop.
Where the gap stood when this started
Counted by walking
content/rather than by reading a report, because the two had disagreed before:Alongside that, 124 paragraphs in 32 files under
content/viare still in English. Four of those files are notes to the reader that never changed language at all,fvrat 11 paragraphs,int i-viat 11,evtat 10 andtop v-xat 9, and the rest are spread thin across body sections and exercises. That is the second lane on this branch.What had to happen first
The fleet was not answering.
fleet accountsread 0 ready on server3 and 1 on server2, with server1 at 66 MB free RAM and a load average of 57, and every ask was holding its full deadline and coming back with nothing. Running seven lanes into that was spending twenty minutes an ask to learn nothing, so the lanes came down,heal-sessionsran on server3, and the fleet came back at 11 ready on server3, 4 on server2 and 1 on server1. The lanes went back up after that and files started landing within the minute.The other thing worth writing down is that a translator can answer with an error and the answer gets written to disk as if it were a translation. Ten files in the corpus hold
Unusual activity has been detected from your device. Try again later.as their body, complete with atranslation_model, atranslation_runand a matchingsource_content_sha256, so nothing in the pipeline will ever look at them again. That is filed as tamnd/bourbaki-solver#471 and the ten are being retranslated by hand.How to read the commits
Every commit here says how many files it carries and nothing else, because they are written by the lane rather than by a person. The README blocks are regenerated in the same commit as the files they count, so the numbers in the README always describe the tree they are committed with.