You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First of all, thanks for the existence of opam-health-check which is obviously quite a piece of work. I am trying to use opam-health-check and I am being substantially slowed down by the fact that I don’t know whether something is going on, or whether I did something wrong and need to start again.
In detail, I do opam-health-serve --debug --connect <cap_file> <instancedir>, and then opam-health-check run with what I believe to be a proper config file. But hardly any information is printed about what is being set in motion (if anything):
Since no new logs files are appearing in the instance directory, it’s not clear to me whether something is being computed on the cluster, or nothing happens because of some error / mistake.
Edit.: This would be particularly useful because depending on the cluster’s load, logs might not start appearing before almost an hour.
The text was updated successfully, but these errors were encountered:
First of all, thanks for the existence of
opam-health-check
which is obviously quite a piece of work. I am trying to useopam-health-check
and I am being substantially slowed down by the fact that I don’t know whether something is going on, or whether I did something wrong and need to start again.In detail, I do
opam-health-serve --debug --connect <cap_file> <instancedir>
, and thenopam-health-check run
with what I believe to be a proper config file. But hardly any information is printed about what is being set in motion (if anything):on the server side, and
on the client side.
Since no new logs files are appearing in the instance directory, it’s not clear to me whether something is being computed on the cluster, or nothing happens because of some error / mistake.
Edit.: This would be particularly useful because depending on the cluster’s load, logs might not start appearing before almost an hour.
The text was updated successfully, but these errors were encountered: