| Re: [chrony-dev] Failure of certain simulation tests |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
- To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
- Subject: Re: [chrony-dev] Failure of certain simulation tests
- From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
- Date: Wed, 24 Apr 2024 12:17:16 +0200
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1713953844; h=from:from:reply-to:subject:subject:date:date:message-id:message-id: to:to:cc:mime-version:mime-version:content-type:content-type: content-transfer-encoding:content-transfer-encoding: in-reply-to:in-reply-to:references:references; bh=lpwbPi1x3I/saBEJss1zXQojemiUu1ntFR/ZWMraC+U=; b=XgVWMkElT99Zu+Ma7Yjyt+bXi84Yhu9TigTg8fNihUrrnLCs20DYEnnPNC12eTkt/YxdEE auACgZexPawOouvy9rD7n2g2avVJJlY1+jAe9gitIoJ7Stk85zWr9ZAAFYum/zJHXYC+uO OmoMUVvkkF7zNBaZchnTj7L6M7N4tGs=
On Thu, Apr 18, 2024 at 07:07:33PM +0200, Vincent Blut wrote:
> Le 2024-04-18 17:19, Miroslav Lichvar a écrit :
> > On Thu, Apr 18, 2024 at 04:06:54PM +0200, Vincent Blut wrote:
> > > So after building clknetsim with these flags, the same tests are still
> > > failing (well I guess so because I stopped the execution after 008-ntpera
> > > has failed since the execution time is so slow on my armhf vm.)
> >
> > Hm, can you please run readelf -sW /usr/sbin/chronyd on this machine?
> > Maybe there is a new 64-bit specific symbol on this arch that needs to
> > be covered.
>
> Attached.
> 62: 00000000 0 FUNC GLOBAL DEFAULT UND __fstat64_time64@GLIBC_2.34 (4)
> 145: 00000000 0 FUNC GLOBAL DEFAULT UND __stat64_time64@GLIBC_2.34 (4)
Missing support for these two caused chronyd and gnutls to
misinterpret the stat data due to unexpected format. There was also a
problem with atol() not parsing 64-bit numbers. It should be fixed now
in git.
Thanks for the report.
--
Miroslav Lichvar
--
To unsubscribe email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "unsubscribe" in the subject.
For help email chrony-dev-request@xxxxxxxxxxxxxxxxxxxx with "help" in the subject.
Trouble? Email listmaster@xxxxxxxxxxxxxxxxxxxx.