Skip to content
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 feedback to inform whether something is happening or not #56

Open
OlivierNicole opened this issue Jul 13, 2023 · 0 comments
Open

Add feedback to inform whether something is happening or not #56

OlivierNicole opened this issue Jul 13, 2023 · 0 comments

Comments

@OlivierNicole
Copy link
Contributor

OlivierNicole commented Jul 13, 2023

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):

$ opam-health-serve --debug --connect /home/olivier/.config/ocluster/OlivierNicole.cap /home/olivier/opam-health-check/state/instance1
Done. Cache prefetching took: 0. seconds

on the server side, and

$ opam-health-check run                                                                       
Sending command…
$

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant