dovetail: posix-clock: Sporadic test failures

dovetail: posix-clock: Sporadic test failures

[Bezdeka, Florian]

Hi,

would be interesting to know if someone else is seeing sporadic test
failures of the posix-clock tests. There are two failures that I can
regularly reproduce on one of our (quite big) test machines:

Hardware info:
32 cores, Intel Xeon E5-2640, Sandy Bridge EP

a)
posix-clock.c:285, assertion failed: diff >= 5500000000LL && diff <= 6500000000LL
/usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument

b) 
posix-clock.c:409, assertion failed: ticks == 1
/usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument

After restarting the test suite multiple times there is normally a run
which does not report any error.

Best regards,
Florian

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: dovetail: posix-clock: Sporadic test failures

[Jan Kiszka]

On 22.06.21 10:09, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> Hi,
> 
> would be interesting to know if someone else is seeing sporadic test
> failures of the posix-clock tests. There are two failures that I can
> regularly reproduce on one of our (quite big) test machines:
> 
> Hardware info:
> 32 cores, Intel Xeon E5-2640, Sandy Bridge EP
> 
> a)
> posix-clock.c:285, assertion failed: diff >= 5500000000LL && diff <= 6500000000LL
> /usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument
> 
> b)
> posix-clock.c:409, assertion failed: ticks == 1
> /usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument
> 
> After restarting the test suite multiple times there is normally a run
> which does not report any error.
> 

There is no ntp etc. service running on that box? We have
systemd-timesyncd disabling via xeno_test now, but that might be
incomplete (or was not used here).

Jan

-- 
Siemens AG, T RDA IOT
Corporate Competence Center Embedded Linux

Re: dovetail: posix-clock: Sporadic test failures

[Bezdeka, Florian]

On Tue, 2021-06-22 at 10:18 +0200, Jan Kiszka wrote:
> On 22.06.21 10:09, Bezdeka, Florian (T RDA IOT SES-DE) wrote:
> > Hi,
> > 
> > would be interesting to know if someone else is seeing sporadic test
> > failures of the posix-clock tests. There are two failures that I can
> > regularly reproduce on one of our (quite big) test machines:
> > 
> > Hardware info:
> > 32 cores, Intel Xeon E5-2640, Sandy Bridge EP
> > 
> > a)
> > posix-clock.c:285, assertion failed: diff >= 5500000000LL && diff <= 6500000000LL
> > /usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument
> > 
> > b)
> > posix-clock.c:409, assertion failed: ticks == 1
> > /usr/xenomai/bin/smokey: test posix_clock failed: Invalid argument
> > 
> > After restarting the test suite multiple times there is normally a run
> > which does not report any error.
> > 
> 
> There is no ntp etc. service running on that box? We have
> systemd-timesyncd disabling via xeno_test now, but that might be
> incomplete (or was not used here).

systemd-timesyncd running and smokey called directly. Thanks! I guess
that will do the trick.

> 
> Jan
>