[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[bug#43745] [PATCH 04/27] gnu: ocaml-migrate-parsetree: Update to 1.7.3.
From: |
zimoun |
Subject: |
[bug#43745] [PATCH 04/27] gnu: ocaml-migrate-parsetree: Update to 1.7.3. |
Date: |
Tue, 13 Oct 2020 14:09:55 +0200 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/27.1 (gnu/linux) |
Hi Julien,
Wow! Thank you for this detailed investigation.
On Tue, 13 Oct 2020 at 04:03, Julien Lepiller <julien@lepiller.eu> wrote:
> So, my hypothesis is that dune is building files out of order, but lets
> ocaml read the generated cmi files. Since the build is not in order,
> when it builds the same file in two different builds, the cmi are not
> the same and the result is different. Since dune will always use all
> my cores, I used a trick I learned from LFS:
>
> echo 0 > /sys/devices/system/cpu/cpu1/online
> (and similar for every other core, except cpu0)
>
> This way, I have a single-core machine and, hopefully, dune runs
> sequentially. This time, --rounds=2 passed (after removing the existing
> store item of course).
Where do you this “echo 0 > /sys/devices/system/cpu/cpu1/online“ to
disable all except cpu0? Because, I have tried as root on my 4 cpu
machine and then “./pre-inst-env guix build ocaml-migrate-parsetree
–no-grafts –check“ still returns an error.
Cheers,
simon
- [bug#43745] [PATCH 02/27] gnu: camlp5: Update to 7.13., (continued)
[bug#43745] [PATCH 12/27] gnu: ocaml4.07-merlin: Do not use deprecated jbuilder., Julien Lepiller, 2020/10/01
[bug#43745] [PATCH 13/27] gnu: ocaml4.07-ppx-expect: Do not use deprecated jbuilder., Julien Lepiller, 2020/10/01
[bug#43745] [PATCH 14/27] gnu: ocaml4.07-core: Do not use deprecated jbuilder., Julien Lepiller, 2020/10/01
[bug#43745] [PATCH 05/27] gnu: ocaml-ppx-tools-versioned: Update to 5.4.0., Julien Lepiller, 2020/10/01