| [chrony-dev] "make check" failure on Centos 6.10 for chrony 3.4 |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
Always liking to run the chrony check testing (with the current release of clknetsim)....I am failing a few of the tests.
One note, I ran the tests on a Centos 6.10 patched to current:
$ make check
..
..
Testing addrfilt PASS
Testing clientlog PASS
Testing hash PASS
Testing hwclock PASS
Testing keys PASS
Testing ntp_core PASS
Testing ntp_sources PASS
Testing regress PASS
Testing samplefilt PASS
Testing smooth PASS
Testing sources PASS
Testing util PASS
make[1]: Leaving directory `/home/parkerm/proj/chrony34/chrony-3.4/test/unit'
cd test/simulation && ./run -i 20 -m 2
001-defaults .................... PASS
002-largenetwork .................... PASS
003-largefreqoffset .................... PASS
004-largetimeoffset .................... PASS
005-externalstep .................... PASS
006-largejitter .................... PASS
007-largewander .................... PASS
008-ntpera .................... PASS
009-sourceselection .................... PASS
010-multrecv .................... PASS
011-asymjitter .................... PASS
012-daemonts .................... PASS
101-poll .................... PASS
102-iburst .................... PASS
103-initstepslew .................... PASS
104-driftfile .................... PASS
105-ntpauth .................... PASS
106-refclock xxxxxxxxxxxxxxxxxxxx FAIL
107-allowdeny .................... PASS
108-peer ........x........... PASS
109-makestep .................... PASS
110-chronyc .................... PASS
111-knownclient .................... PASS
112-port .................... PASS
113-leapsecond .................... PASS
114-presend ...............x.... PASS
115-cmdmontime .................... PASS
116-minsources .................... PASS
117-fallbackdrift .................... PASS
118-maxdelay .................... PASS
119-smoothtime .................... PASS
120-selectoptions .x.................. PASS
121-orphan .................... PASS
122-xleave .................... PASS
123-mindelay .................... PASS
124-tai .................... PASS
125-packetloss .................... PASS
126-burst .................... PASS
127-filter .................... PASS
128-nocontrol .................... PASS
129-reload .................... PASS
130-quit .................... PASS
131-maxchange .................... PASS
132-logchange .................... PASS
133-hwtimestamp xxxxxxxxxxxxxxxxxxxx FAIL
134-log xxxxxxxxxxxxxxxxxxxx FAIL
135-ratelimit .................... PASS
136-broadcast .................... PASS
201-freqaccumulation .................... PASS
202-prefer .................... PASS
SUMMARY:
TOTAL 50
PASSED 47
FAILED 3 (106-refclock 133-hwtimestamp 134-log) (192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 200 207 193 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211 192 193 194 195 196 197 198 199 200 201 202 203 204 205 206 207 208 209 210 211)
SKIPPED 0 ()
make: *** [check] Error 1
Do you all think these FAILures are ok and that the result of the compilation will function properly on the Centos 6.10 platform?
BTW, no compilation or loading errors just running ./configure and then make.
I haven't tried a RHEL 6.9 platform yet.
-----Original Message-----
From: Miroslav Lichvar <mlichvar@xxxxxxxxxx>
Sent: Thursday, September 20, 2018 00:29
To: chrony-dev@xxxxxxxxxxxxxxxxxxxx
Subject: -EXT-Re: [chrony-dev] chrony-3.4 released
On Thu, Sep 20, 2018 at 07:42:41AM +1200, Bryan Christianson wrote:
> Thank you Miroslav
>
> All working well on macOS 10.14 (Mojave)
That's great.
Do we still need that detection of broken adjtime()?
--
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.
--
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.