From: "Roger Pau Monné" <roger.pau@citrix.com>
To: <xen-devel@lists.xenproject.org>
Subject: osstest: boxes pending comission
Date: Mon, 4 Apr 2022 12:04:03 +0200 [thread overview]
Message-ID: <YkrCkzWRW1xMvzSj@Air-de-Roger> (raw)
Hello,
We have the following boxes pending commission:
italias
* Commission flight at:
http://logs.test-lab.xenproject.org/osstest/logs/169015/
* Issues:
All fine except for the leak-check errors:
LEAKED [process 14559 run-parts] process: root 14559 14558 0 19:29 ? 00:00:00 run-parts --report /etc/cron.daily
LEAKED [process 14558 /bin/sh] process: root 14558 2252 0 19:29 ? 00:00:00 /bin/sh -c run-parts --report /etc/cron.daily
LEAKED [process 14564 /bin/sh] process: root 14564 14559 0 19:29 ? 00:00:00 /bin/sh /etc/cron.daily/apt-compat
LEAKED [process 14571 sleep] process: root 14571 14564 0 19:29 ? 00:00:00 sleep 1091
Those processes are from tasks started by cron. Disabling cron in
rc.d during the host install doesn't seem to be honored later on,
I'm looking into a fix for this.
joubertins
* Commission flight at:
http://logs.test-lab.xenproject.org/osstest/logs/169014/
* Issues:
* 2 network timeouts while connecting to guests. The timeout seems to
be while executing the command, not while establishing the network
connection.
* 1 timeout while running update-grub on bare metal (without Xen
installed). I've already had the raise the timeout for
update-grub to 120s, but that's doesn't seem to always be enough.
debinas
* Commission flight at:
http://logs.test-lab.xenproject.org/osstest/logs/169016/
* No issues: Arm test failing, -amd test failing due to the box being
Intel.
* Will bless tomorrow (5th of April) during the day unless I hear
objections.
next reply other threads:[~2022-04-04 10:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-04 10:04 Roger Pau Monné [this message]
2022-04-11 8:18 ` osstest: boxes pending comission Roger Pau Monné
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YkrCkzWRW1xMvzSj@Air-de-Roger \
--to=roger.pau@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.