-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add dependencies to fix opam-dune-lint
#50
Conversation
I noticed the following item didn't pass in #48 in the list of checks: ❌ EXPERIMENTAL: (lint-opam) (failure: Lint failed for grpc-async.opam) The motivation for this PR is to fix that check. Rebasing the PR across this change will also allows to verify that #48 doesn't introduce breaking changes for |
5582ce8
to
cbac7ec
Compare
This satisfies $ opam-dune-lint
grpc-async.opam: OK
grpc-bench.opam: OK
grpc-eio.opam: OK
grpc-examples.opam: OK
grpc-lwt.opam: OK
grpc.opam: OK |
/src: (run (shell "opam exec -- opam-dune-lint"))
grpc-async.opam: OK
grpc-bench.opam: OK
grpc-eio.opam: OK
grpc-examples.opam: OK
grpc-lwt.opam: OK
grpc.opam: OK |
cbac7ec
to
77d4757
Compare
opam-dune-lint
I just noticed that a new check is failing: ❌ EXPERIMENTAL: freebsd-5.1_opam-2.1 (failure: Failed: Build failed) I don't have experience with ocaml-ci nor FreeBSD builds. I haven't managed to access the log for the failure (500 error page on ocaml-ci). I don't know how the changes in this PR could cause this check to fail. There's a possibility this is a spurious or flickering failure. Putting this out there for your consideration. Note that |
This makes it is easier to avoid duplicated entries as well as making it obvious were new dependencies need to be added, which makes it more straight forward to write PRs that add new dependencies. In the process I discovered that the notty dependency was duplicated in `grpc-bench.opam`, which I fixed. This had no incidence on the build. The canonical order I used here was to put `ocaml` first, and then the rest of dependencies alphabetically.
For each added dependency, I looked elsewhere in the file for occurrences of the same library, and kept the same version bound if there was one, and none otherwise.
77d4757
to
b0fdc98
Compare
The check appears to be successful again. https://github.com/dialohq/ocaml-grpc/pull/50/checks ✅ freebsd-5.1_opam-2.1 (passed) If this isn't a transient issue, one potential cause could be the unintentional Regardless, I think that this PR doesn't make the situation worse regarding this |
I think this makes sense. We didn't have e.g. |
Thank you @quernd for reviewing the PR. I've observed that the CI checks have re-run and some are now showing an internal error status. I'm unsure why they re-ran as they were all passing previously. Could you possibly request a re-run? I'm hopeful this is a transient issue that will resolve itself. |
I triggered a re-run but I'm seeing many "Internal Error" failures like this:
I don't know how |
All green now, likely a transient issue. Thanks @mbarbin |
It was an issue on the Mac workers with removing cached results. In future
if you see issues please report them on
https://github.com/ocurrent/ocaml-ci/issues
…On Tue, 16 Jan 2024 at 4:39 am, Daniel Quernheim ***@***.***> wrote:
Merged #50 <#50> into main.
—
Reply to this email directly, view it on GitHub
<#50 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AABJXOLKGSBMDOPJD3H7FILYOVSWVAVCNFSM6AAAAABBPOCHKGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJRGQ4TAOBWGQ4DEOI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
Thanks, will keep it in mind! |
So that it is easier to avoid duplicating entries, use a canonical order to sort the libraries.
The canonical order I used here was to put
ocaml
first, and then the rest of dependencies alphabetically.Note that this PR is based on top of #49, so it is currently marked as draft.