All of lore.kernel.org
 help / color / mirror / Atom feed
From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xenproject.org, osstest-admin@xenproject.org
Subject: [xen-unstable-smoke test] 133375: trouble: broken/pass
Date: Fri, 22 Feb 2019 21:40:09 +0000	[thread overview]
Message-ID: <osstest-133375-mainreport@xen.org> (raw)

flight 133375 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/133375/

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-libvirt        <job status>                 broken

Tests which are failing intermittently (not blocking):
 test-amd64-amd64-libvirt      4 host-install(4)          broken pass in 133371
 test-amd64-amd64-xl-qemuu-debianhvm-i386 10 debian-hvm-install fail in 133371 pass in 133375

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt    13 migrate-support-check fail in 133371 never pass
 test-arm64-arm64-xl-xsm      13 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      14 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl          13 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          14 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  e72ecc7615410e5bf1a1c9a4c7772322c16eeb82
baseline version:
 xen                  db2af23d15077605f286d8ef86c8f5d9c1b8302a

Last test of basis   133343  2019-02-21 03:00:49 Z    1 days
Testing same since   133371  2019-02-22 15:00:34 Z    0 days    2 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Jan Beulich <jbeulich@suse.com>

jobs:
 build-arm64-xsm                                              pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      pass    
 test-amd64-amd64-xl-qemuu-debianhvm-i386                     pass    
 test-amd64-amd64-libvirt                                     broken  


------------------------------------------------------------
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

broken-job test-amd64-amd64-libvirt broken
broken-step test-amd64-amd64-libvirt host-install(4)

Not pushing.

------------------------------------------------------------
commit e72ecc7615410e5bf1a1c9a4c7772322c16eeb82
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Thu Jan 17 12:26:17 2019 +0000

    x86/altp2m: Rework #VE enable/disable paths
    
    Split altp2m_vcpu_{enable,disable}_ve() out of the
    HVMOP_altp2m_vcpu_{enable,disable}_notify marshalling logic.  A future change
    is going to need to call altp2m_vcpu_disable_ve() from the domain_kill() path.
    
    While at it, clean up the logic in altp2m_vcpu_{initialise,destroy}().
    altp2m_vcpu_reset() has no external callers, so fold it into its two
    callsites.  This in turn allows for altp2m_vcpu_destroy() to reuse
    altp2m_vcpu_disable_ve() rather than opencoding it.
    
    No practical change.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: Razvan Cojocaru <rcojocaru@bitdefender.com>
    Acked-by: Jan Beulich <jbeulich@suse.com>
    Release-acked-by: Juergen Gross <jgross@suse.com>

commit 0dfffe01d5681ede6a50c6b57131320d9f4a3361
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Wed Feb 20 13:39:20 2019 +0000

    x86: Improve the efficiency of domain_relinquish_resources()
    
    pci_release_devices() takes the global PCI lock.  Once pci_release_devices()
    has completed, it will be called redundantly each time paging_teardown() and
    vcpu_destroy_pagetables() continue.
    
    This is liable to be millions of times for a reasonably sized guest, and is a
    serialising bottleneck now that domain_kill() can be run concurrently on
    different domains.
    
    Instead of propagating the opencoding of the relinquish state machine, take
    the opportunity to clean it up.
    
    Leave a proper set of comments explaining that domain_relinquish_resources()
    implements a co-routine.  Introduce a documented PROGRESS() macro to avoid
    latent bugs such as the RELMEM_xen case, and make the new PROG_* states
    private to domain_relinquish_resources().
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: Wei Liu <wei.liu2@citrix.com>
    Acked-by: Jan Beulich <jbeulich@suse.com>
    Release-acked-by: Juergen Gross <jgross@suse.com>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

                 reply	other threads:[~2019-02-22 21:40 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=osstest-133375-mainreport@xen.org \
    --to=osstest-admin@xenproject.org \
    --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.