| Re: [chrony-dev] 4.0 release soon |
[ Thread Index |
Date Index
| More chrony.tuxfamily.org/chrony-dev Archives
]
On Mon, Oct 5, 2020 at 9:09 AM Miroslav Lichvar <mlichvar@xxxxxxxxxx> wrote:
>
> On Sat, Oct 03, 2020 at 02:07:23PM +0200, Vincent Blut wrote:
> > So I find the time to debug this. It was due to a packaging error I made
> > when removing an old migration code snippet. Fixed in git!
> >
> > On the compilation side, all seems well [1].
As mentioned I'm trying to verify the same on Ubuntu with glibc2.32.
Compilation is fine here as well.
Upgrade in system worked fine
ubuntu@ubuntu:~$ sudo apt dist-upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
chrony
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 259 kB of archives.
After this operation, 75.8 kB of additional disk space will be used.
Do you want to continue? [Y/n] Y
Get:1 http://ppa.launchpad.net/ci-train-ppa-service/4299/ubuntu
groovy/main amd64 chrony amd64 4.0~pre4-2ubuntu1~ppa1 [259 kB]
Fetched 259 kB in 0s (1133 kB/s)
(Reading database ... 116880 files and directories currently installed.)
Preparing to unpack .../chrony_4.0~pre4-2ubuntu1~ppa1_amd64.deb ...
Unpacking chrony (4.0~pre4-2ubuntu1~ppa1) over (3.5.1-1ubuntu1) ...
Setting up chrony (4.0~pre4-2ubuntu1~ppa1) ...
Installing new version of config file /etc/apparmor.d/usr.sbin.chronyd ...
Installing new version of config file /etc/default/chrony ...
Installing new version of config file /etc/dhcp/dhclient-exit-hooks.d/chrony ...
Installing new version of config file /etc/init.d/chrony ...
Installing new version of config file /etc/network/if-post-down.d/chrony ....
Installing new version of config file /etc/network/if-up.d/chrony ...
Installing new version of config file /etc/ppp/ip-down.d/chrony ...
Installing new version of config file /etc/ppp/ip-up.d/chrony ...
Processing triggers for man-db (2.9.3-2) ...
Processing triggers for systemd (246.6-1ubuntu1) ...
This is a box with a USB GPS attached,
checking this before/after upgrade shows that it seems ok from this
simple check at least.
ubuntu@ubuntu:~$ systemctl status chronyd gpsd; chronyc sources
● chrony.service - chrony, an NTP client/server
Loaded: loaded (/lib/systemd/system/chrony.service; enabled;
vendor preset: enabled)
Active: active (running) since Tue 2020-10-06 06:27:31 UTC; 2min 40s ago
Docs: man:chronyd(8)
man:chronyc(1)
man:chrony.conf(5)
Main PID: 107300 (chronyd)
Tasks: 2 (limit: 18472)
Memory: 2.2M
CGroup: /system.slice/chrony.service
├─107300 /usr/sbin/chronyd -F -1
└─107301 /usr/sbin/chronyd -F -1
Oct 06 06:27:31 ubuntu systemd[1]: Starting chrony, an NTP client/server...
Oct 06 06:27:31 ubuntu chronyd[107300]: chronyd version 4.0-pre4
starting (+CMDMON +NTP +REFCLOCK +RTC +PRIVDROP +SCFILTER +SIGND
+ASYNCDNS +NTS +SECHASH +IPV6 -DEBUG)
Oct 06 06:27:31 ubuntu chronyd[107300]: Frequency -69.194 +/- 3.215
ppm read from /var/lib/chrony/chrony.drift
Oct 06 06:27:31 ubuntu chronyd[107300]: Loaded seccomp filter
Oct 06 06:27:31 ubuntu systemd[1]: Started chrony, an NTP client/server.
Oct 06 06:27:38 ubuntu chronyd[107300]: Selected source 89.163.144.30
(0.ubuntu.pool.ntp.org)
Oct 06 06:29:56 ubuntu chronyd[107300]: Selected source PPS
● gpsd.service - GPS (Global Positioning System) Daemon
Loaded: loaded (/lib/systemd/system/gpsd.service; enabled; vendor
preset: enabled)
Active: active (running) since Tue 2020-10-06 06:29:01 UTC; 1min 10s ago
TriggeredBy: ● gpsd.socket
Process: 107534 ExecStart=/usr/sbin/gpsd $GPSD_OPTIONS $DEVICES
(code=exited, status=0/SUCCESS)
Main PID: 107535 (gpsd)
Tasks: 2 (limit: 18472)
Memory: 1.0M
CGroup: /system.slice/gpsd.service
└─107535 /usr/sbin/gpsd -n /dev/ttyUSB0
Oct 06 06:29:01 ubuntu systemd[1]: Starting GPS (Global Positioning
System) Daemon...
Oct 06 06:29:01 ubuntu systemd[1]: Started GPS (Global Positioning
System) Daemon.
MS Name/IP address Stratum Poll Reach LastRx Last sample
===============================================================================
#x GPS 0 4 377 7 -861ms[ -861ms] +/- 200ms
#* PPS 0 4 17 8 +234us[ +929us] +/- 2551ns
^- alphyn.canonical.com 2 6 77 22 -1531us[ -699us] +/- 101ms
^- golem.canonical.com 2 6 77 24 -813us[ +25us] +/- 50ms
^- chilipepper.canonical.com 2 6 77 23 -873us[ -38us] +/- 39ms
^- pugot.canonical.com 2 6 77 23 -968us[ -134us] +/- 45ms
^- house.root.project-creat> 2 6 77 24 -1073us[ -451us] +/- 26ms
^- funky.f5s.de 2 6 77 23 -826us[+6843ns] +/- 62ms
^- monkey.spod.net 2 6 77 24 -777us[ +59us] +/- 17ms
^- rondra.lf-net.org 2 6 77 24 -443us[ +180us] +/- 42ms
> Thanks. Is it possible to run all tests in the test suite on those
> archs?
At build time it runs the unit-tests - you can find the links for
these in the build logs at
Ubuntu: https://launchpad.net/~ci-train-ppa-service/+archive/ubuntu/4299/+packages
Debian: https://buildd.debian.org/status/package.php?p=chrony&suite=experimental
The full simulation and system test suite is executed not at build,
but autopkgtest time.
Not sure if that can be run for debian/experimental but I was doing so
for Ubuntu.
Worked:
amd64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4299/groovy/amd64/c/chrony/20201006_074508_4c4b8@/log.gz
ppc64el: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4299/groovy/ppc64el/c/chrony/20201006_075236_e2e9c@/log.gz
s390x: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4299/groovy/s390x/c/chrony/20201006_074002_e2e9c@/log.gz
Issues:
armhf: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4299/groovy/armhf/c/chrony/20201006_082406_e2e9c@/log.gz
arm64: https://objectstorage.prodstack4-5.canonical.com/v1/AUTH_77e2ada1e7a84929a74ba3b87153c0ac/autopkgtest-groovy-ci-train-ppa-service-4299/groovy/arm64/c/chrony/20201006_084248_e2e9c@/log.gz
Both fail in 007-cmdmon fails of the system tests, the other tests all
pass on armhf/arm64.
> Anyway, I found few more issues in my testing, so I'd like to give
> it at least one extra day for fixing and testing.
>
> --
> 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.
>
--
Christian Ehrhardt
Staff Engineer, Ubuntu Server
Canonical Ltd
--
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.