[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
** Changed in: chrony (Ubuntu Disco) Status: Fix Committed => Won't Fix -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Won't Fix Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- 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 FAIL 112-port 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
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
don't mark bugs fixed when the package has only been uploaded to the SRU queue ** Changed in: chrony (Ubuntu Disco) Status: Fix Released => In Progress ** Changed in: chrony (Ubuntu Disco) Status: In Progress => Fix Committed ** Tags added: verification-needed verification-needed-disco -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Fix Committed Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- 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 FAIL 112-port 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
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
** Changed in: chrony (Ubuntu Disco) Status: In Progress => Fix Released -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Fix Released Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- 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 FAIL 112-port 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
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
After discussion decided that it is not a dup, they just share the symptom to hit at autopkgtest time. ** This bug is no longer a duplicate of bug 1836882 autopkgtest due to other packages changing -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: In Progress Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- 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 FAIL 112-port 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:
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
> TODO: marking as a duplicate of: LP: #1736882 TODO: marking as a duplicate of: LP: #1836882 ** This bug has been marked a duplicate of bug 1836882 autopkgtest due to other packages changing -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Triaged Status in chrony source package in Eoan: Fix Released Bug description: [Impact] * Recent changes have caused the chrony autopkgtests to fail. In this case upstream of chrony and the clk tests changed, which need to be back under control to match what works reliably for Disco. * Later versions have this fixed, backport the changes to fix it in Disco as well [Test Case] * Let the autopkgtests run (which is part of the proposed migration anyway) Sniffs already show them completing: https://bileto.ubuntu.com/excuses/3759/disco.html [Regression Potential] * There is no functional change, only the self-tests as well the autopkgtest execution are changed. The one source for a regression could be that the rebuild picks something up that triggers a behavior change. But the PPA builds have not shown something (at least not something obvious) [Other Info] * This is one of the cases where the actual package as used by the user has no bug. I'm unsure how to proceed. Do we want to push it just to disco-proposed but keep it there (to avoid downloads for "nothing")? I know rbasak wanted to discuss that in the SRU team for the even worse https://bugs.launchpad.net/cloud-archive/+bug/1829823/comments/14 To some extend this come under the same banner. * If this is denied from SRU for this reason I'd ask to add a force- badtest as a replacement to unblock proposed migration. --- 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 FAIL 112-port 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
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
** Changed in: chrony (Ubuntu Eoan) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) ** Changed in: chrony (Ubuntu Disco) Status: Won't Fix => Triaged -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Triaged Status in chrony source package in Eoan: Fix Released Bug description: 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 FAIL 112-port 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). To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chrony/+bug/1836929/+subscriptions ___ Mailing list: https://launchpad.net/~group.of.nepali.translators Post to : group.of.nepali.translators@lists.launchpad.net Unsubscribe : https://launchpad.net/~group.of.nepali.translators More help : https://help.launchpad.net/ListHelp
[Group.of.nepali.translators] [Bug 1836929] Re: chrony has migration regressions from autopkgtests (disco/eoan)
I have checked all other versions and they have passed latest autopkgtest because the change, to clknetsim that caused the issue was made in: Date: Tue Jun 11 17:05:22 2019 +0200 And debian fix was made in: Date: Tue, 18 Jun 2019 15:41:50 +0200 But the tests never ran after that. I'm requesting all chrony tests: Xenial/Bionic/Cosmic/Disco to be marked as known issues in ubuntu autopkgtests. ** Also affects: chrony (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Cosmic) Importance: Undecided Status: New ** Also affects: chrony (Ubuntu Xenial) Importance: Undecided Status: New ** Changed in: chrony (Ubuntu Cosmic) Status: New => Won't Fix ** Changed in: chrony (Ubuntu Bionic) Status: New => Won't Fix ** Changed in: chrony (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: chrony (Ubuntu Cosmic) Importance: Undecided => Medium ** Changed in: chrony (Ubuntu Bionic) Importance: Undecided => Medium ** Changed in: chrony (Ubuntu Xenial) Importance: Undecided => Medium ** Changed in: chrony (Ubuntu Disco) Assignee: Rafael David Tinoco (rafaeldtinoco) => (unassigned) -- You received this bug notification because you are a member of नेपाली भाषा समायोजकहरुको समूह, which is subscribed to Xenial. Matching subscriptions: Ubuntu 16.04 Bugs https://bugs.launchpad.net/bugs/1836929 Title: chrony has migration regressions from autopkgtests (disco/eoan) Status in chrony package in Ubuntu: Fix Released Status in chrony source package in Xenial: Won't Fix Status in chrony source package in Bionic: Won't Fix Status in chrony source package in Cosmic: Won't Fix Status in chrony source package in Disco: Won't Fix Status in chrony source package in Eoan: Fix Released Bug description: 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 FAIL 112-port 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). To manage
