I verified the test results and am satisfied that they show the executed planned test case, and that the results are correct.
In such types of test plans, I would suggest that in the future you also add output showing whether the relevant artifact you are looking for is there or not. For example, in the case of crash files, show that they exist when expected, and don't exist when not expected. I would also have looked at log files, either from systemd, or the daemon itself, which should have some sort of indication that a crash happened.
That's better than just "I've noticed that nothing has changed there, so the problem still existed", for example.
The package built correctly in all architectures and Ubuntu releases it was meant for.
There are no DEP8 regressions.
There is no SRU freeze ongoing at the moment.
There is no halted phasing on the previous update.
I verified the test results and am satisfied that they show the executed planned test case, and that the results are correct.
In such types of test plans, I would suggest that in the future you also add output showing whether the relevant artifact you are looking for is there or not. For example, in the case of crash files, show that they exist when expected, and don't exist when not expected. I would also have looked at log files, either from systemd, or the daemon itself, which should have some sort of indication that a crash happened.
That's better than just "I've noticed that nothing has changed there, so the problem still existed", for example.
The package built correctly in all architectures and Ubuntu releases it was meant for.
There are no DEP8 regressions.
There is no SRU freeze ongoing at the moment.
There is no halted phasing on the previous update.