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

[Vincent Blut <vincent.debian@xxxxxxx>]

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 reproducibly work.
>
> By the way, I just gave it a shot on an arm64 VM and the rtc test 
> passed flawlessly. Note that this VM is powered by Linux 4.19.x.
> I will soon run that test with a more recent kernel.

I still can’t reproduce the issue on an updated Debian unstable arm64 VM:

$ uname -a
Linux debian-arm64 5.3.0-2-arm64 #1 SMP Debian 5.3.9-3 (2019-11-19) aarch64 GNU/Linux

$ sudo ./run -d 101-rtc
101-rtc   Testing real-time clock:
 non-default settings:
   extra_chronyd_directives=rtcfile /home/guest/chrony-3.5/test/system/tmp/rtcfile
	extra_chronyd_options=-s
	minimal_config=1
 starting chronyd                                              OK
 stopping chronyd                                              OK
 checking message "\(clock off from RTC\|RTC time before last\)"       OK
PASS

I haven't had the opportunity to test this on ppc64el yet.

Attachment: signature.asc
Description: PGP signature