I’d like to announce here a few things regarding check.ocamllabs.io. To recall, this website is an interface to find out which opam packages are broken with a given set of OCaml compilers.
First of all some features, I hope useful for everyone, have been added:
Log search: gives you the possibility to filter the packages by whether or not it contains any given [posix regexp] in their logs. This feature is a bit slow for obvious reasons so expect a 10 to 20 seconds delay if you use this feature.
The diff page: A page on the website (see link on the top right) is now dedicated to show the differences between the current check and the previous check (the tool checks every two days and takes approximately one and a half day to finish, sometimes more because the service has to be restarted for maintenance reasons).
I’d like also to ask here if anybody would have any idea of a new name for the tool itself. For now its name is opam-check-all but I find this name not good and would like to find a new one like maybe
opam-health or maybe something more original but I have no idea. If somebody has any ideas please submit them here.
For the future I want to add again more features like: revdeps counter (suggested by @bluddy on the last post about opam-check-all), add a way of viewing all the packages despite being not available on any of the switches (not shown at the time), or automatically send the diff for each run by email somewhere (another solution of an improvement suggested by @UnixJunkie on the last post again)
Keep sending me features requests in the comments on over on github if you have ideas.
I almost forgot, but the next run is going to include OCaml 4.08.0beta1, and so, test which packages need to be upgraded before the next release.
opam-health-check seems good to me.
How about opam-watch or opam-repo-watch?
FWIW this looks related in purpose to https://coq-bench.github.io/clean/Linux-x86_64-4.05.0-2.0.1/released/ (work by @clarus, sources at https://github.com/coq-bench, not something that is maintained by the Coq team).
Nice site and thank you.
Is this a color blindness aware design?
I’m not get color blindness, but my simulator camera shows this pic.
type C is majority, P, D and T is three well known type of color blindness.
There is a color universal design. ( https://ja.wikipedia.org/wiki/カラーユニバーサルデザイン ) (unfotunately no english page.)
(Here is the main English page about this work. People doing presentations with slides should read it, considering 1 in 12 men (8%) and 1 in 200 women are color blind. E.g. a colleague of mine usually can’t see the basic light green color on LaTeX slides and cannot follow a red laser pointer.)
Color Brewer is an easy way to get color palettes that are both pretty and readable for everybody (select “colorblind safe”)".
Is this project alive? It looks like that it is missing compilers younger than 4.10
Also, It would be great to see the date of last table update
I have a feeling that information at http://check.ocamllabs.io/ has been updated only after my last post on this forum (i.e. around 13 of september).
@kit-ty-kate, did I get correct intuition? Should I use something else to check status of packages maintained by me?
Sorry for not getting back to you sooner, I don’t really check discuss often and I can’t find a way to filter email notifications coming from it,
You can see the date of the last runs on this page: http://check.ocamllabs.io/run
At the moment, checks from 4.02 to 4.11 take about a 100 hours (~4 days). During those 4 days the 72 cores are 100% maxed out.
However, I currently use the machine to check for the next versions of the compiler, extra ocaml PR checks and things like checking compatible packages when the a new janestreet package suite comes out, and waiting 5 days to get an answer for that is too much for me. So even though I’m not using the machine full time I disabled the automatic runs to allow me to run these with high priority.
Now, I know there are things that could be improved but it has not been on my priority list in a bit. Since you seem interested I’ll try to find a solution. I’ll get back to you soon.