All of lore.kernel.org
 help / color / mirror / Atom feed
From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [RFT PATCH -perfbook v3 v3 0/4] Enable parallel runs of pdflatex
Date: Sun, 30 Jan 2022 18:30:56 +0900	[thread overview]
Message-ID: <92c18a74-e182-6e23-ff57-e3de19780fb4@gmail.com> (raw)
In-Reply-To: <20220130043603.GR4285@paulmck-ThinkPad-P17-Gen-1>

On Sat, 29 Jan 2022 20:36:03 -0800, Paul E. McKenney wrote:
> On Sat, Jan 29, 2022 at 08:19:33PM +0900, Akira Yokosawa wrote:
>> Hi Paul,
>>
>> I said earlier in v2's thread:
>>
>>> This patch changes both LaTeX code and Makefile.
>>> SyncTeX database is affected by LaTeX code change because
>>> it is a collection of "LaTeX code (file:line:char) <->
>>> coordinates in PDF".
>>> So we can't see if changes in Makefile affect PDF or not.
>>>
>>> I'll split this patch into a set of "preparatory LaTeX change"
>>> and "Makefile update" patches.
>>
>> I did break up the patch (1/4 and 2/4), but it did not work as I
>> had expected.
>> Because of the Git-commit info in the footer area, SyncTeX database
>> can't be identical when you move to another commit.
>>
>> So, I restored the Makefile as of 2022.01.25 for reference (3/4)
>> and added a script to collect and compare SyncTeX databases from
>> reference, sequential, and parallel runs of pdflatex (4/4).
>>
>> Please give it a try.
>>
>> You can override defaults of TARGETS (2c 1c eb) and JOBS (4) by
>> saying, e.g.:
>>
>>   TARGETS="2c 1c eb nq 1cnq ebnq" JOBS=8 ./utilities/parallel-latex-regress.sh
>>
>> It will take quite a while for sequential runs of pdflatex with
>> the synctex option enabled.  So I'd suggest starting from a short
>> list.
>>
>> In my tests so far, no mismatch was detected.
> 
> Thank you, especially for the script!  I applied these patches, but I
> get an exit code of 1.  Ah, but that is because "2cnq" is not a thing.
> Trying again with:
> 
> TARGETS="2c 1c eb 1cnq nq ebnq" time ./utilities/parallel-latex-regress.sh
> 
> And I still got mismatches and an exit code of 1, with output shown
> below.  Any hints?

Paul, you did find a regression in the changes of 2/4.
I did not expect the script would actually catch such a bug.

The "sorting out" in 2/4 caused autodate.sh to see temporary
untracked files from concurrent conversions of figures.

I'm sending a followup patch (5/4) partially reverting 2/4.
I should have run the test under a newly cloned Git repository...

        Thanks, Akira

> 
> 							Thanx, Paul
> 
> ------------------------------------------------------------------------
> 
[...]
> /tmp/perfbook.ref.synctex.gz /tmp/perfbook.sequ.synctex.gz differ: byte 3690, line 6
> /tmp/perfbook.ref.synctex.gz /tmp/perfbook.para.synctex.gz differ: byte 3690, line 6
> /tmp/perfbook-1c.ref.synctex.gz /tmp/perfbook-1c.sequ.synctex.gz differ: byte 3720, line 5
> /tmp/perfbook-1c.ref.synctex.gz /tmp/perfbook-1c.para.synctex.gz differ: byte 3720, line 5
> /tmp/perfbook-eb.ref.synctex.gz /tmp/perfbook-eb.sequ.synctex.gz differ: byte 3705, line 8
> /tmp/perfbook-eb.ref.synctex.gz /tmp/perfbook-eb.para.synctex.gz differ: byte 3705, line 8
> /tmp/perfbook-1cnq.ref.synctex.gz /tmp/perfbook-1cnq.sequ.synctex.gz differ: byte 3722, line 4
> /tmp/perfbook-1cnq.ref.synctex.gz /tmp/perfbook-1cnq.para.synctex.gz differ: byte 3722, line 4
> /tmp/perfbook-nq.ref.synctex.gz /tmp/perfbook-nq.sequ.synctex.gz differ: byte 24, line 1
> /tmp/perfbook-nq.ref.synctex.gz /tmp/perfbook-nq.para.synctex.gz differ: byte 24, line 1
> /tmp/perfbook-ebnq.ref.synctex.gz /tmp/perfbook-ebnq.sequ.synctex.gz differ: byte 3701, line 7
> /tmp/perfbook-ebnq.ref.synctex.gz /tmp/perfbook-ebnq.para.synctex.gz differ: byte 3701, line 7
> Mismatch detected in SyncTeX databases!
> Command exited with non-zero status 1
> 2230.23user 110.37system 27:21.46elapsed 142%CPU (0avgtext+0avgdata 127116maxresident)k
> 0inputs+4072584outputs (263249major+15113217minor)pagefaults 0swaps

  parent reply	other threads:[~2022-01-30  9:30 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-29 11:19 [RFT PATCH -perfbook v3 v3 0/4] Enable parallel runs of pdflatex Akira Yokosawa
2022-01-29 11:23 ` [RFT PATCH -perfbook v3 v3 1/4] Replace \include{} with \input{} for parallel pdflatex runs Akira Yokosawa
2022-01-29 11:25 ` [RFT PATCH -perfbook v3 v3 2/4] Makefile: Fix issues WRT parallel runs of pdflatex Akira Yokosawa
2022-01-29 11:27 ` [RFT PATCH -perfbook v3 v3 3/4] Restore Makefile as of 2022.01.25 Akira Yokosawa
2022-01-29 11:28 ` [RFT PATCH -perfbook v3 v3 4/4] Add script for parallel-pdflatex-run regression test Akira Yokosawa
     [not found] ` <20220130043603.GR4285@paulmck-ThinkPad-P17-Gen-1>
2022-01-30  9:30   ` Akira Yokosawa [this message]
2022-01-30  9:38 ` [RFT PATCH -perfbook v3 5/4] Makefile: Fix regression of parallel run of autodate.sh Akira Yokosawa
2022-01-31  1:48   ` Paul E. McKenney

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=92c18a74-e182-6e23-ff57-e3de19780fb4@gmail.com \
    --to=akiyks@gmail.com \
    --cc=paulmck@kernel.org \
    --cc=perfbook@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.