All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: robert.hu@intel.com
Cc: "Tian, Kevin" <kevin.tian@intel.com>,
	"xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
	"Nakajima, Jun" <jun.nakajima@intel.com>,
	guangrong.xiao@intel.com,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	"Wang, Yong Y" <yong.y.wang@intel.com>,
	Jan Beulich <jbeulich@suse.com>,
	"Jin, Gordon" <gordon.jin@intel.com>
Subject: Re: [xen-unstable test] 65141: regressions - FAIL
Date: Fri, 11 Dec 2015 11:49:53 +0000	[thread overview]
Message-ID: <1449834593.29268.4.camel@citrix.com> (raw)
In-Reply-To: <1449806675.13027.14.camel@vmm.sh.intel.com>

On Fri, 2015-12-11 at 12:04 +0800, Robert Hu wrote:
> On Tue, 2015-12-08 at 10:29 +0000, Ian Campbell wrote:
> > On Tue, 2015-12-08 at 08:06 +0000, Hu, Robert wrote:
> > > > 
> > > [...]
> > 
> > Please trim your quotes.
> > 
> > > For your failure, as Kevin mentioned in other mail, we will find
> > > someone
> > > to look into.
> > > Would you find out the detailed log of ' debian-hvm-install--l1--l2'
> > > step? so that he
> > > can start analyze, as I cannot reproduce it right now.
> > > (I didn't managed to find out the log in your web links)
> > 
> > From
> > http://osstest.test-lab.xenproject.org/~osstest/pub/logs/65301/
> > 
> > (in this thread, or any other relevant logs/NNNNN/ link), you can click
> > the
> > "test -amd64 -amd64 -qemuu -nested -intel" header to go to
> > http://osstest.test-lab.xenproject.org/~osstest/pub/logs/65301/test-amd
> > 64-amd64-qemuu-nested-intel/info.html
> > 
> > Then click the result of the "debian-hvm-install/l1/l2" step from that
> > table to go to the step log:
> > http://osstest.test-lab.xenproject.org/~osstest/pub/logs/65301/test-amd
> > 64-amd64-qemuu-nested-intel/16.ts-debian-hvm-install.log
> > 
> > Which I think is what you were after?
> 
> Yes, I had tracked to here. However, from logs like (the above cannot
> open now, let me take the latest for example)
> http://logs.test-lab.xenproject.org/osstest/logs/65633/test-amd64-amd64-q
> emuu-nested-intel/16.ts-debian-hvm-install.log
> [...]
> I can only see L1 try to create L2 timeout. We'd like to what's
> happening inside L1 hypervisor. Where can I find it? or cannot?

Please take a look through the big list of logfiles in the test case
report:
http://logs.test-lab.xenproject.org/osstest/logs/65633/test-amd64-amd64-qemuu-nested-intel/info.html

There is lots of stuff there, including plenty of stuff from the L1 host
(which generally has names beginning <host>_l1.guest.osstest...,
i.e. godello0_l1.guest.osstest)

This should include everything which is normally collected from a host, it
doesn't matter if it is L0 or L1. If something is missing then we should
add it to ts-logs-capture.

Ian.

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

      reply	other threads:[~2015-12-11 11:49 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-27 15:45 [xen-unstable test] 65141: regressions - FAIL osstest service owner
2015-11-27 15:54 ` Ian Jackson
2015-11-30  5:35   ` Hu, Robert
2015-12-02 10:34     ` Ian Campbell
2015-12-02 10:52       ` Jan Beulich
2015-12-02 10:57         ` Andrew Cooper
2015-12-02 11:07         ` Ian Campbell
2015-12-02 13:51       ` Ian Campbell
2015-12-03  5:58         ` Tian, Kevin
2015-12-03  9:25           ` Ian Campbell
2015-12-05  8:09         ` Ian Campbell
2015-12-07 16:18           ` Jan Beulich
2015-12-07 16:28             ` Ian Campbell
2015-12-07 16:48               ` Jan Beulich
2015-12-08  2:46             ` Tian, Kevin
2015-12-08  7:28               ` Jan Beulich
2015-12-08  8:06           ` Hu, Robert
2015-12-08 10:29             ` Ian Campbell
2015-12-09  6:27               ` Robert Hu
2015-12-09  8:35                 ` Jin, Gordon
2015-12-09 10:21                   ` Ian Campbell
2015-12-11  4:04               ` Robert Hu
2015-12-11 11:49                 ` Ian Campbell [this message]

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=1449834593.29268.4.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=gordon.jin@intel.com \
    --cc=guangrong.xiao@intel.com \
    --cc=jbeulich@suse.com \
    --cc=jun.nakajima@intel.com \
    --cc=kevin.tian@intel.com \
    --cc=osstest-admin@xenproject.org \
    --cc=robert.hu@intel.com \
    --cc=xen-devel@lists.xensource.com \
    --cc=yong.y.wang@intel.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.