Puneeth Chaganti

Keeping the issue open until we have some kind of a test for this, based on @art-w's comment [here](https://github.com/ocurrent/current-bench/pull/299#issue-1128617362): > see https://github.com/ocurrent/current-bench/issues/297 ... but I would like to keep this...

See also #143 though this seems nicer to me.

Are you suggesting that we make the benchmark runs triggered manually, instead of automatically running on every PR?

It looks like the analysis failing causes the latch to be stuck in a pending/ready state. Some context on why the latch was added is in [this comment](https://github.com/ocurrent/opam-repo-ci/issues/202#issuecomment-1405584558) and #202...

> Using the linter on [dra27/opam-repository#20](https://github.com/dra27/opam-repository/pull/20), which has 47 packages, took about 1 minute. This surprised me, as I don't think the linting is doing anything computationally expensive. Is a...

I was testing for #405 and ran into this myself too. I didn't do any detailed benchmarking but from crude printf benchmarking, it looks like we spend a bunch of...

I chose the Apache-2.0 license here based on the licenses used in other repos in this org, for instance [ocurrent], [obuilder], [solver-service], etc. [ocurrent]: https://github.com/ocurrent/ocurrent [obuilder]: https://github.com/ocurrent/obuilder [solver-service]: https://github.com/ocurrent/solver-service

@SitaGanesh Thanks for reporting the issue. It may be better to report it on the [opam](https://github.com/ocaml/opam/issues/) GitHub repository, possibly with more debug information like your $PATH, etc.

> As @panglesd states, the main missing bit is the dune-lang check and the test for it. > > The rest are fairly minor things that I came across when...

The tests seem to be freezing randomly on some files. Here are some manual runs of the tests on Windows and they seem to be freezing on different files in...