-
Notifications
You must be signed in to change notification settings - Fork 23
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
UCX warning messages filling log file #244
UCX warning messages filling log file #244
Comments
should I do this or are you onto it? |
Not currently doing it. Just flagged for it to be done. Aside: I usually try and assign issues to me if I am working on them so as not to duplicate effort ... speaking of which ... |
@aidanheerdegen if these PRs look OK, feel free to merge |
(sorry for barging in with this, I just realised I hadn't read your reply carefully) |
No barging. I hadn't planned on doing it myself ... |
Travis is being a pain. Will need to merge without CI, see #245. Sorry, I realise I quoted error, but when I actually tested it I didn't use quotes. My apologies. env:
UCX_LOG_LEVEL: error http://www.yamllint.com says it's ok and functionally the same. I have now tested with quotes and it also works fine. |
no worries @aidanheerdegen - if the quotes are just a cosmetic issue I think we'll cope |
Currently the
access-om2.out
stdout log file has a large number of lines (10425 for a 1 degree model, 278504 for a 0.1 degree model) like this:These may be due to not waiting for non-blocking requests to return (open-mpi/ompi#6376), but in any case are only warnings, and can be ignored.
They can be suppressed by setting an environment variable:
UCX_LOG_LEVEL=error
This should be done for all the configs by adding this to
config.yaml
The text was updated successfully, but these errors were encountered: