Re: [chrony-dev] Failure of certain simulation tests

2024-04-24 Thread Vincent Blut
Le 2024-04-24 12:17, Miroslav Lichvar a écrit :
> 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:  0 FUNCGLOBAL DEFAULT  UND 
> > __fstat64_time64@GLIBC_2.34 (4)
> >145:  0 FUNCGLOBAL 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.

The failing tests that initiated this thread are now fixed, however 
002-largenetwork
still fails though.

> Thanks for the report.

You're welcome.


signature.asc
Description: PGP signature


Re: [chrony-dev] Failure of certain simulation tests

2024-04-24 Thread Miroslav Lichvar
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:  0 FUNCGLOBAL DEFAULT  UND 
> __fstat64_time64@GLIBC_2.34 (4)
>145:  0 FUNCGLOBAL 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-requ...@chrony.tuxfamily.org with "unsubscribe" 
in the subject.
For help email chrony-dev-requ...@chrony.tuxfamily.org with "help" in the 
subject.
Trouble?  Email listmas...@chrony.tuxfamily.org.