Noureddine

I think this is referring to device configuration of which NTP server to use rather than a test module. We don't strictly need a local DAQ NTP server, as the...

My apologies @pbatta completely missed the notification. I suggest this test uses the hostname only. I understand the expectation is now that NTP through DHCP is not required? If we...

Thanks @grafnu, all understood and clear now. I think we can have both as separate test line items. This possibilities would be: | NTP/DNS | NTP/DHCP | | | -...

Seems to be due to a misconfiguration of the DHCP module at my end. I was using the the module config from resource/baseline which appears to not be up to...

Thanks Trevor the prompt response. I tried with with `’port’ : 1` fixed it for me. I had to run `bin/net_clean` though. Thank you - all working now. I’ll update...

@pisuke to clarify, the new table doesn't give a total number of tests passed for each category, only total number of tests for each category and then a breakdown per...

Hello, The error here is that the devices metadata here has a pointset, therefore it is required that the state message also includes the pointset blocks with the points the...

I agree with you, I think null should be acceptable value. Tagging @grafnu

@grafnu @DollyGodet @pisuke any views as to which should be correct? In my mind, `INFO` for all the config apply/parse/receive events was excessive, and I'm leaning towards `DEBUG` or `NOTICE`...

I confused the levels of NOTICE and INFO! The levels you've suggested sound good to me