All of lore.kernel.org
 help / color / mirror / Atom feed
From: osstest service owner <osstest-admin@xenproject.org>
To: xen-devel@lists.xensource.com, osstest-admin@xenproject.org
Subject: [xen-unstable-coverity test] 117109: trouble: broken
Date: Wed, 13 Dec 2017 22:49:48 +0000	[thread overview]
Message-ID: <osstest-117109-mainreport@xen.org> (raw)

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 coverity-amd64                  <job status>                 broken
 coverity-amd64                4 host-install(4)        broken REGR. vs. 116909

version targeted for testing:
 xen                  43550972395f9a3a48bb4086a0faf0f8d442e37d
baseline version:
 xen                  289adc1c56562d88e50b04245cd2027df8813bf4

Last test of basis   116909  2017-12-06 10:35:57 Z    7 days
Testing same since   117050  2017-12-10 09:18:49 Z    3 days    2 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Jan Beulich <jbeulich@suse.com>
  Julien Grall <julien.grall@linaro.org>

jobs:
 coverity-amd64                                               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


Not pushing.

------------------------------------------------------------
commit 43550972395f9a3a48bb4086a0faf0f8d442e37d
Author: Julien Grall <julien.grall@linaro.org>
Date:   Thu Dec 7 17:18:46 2017 +0000

    xen/arm64: head.S: Introduce macro to load the physical address of a symbol
    
    A lot of places in the ARM64 assembly code requiring to load the
    physical address of a symbol. Rather than open-coding the translation,
    introduce a new macro that will load the physical address of a symbol.
    
    Lastly, use this new macro to replace all the current opencoded version.
    
    Note that most of comments associated to the code changed have been
    removed because the code is now self-explanatory.
    
    Signed-off-by: Julien Grall <julien.grall@linaro.org>
    Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>

commit d81a43fad35820fff73cada44fce2abbcb0a8930
Author: Julien Grall <julien.grall@linaro.org>
Date:   Thu Dec 7 17:19:11 2017 +0000

    xen/arm: Remove unused fixmap slots
    
    There are quite a few fixmap slots that have not been used for a while.
    Remove them.
    
    Signed-off-by: Julien Grall <julien.grall@linaro.org>
    Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>

commit a04458bbf99f8fa64d727342938735727685f093
Author: Jan Beulich <jbeulich@suse.com>
Date:   Thu Dec 7 11:10:12 2017 +0100

    x86: rename DIRTY_GS_BASE_USER
    
    As of commit 91f85280b9 ("x86: fix GS-base-dirty determination") the
    USER part of it isn't really appropriate anymore.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

commit 9d0ded563a31b176bd8fd636c150426f0184b1bc
Author: Jan Beulich <jbeulich@suse.com>
Date:   Thu Dec 7 11:09:31 2017 +0100

    mm: don't use domain_shutdown() when re-offlining a page
    
    It goes all silent, leaving open what has actually caused the crash.
    Use domain_crash() instead, which leaves a log message before calling
    domain_shutdown(..., SHUTDOWN_crash).
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Acked-by: Andrew Cooper <andrew.cooper3@citrix.com>

commit 0def739d77c14b570cf30b6156afea0f5929b038
Author: Jan Beulich <jbeulich@suse.com>
Date:   Thu Dec 7 11:08:41 2017 +0100

    pdx: correct indentation
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Andrew Cooper <andrew.cooper3@citrix.com>

commit 5fcb26e69e8089e20c9168774bee681b8f5a3187
Author: Jan Beulich <jbeulich@suse.com>
Date:   Wed Dec 6 12:50:23 2017 +0100

    x86/HVM: don't retain emulated insn cache when exiting back to guest
    
    vio->mmio_retry is being set when a repeated string insn is being split
    up. In that case we'll exit to the guest, expecting immediate re-entry.
    Interruptions, however, may be serviced by the guest before re-entry
    from the repeated string insn. Any emulation needed in the course of
    handling the interruption must not fetch from the internally maintained
    cache.
    
    Signed-off-by: Jan Beulich <jbeulich@suse.com>
    Reviewed-by: Paul Durrant <paul.durrant@citrix.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:[~2017-12-13 22:49 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-117109-mainreport@xen.org \
    --to=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \
    /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.