xen-devel.lists.xenproject.org archive mirror
 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-smoke test] 94720: trouble: broken/pass
Date: Mon, 23 May 2016 12:43:09 +0000	[thread overview]
Message-ID: <osstest-94720-mainreport@xen.org> (raw)

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

Failures and problems with tests :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-armhf-armhf-xl           3 host-install(3)         broken REGR. vs. 94666

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     12 migrate-support-check        fail   never pass

version targeted for testing:
 xen                  082096f91a71a28fec0a397cefe598f56ace6a1f
baseline version:
 xen                  ed2cddb66b40cacdefd2e7920bde578d8da67fa9

Last test of basis    94666  2016-05-21 16:00:54 Z    1 days
Testing same since    94720  2016-05-23 11:00:58 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@citrix.com>
  Ian Jackson <ian.jackson@eu.citrix.com>
  Wei Liu <wei.liu2@citrix.com>

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


------------------------------------------------------------
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-step test-armhf-armhf-xl host-install(3)

Not pushing.

------------------------------------------------------------
commit 082096f91a71a28fec0a397cefe598f56ace6a1f
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Tue Apr 26 18:34:34 2016 +0100

    docs/feature: Tweaks to the feature document template
    
    During review of the migration feature doc, some changes were made which
    should have been reflected in the template.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Release-acked-by: Wei Liu <wei.liu2@citrix.com>

commit 3aae91f5c7a536e178bae255320a858d388c7fe6
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Sun May 15 14:09:30 2016 +0100

    docs/xsplice: Fix syntax when compiling to pdf with pandoc
    
    Pandoc (version 1.12.4.2 from Debian Jessie) complains at the embedded \n in
    the signature checking paragraph.
    
      /usr/bin/pandoc --number-sections --toc --standalone misc/xsplice.markdown
        --output pdf/misc/xsplice.pdf
      ! Undefined control sequence.
      l.1085 appended\textasciitilde{}\n
    
    Surround the string in backticks to make it verbatim text.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Reviewed-by: Konrad Rzeszutek Wilk <konrad.wilk@oracle.com>
    Release-acked-by: Wei Liu <wei.liu2@citrix.com>

commit e9bcfcfbde744fea656556b09e35f798144d0bbc
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date:   Mon Apr 25 12:55:12 2016 +0000

    docs/build: Avoid using multi-target pattern rules
    
    Multi-target non-pattern rules and Multi-target pattern rules behave rather
    differently.  From `Pattern Intro':
    
      Pattern rules may have more than one target.  Unlike normal rules, this does
      not act as many different rules with the same prerequisites and commands.
      If a pattern rule has multiple targets, `make' knows that the rule's
      commands are responsible for making all of the targets.  The commands are
      executed only once to make all the targets.
    
    The intended use of the multi-target pattern rules was to avoid repeating the
    identical recipe multiple times.  The issue can be demonstrated with the
    generation of documentation from pandoc source.
    
      ./xen.git$ touch docs/features/template.pandoc
      ./xen.git$ make -C docs/
      # Regenerates html/features/template.html
      ./xen.git$ make -C docs/
      # Regenerates txt/features/template.txt
      ./xen.git$ make -C docs/
      # Regenerates pdf/features/template.pdf
    
    To work around this, there need to be three distinct rules, so the execution
    of one recipe doesn't short ciruit the others.  To avoid copy&paste
    duplication, introduce a metarule, and evalute it for each document target.
    
    As $(PANDOC) is used to generate documentation from different source types,
    the metarule can be extended to also encompas the rule to create pdfs from
    markdown.
    
    Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
    Acked-by: Ian Jackson <ian.jackson@eu.citrix.com>
    Release-acked-by: Wei Liu <wei.liu2@citrix.com>

commit ccf4a5e6db25b229a52e347b88d0c17da6ef31e5
Author: Wei Liu <wei.liu2@citrix.com>
Date:   Mon May 23 11:11:39 2016 +0100

    Revert "Config.mk: update ovmf changeset"
    
    This reverts commit 1542efcea893df874b13b1ea78101e1ff6a55c41. It fails
    consistently on our Debian HVM test when the VM has more than 4G of
    memory.
    
    Signed-off-by: Wei Liu <wei.liu2@citrix.com>
(qemu changes not included)

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
http://lists.xen.org/xen-devel

                 reply	other threads:[~2016-05-23 12:43 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-94720-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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).