Closed oschuett closed 4 years ago
Hi @oschuett, thanks for the report.
Before I start fixing the problems could you please provide me with the link to the failing dashboard tests? It appears to me that the link you've posted above does not contain any reference to the logs. Also, does the fact that the tests timed-out mean that we should reduce the number of tests?
In the output you've posted I see two problems with the number of warnings. Do you think they are related to the recent CP2K update? Our tests went fine, so I am a bit puzzled. I assume that locally you have cp2k-7.1, right?
Yes, I'm also a bit puzzled. In the CI it get to example_multistage_h2o_singlepoint.py
and then stalls until the deadline of 3 hours is reached. Unfortunately, the output is not very helpful. Is there maybe any way I could enable more debugging output?
I'm running the test using the CP2K master branch. However, I think the likely cause is https://github.com/aiidateam/aiida-cp2k/commit/a049931946992a5332edc7efd6b9d7e78b42156e.
I was wondering about these lines:
assert calc['output_parameters'].dict.nwarnings == 0
assert calc2['output_parameters'].dict.nwarnings == 1
In CP2K we are rather liberal about adding or removing warnings. So, this is probably not a good properties to assert on.
In CP2K we are rather liberal about adding or removing warnings. So, this is probably not a good properties to assert on.
Good to know, I will then remove it :)
Any news on this?
The CP2K Dashboard test is currently failing. Well, actually it times out. Hence, I ran it again locally and pasted the full output below: