[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 165638: regressions - FAIL
flight 165638 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/165638/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-debianhvm-amd64 11 leak-check/basis(11) fail REGR. vs. 165635 test-amd64-amd64-libvirt 11 leak-check/basis(11) fail REGR. vs. 165635 test-arm64-arm64-xl-xsm 11 leak-check/basis(11) fail REGR. vs. 165635 test-armhf-armhf-xl 11 leak-check/basis(11) fail REGR. vs. 165635 version targeted for testing: xen 3ae80dea4601764818d1e5b84bd1e4479c0d4790 baseline version: xen c11b8d25fbe9c0155e91409594ea6701008409ed Last test of basis 165635 2021-10-18 13:00:26 Z 0 days Testing same since 165638 2021-10-18 16:01:36 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Ian Jackson <iwj@xxxxxxxxxxxxxx> Juergen Gross <jgross@xxxxxxxx> jobs: build-arm64-xsm pass build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl fail test-arm64-arm64-xl-xsm fail test-amd64-amd64-xl-qemuu-debianhvm-amd64 fail test-amd64-amd64-libvirt fail ------------------------------------------------------------ sg-report-flight on osstest.test-lab.xenproject.org logs: /home/logs/logs images: /home/logs/images Logs, config files, etc. are available at http://logs.test-lab.xenproject.org/osstest/logs Explanation of these reports, and of osstest in general, is at http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master Test harness code can be found at http://xenbits.xen.org/gitweb?p=osstest.git;a=summary Not pushing. ------------------------------------------------------------ commit 3ae80dea4601764818d1e5b84bd1e4479c0d4790 Author: Juergen Gross <jgross@xxxxxxxx> Date: Fri Sep 10 07:55:17 2021 +0200 stubdom: disable building pv-grub The stubdom based pv-grub is using a very outdated version of grub (0.97) and should not be used any longer. Mainline grub has support for PV guests for a long time now, so that should be used as a boot loader of a PV domain. So disable building pv-grub per default. In case someone really wants to continue using it he/she can still use a pv-grub binary from an older Xen version or manually enable building it via: configure --enable-pv-grub [ This was already disabled in osstest by 8dee6e333622 "make-flight: Drop pvgrub (pvgrub1) tests" -iwj ] Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Samuel Thibault <samuel.thibault@xxxxxxxxxxxx> Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> commit 9cfeb83cbe23a873de512211d7ecd989348b9df0 Author: Juergen Gross <jgross@xxxxxxxx> Date: Tue Oct 12 15:41:48 2021 +0200 tools/xenstore: set open file descriptor limit for xenstored Add a configuration item for the maximum number of open file descriptors xenstored should be allowed to have. The default should be "unlimited" in order not to restrict xenstored in the number of domains it can support, but unfortunately the kernel is normally limiting the maximum value via /proc/sys/fs/nr_open [1], [2]. So check that file to exist and if it does, limit the maximum value to the one specified by /proc/sys/fs/nr_open. As an aid for the admin configuring the value add a comment specifying the common needs of xenstored for the different domain types. [1]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=60fd760fb9ff7034360bab7137c917c0330628c2 [2]: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/?id=0c2d64fb6cae9aae480f6a46cfe79f8d7d48b59f Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> commit f282182af32939107d47943aba242d3189ec6f90 Author: Juergen Gross <jgross@xxxxxxxx> Date: Tue Oct 12 15:41:47 2021 +0200 tools/xenstore: set oom score for xenstore daemon on Linux Xenstored is absolutely mandatory for a Xen host and it can't be restarted, so being killed by OOM-killer in case of memory shortage is to be avoided. Set /proc/$pid/oom_score_adj (if available) per default to -500 (this translates to 50% of dom0 memory size) in order to allow xenstored to use large amounts of memory without being killed. The percentage of dom0 memory above which the oom killer is allowed to kill xenstored can be set via XENSTORED_OOM_MEM_THRESHOLD in xencommons. Make sure the pid file isn't a left-over from a previous run delete it before starting xenstored. Signed-off-by: Juergen Gross <jgross@xxxxxxxx> Reviewed-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> Release-Acked-by: Ian Jackson <iwj@xxxxxxxxxxxxxx> (qemu changes not included)
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |