Repository navigation
test(qa): take #899's rows into the Linux LibreOffice fidelity baseline - #908
Merged
Merged
Conversation
The Linux baseline held the five documents #899 moves (cv-orange_ops, cv-serif_headline, invoice-workspace, proposal-editorial, proposal-northline) as they stood before it, while every CI run since measures them as #899's did. Both files now match the docx-fidelity artifact of #907's run (38794754386) byte for byte: 45 lines nearer the page, 2 further by 0.05pt, all others unchanged.
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.
Why
#899 moves five documents:
cv-orange_ops,cv-serif_headline,invoice-workspace,proposal-editorialandproposal-northline. The Linux LibreOffice baseline still holds those five as they stood before #899. #898 says its baseline matches thedocx-fidelityartifact of #899's last CI run (38571103664) byte for byte. The merged files differ from that artifact in exactly these five documents' rows and match it everywhere else.Every CI run since then measures the corpus the way #899's run did; the artifacts of #906 and #907 match it byte for byte. Because the five documents now stand nearer the page than the baseline says, the DOCX fidelity job passes. It would also pass a change that undid #899 on Linux.
What changed
libreoffice-linux.tsvandlibreoffice-linux-lines.tsvnow match thedocx-fidelityartifact of #907's CI run (38794754386) byte for byte, summary and lines. That run measured2.5-devat43adc8336.Only the rows of the five documents change.
Lines that moved by more than 0.05pt: 45 nearer the page, 2 further. Both further lines belong to
cv-orange_opsand moved by 0.05pt each.Summary rows:
proposal-editorialproposal-northlinecv-serif_headlinecv-orange_opsinvoice-workspace's summary row stays the same; two of its lines move nearer.Verification
./mvnw -B -ntp clean verify→ BUILD SUCCESS (render-docx 1628, qa 1820).git show HEAD:<file> | cmp - <artifact file>reports no difference for either file.Lane: test (qa fidelity baseline), no code change.