odig.0.1.0: relax pessimistic constraints on b0

[dbuenzli]

What the title says.

[dbuenzli]

Is it possible to access the opam logs on the windows build failure ? I'd like to know why b0 is failing (especially since I'm going to push a release in the upcoming days) but I can't read the actual error.

[jmid]

Is it possible to access the opam logs on the windows build failure ? I'd like to know why b0 is failing (especially since I'm going to push a release in the upcoming days) but I can't read the actual error.

I don't know of an easy way. Previously I've tried the following (both on self-PRs for my own opam-repository fork):

• adding flags: verbose which I learned from https://github.com/ocaml/opam-repository/wiki/How-to-deal-with-CI#annex
• adding a -v verbose flag to the relevant line of the workflow file https://github.com/ocaml/opam-repository/blob/master/.github/workflows/windows.yml#L115

[jmid]

The change LGTM too, thanks!

[mseri]

I am re-running the jobs with debug logging enabled, let's see if this gives any new insight or not. I'll let them go through before merging, since I don't know if they would be terminated otherwise.

[jmid]

TIL: https://docs.github.com/en/actions/how-tos/manage-workflow-runs/re-run-workflows-and-jobs#re-running-failed-jobs-in-a-workflow

[dbuenzli]

Doesn't seem to improve. Forget about that, I suspect there's a problem with compiling the c stubs. Hopefully I can get something out of that windows arm vm I managed to make myself a couple of month agos.

[jmid]

Note: There's also ocaml/ocamlfind#112 which solves the ocamlfind issue triggered on topkg under MSys2 (just letting you know to avoid double work).

[mseri]

Thanks

[dbuenzli]

Hopefully I can get something out of that windows arm vm I managed to make myself a couple of month agos.

So after figuring out I was going nowhere with that ARM image (help @dra27 play more it's all smooth there :-), I managed after something like a whole day of compilation to have working opam x86_64 install running at continental drift speed to get this very sad error:

PS C:\Users\admin> opam install b0 --keep-build-dir -v
The following actions will be performed:
=== install 1 package
  ∗ b0 0.0.6

<><> Processing actions <><><><><><><><><><><><><><><><><><><><><><><><><><>  🐫
⬇ retrieved b0.0.0.6  (https://opam.ocaml.org/cache)
+ C:\Users\admin\AppData\Local\opam\default\bin\ocaml.exe "pkg/pkg.ml" "build" "--dev-pkg" "false" (CWD=C:\Users\admin\AppData\Local\opam\default\.opam-switch\build\b0.0.0.6)
- The command line is too long.
- pkg.ml: [ERROR] cmd ["ocamlbuild" "-use-ocamlfind" "-classic-display" "-j" "4" "-tag" "debug"
-      "-build-dir" "_build" "opam" "pkg/META" "CHANGES.md" "LICENSE.md"

I don't think ocamlbuild supports response files and really don't expect nor would dare asking the current maintainers to add support for it. Perhaps I can switch the project to its own bootstrap build and/or make, need to look into that.

[dbuenzli]

I don't think ocamlbuild supports response files

But it supports .itarget files. So there's a nice and short fix at the topkg level that I tested successfully on my turtle vm. I'm going to go with that as it insulates all topkg packages from that problem (which could show up more than expected now that topkg also install sources by default).

As I side effect it also improves seeing build errors in opam's short log (before you'd only get the end list of the list of targets).