Closed jouvin closed 8 years ago
I should have added that this is a very bad problem as after occuring, ncm-cdispd
doesn't process any new profile...
very serious indeed. i never saw it, and it looks strange given https://github.com/quattor/ncm-cdispd/blob/809c910171b0c5ee306f21564db12cdf71167bd9/src/main/scripts/ncm-cdispd#L717
patch should be trivial, but it would be good to know where the undef comes from.
if it is easy to reproduce, i'm very interested in a --debug 5
output
the launch_ncd
code seems to be prepared for it...
Thanks. I'll try to deploy it tomorrow. Unfortunately, I don't know how to trigger it as it doesn't seem to happen everytime...
I saw already several times the following error in
ncm-cdispd
:The faulty line is:
A code added in 809c910171b0c5ee306f21564db12cdf71167bd9. I remember commenting on this change that the initial state should be checked (as having unit test for ncm-cdispd is almost impossible)... I'm afraid we missed something. It seems to happen after a new profile was received identical to the previous one. The log lines before the error are typically: