Public bug reported: Checking last eoan merge I realized that some tests were failing for chrony:
https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 But eoan ran autopkgtests okay when the trigger was chrony/3.5-2ubuntu2 (this last merge): http://autopkgtest.ubuntu.com/packages/chrony/eoan/amd64 Despite having failed for the previous 12 times (eoan). Now, for the first time, we have the same failure for disco: http://autopkgtest.ubuntu.com/packages/chrony/disco/amd64 http://bit.ly/2LpMx4G """ make: Leaving directory '/tmp/autopkgtest.pBHSAl/build.WCD/src/test/simulation/clknetsim' ... 110-chronyc .................... PASS 111-knownclient xxxxxxxxxxxxxxxxxxxx FAIL 112-port xxxxxxxxxxxxxxxxxxxx FAIL 121-orphan .................... PASS ... SUMMARY: TOTAL 50 PASSED 48 FAILED 2 (111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 265) """ And I'm able to reproduce locally: """ (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 server_conf=server 192.168.123.2 noselect acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: network with 1*1 servers and 1 clients: non-default settings: starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking source selection: node 2: OK checking mean/min incoming/outgoing packet interval: node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK checking clock sync time, max/rms time/freq error: node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK checking port numbers in packet log: node 1: BAD node 2: BAD network with 1*1 servers and 1 clients: non-default settings: client_conf=acquisitionport 123 starting node 1: OK starting node 2: OK running simulation: OK checking chronyd exit: node 1: OK node 2: OK checking port numbers in packet log: node 1: BAD node 2: BAD FAIL """ When doing verification for an iproute2 bug (LP: #1831775) we faced the 1st failure in autopkgtests for chrony in disco (at least from the ones I can check from autopkgtests.ubuntu.com). ** Affects: chrony (Ubuntu) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Affects: chrony (Ubuntu Disco) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Affects: chrony (Ubuntu Eoan) Importance: Medium Assignee: Rafael David Tinoco (rafaeldtinoco) Status: Confirmed ** Description changed: Checking last eoan merge I realized that some tests were failing for chrony: https://code.launchpad.net/~paelzer/ubuntu/+source/chrony/+git/chrony/+merge/369588/comments/967625 But eoan ran autopkgtests okay when the trigger was chrony/3.5-2ubuntu2 (this last merge): http://autopkgtest.ubuntu.com/packages/chrony/eoan/amd64 Despite having failed for the previous 12 times (eoan). Now, for the first time, we have the same failure for disco: http://autopkgtest.ubuntu.com/packages/chrony/disco/amd64 http://bit.ly/2LpMx4G """ make: Leaving directory '/tmp/autopkgtest.pBHSAl/build.WCD/src/test/simulation/clknetsim' ... 110-chronyc .................... PASS 111-knownclient xxxxxxxxxxxxxxxxxxxx FAIL 112-port xxxxxxxxxxxxxxxxxxxx FAIL 121-orphan .................... PASS ... SUMMARY: - TOTAL 50 - PASSED 48 - FAILED 2 (111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 265) + TOTAL 50 + PASSED 48 + FAILED 2 (111-knownclient 112-port) (255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 255 256 257 258 259 260 261 262 263 264 265 266 267 268 269 270 271 272 273 274 265) """ And I'm able to reproduce locally: + """ (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./111-knownclient Testing reply to client configured as server: - network with 1*1 servers and 1 clients: - non-default settings: - client_conf=acquisitionport 123 - server_conf=server 192.168.123.2 noselect acquisitionport 123 - starting node 1: OK - starting node 2: OK - running simulation: OK - checking chronyd exit: - node 1: OK - node 2: OK - checking source selection: - node 2: OK - checking port numbers in packet log: - node 1: BAD - node 2: BAD + network with 1*1 servers and 1 clients: + non-default settings: + client_conf=acquisitionport 123 + server_conf=server 192.168.123.2 noselect acquisitionport 123 + starting node 1: OK + starting node 2: OK + running simulation: OK + checking chronyd exit: + node 1: OK + node 2: OK + checking source selection: + node 2: OK + checking port numbers in packet log: + node 1: BAD + node 2: BAD FAIL AND (c)inaddy@iproute2verification:~/work/sources/ubuntu/chrony/test/simulation$ ./112-port Testing port and acquisitionport directives: - network with 1*1 servers and 1 clients: - non-default settings: - starting node 1: OK - starting node 2: OK - running simulation: OK - checking chronyd exit: - node 1: OK - node 2: OK - checking source selection: - node 2: OK - checking mean/min incoming/outgoing packet interval: - node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK - node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK - checking clock sync time, max/rms time/freq error: - node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK - checking port numbers in packet log: - node 1: BAD - node 2: BAD - network with 1*1 servers and 1 clients: - non-default settings: - client_conf=acquisitionport 123 - starting node 1: OK - starting node 2: OK - running simulation: OK - checking chronyd exit: - node 1: OK - node 2: OK - checking port numbers in packet log: - node 1: BAD - node 2: BAD + network with 1*1 servers and 1 clients: + non-default settings: + starting node 1: OK + starting node 2: OK + running simulation: OK + checking chronyd exit: + node 1: OK + node 2: OK + checking source selection: + node 2: OK + checking mean/min incoming/outgoing packet interval: + node 1: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK + node 2: 2.74e+02 2.74e+02 6.40e+01 6.40e+01 OK + checking clock sync time, max/rms time/freq error: + node 2: 132 9.29e-05 1.21e-06 5.77e-05 1.01e-07 OK + checking port numbers in packet log: + node 1: BAD + node 2: BAD + network with 1*1 servers and 1 clients: + non-default settings: + client_conf=acquisitionport 123 + starting node 1: OK + starting node 2: OK + running simulation: OK + checking chronyd exit: + node 1: OK + node 2: OK + checking port numbers in packet log: + node 1: BAD + node 2: BAD FAIL + """ + + When doing verification for an iproute2 bug (LP: #1831775) we faced the + 1st failure in autopkgtests for chrony in disco (at least from the ones + I can check from autopkgtests.ubuntu.com). ** Changed in: chrony (Ubuntu) Status: New => Confirmed ** Also affects: chrony (Ubuntu Eoan) Importance: Undecided Status: Confirmed ** Also affects: chrony (Ubuntu Disco) Importance: Undecided Status: New ** Changed in: chrony (Ubuntu Disco) Status: New => Confirmed ** Changed in: chrony (Ubuntu Disco) Importance: Undecided => Medium ** Changed in: chrony (Ubuntu Eoan) Importance: Undecided => Medium ** Changed in: chrony (Ubuntu Disco) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) ** Changed in: chrony (Ubuntu Eoan) Assignee: (unassigned) => Rafael David Tinoco (rafaeldtinoco) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
