[chrony-dev] chronyd 3.5 on macOS

2019-12-06 Thread Gerriet M. Denkmann
macOS seems to have two clocks: • a hardware clock, which always runs (even if the device is switched off) • and a software clock, which is used by all apps. When the device starts (or awakes from sleep) the software clock is set from the hardware clock. The problem: adjtime (or whatever

Re: [chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Vincent Blut
On 2019-12-06T16:55+0100, Vincent Blut wrote: On 2019-12-06T10:21+0100, Christian Ehrhardt wrote: Hi chrony-dev, chrony is tested in Debian/Ubuntu on any update of related packages and while that was running I found that arm64 and ppc64 reproducibly hang [1][2]. OTOH arm64 and s390x

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Vincent Blut
On 2019-12-06T10:21+0100, Christian Ehrhardt wrote: Hi chrony-dev, chrony is tested in Debian/Ubuntu on any update of related packages and while that was running I found that arm64 and ppc64 reproducibly hang [1][2]. OTOH arm64 and s390x reproducibly work. By the way, I just gave it a shot on

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Christian Ehrhardt
On Fri, Dec 6, 2019 at 12:51 PM Vincent Blut wrote: > > On 2019-12-06T12:35+0100, Christian Ehrhardt wrote: > >> > > >> > Could that be due to the use of “-x”? IFAIR you have extra stuff on > >> > Ubuntu about that option. > >> > >> I was testing the current master tarball from upstream to avoid

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Vincent Blut
On 2019-12-06T12:35+0100, Christian Ehrhardt wrote: > > Could that be due to the use of “-x”? IFAIR you have extra stuff on > Ubuntu about that option. I was testing the current master tarball from upstream to avoid any confusion. =>

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Christian Ehrhardt
> > > > Could that be due to the use of “-x”? IFAIR you have extra stuff on > > Ubuntu about that option. > > I was testing the current master tarball from upstream to avoid any confusion. > => https://git.tuxfamily.org/chrony/chrony.git/snapshot/chrony-master.tar.gz > > That exposes the same

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Christian Ehrhardt
On Fri, Dec 6, 2019 at 11:32 AM Vincent Blut wrote: > > Hi Christian, > > On 2019-12-06T10:21+0100, Christian Ehrhardt wrote: > >Hi chrony-dev, > >chrony is tested in Debian/Ubuntu on any update of related packages > >and while that was running I found that arm64 and ppc64 reproducibly > >hang

[chrony-dev] Re: Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Vincent Blut
Hi Christian, On 2019-12-06T10:21+0100, Christian Ehrhardt wrote: Hi chrony-dev, chrony is tested in Debian/Ubuntu on any update of related packages and while that was running I found that arm64 and ppc64 reproducibly hang [1][2]. OTOH arm64 and s390x reproducibly work. ^

[chrony-dev] Are there known issues in destructive tests on arm64 or ppc64

2019-12-06 Thread Christian Ehrhardt
Hi chrony-dev, chrony is tested in Debian/Ubuntu on any update of related packages and while that was running I found that arm64 and ppc64 reproducibly hang [1][2]. OTOH arm64 and s390x reproducibly work. Unfortunately the tests do not leave any reasonable debug output, the tests run: