All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Hu, Robert" <robert.hu@intel.com>
To: Ian Jackson <Ian.Jackson@eu.citrix.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Ian Campbell <ian.campbell@citrix.com>,
	"Jin, Gordon" <gordon.jin@intel.com>
Subject: Re: Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing)
Date: Fri, 13 Nov 2015 01:53:50 +0000	[thread overview]
Message-ID: <9E79D1C9A97CFD4097BCE431828FDD31023862DB@SHSMSX103.ccr.corp.intel.com> (raw)
In-Reply-To: <22084.47601.565061.526718@mariner.uk.xensource.com>

[-- Attachment #1: Type: text/plain, Size: 2620 bytes --]

> -----Original Message-----
> From: Ian Jackson [mailto:Ian.Jackson@eu.citrix.com]
> Sent: Friday, November 13, 2015 12:10 AM
> To: Hu, Robert <robert.hu@intel.com>
> Cc: Ian Campbell <ian.campbell@citrix.com>; Jin, Gordon
> <gordon.jin@intel.com>; xen-devel@lists.xenproject.org
> Subject: RE: Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2
> 10-26/26] Nested HVM testing)
> 
> Hu, Robert writes ("RE: Osstest nested patch v15 (was RE: [OSSTEST PATCH
> v14 PART 2 10-26/26] Nested HVM testing)"):
> > Here is detail logs
> 
> Thanks.  Most of this is fine.
> 
> > 2015-11-12 03:21:43 Z serial: collecting logs for l1.guest.osstest
> > Use of uninitialized value in concatenation (.) or string at
> Osstest/Serial/guest.pm line 91.
> > Use of uninitialized value in concatenation (.) or string at
> Osstest/Serial/guest.pm line 91.
> 
> This is me being idiotic.  I have a patch below which I'm pretty sure
> will fix it.  Anyway, I don't think I need it retested for this reason
> because this is just a wrong log message, which we can fix in-tree if
> necessary.
> 
> What I want to know is whether the l1 serial console logfile was
> collected, and contains the debug output.
> 
> I think you should find this in the output of the ts-logs-capture for
> the host (L0).  Something like
> 
> 2015-11-12 03:21:48 Z fetching
> /var/log/xen/osstest-serial-l1.guest.osstest.log to
> MYHOSTNAME---var-log-xen-osstest-serial-l1.guest.osstest.log
[Hu, Robert] 

Yes. In last test step, ts-logs-capture host, I can see

2015-11-12 03:22:06 Z fetching /var/log/xen/osstest-serial-l1.guest.osstest.log to osstest-host2---var-log-xen-osstest-serial-l1.guest.osstest.log
2015-11-12 03:22:06 Z executing scp ... root@192.168.199.70:/var/log/xen/osstest-serial-l1.guest.osstest.log logs/standalone/test-amd64-amd64-qemuu-nested/osstest-host2---var-log-xen-osstest-serial-l1.guest.osstest.log


> 
> If you look in the logs directory, do you have a file matching
> *-serial-l1.* ?  If so, can you send it to me ?  I think (hope)! it
> will have the debug keys.
[Hu, Robert] 

See attached. Seems no debug keys in it.

> 
> Thanks,
> Ian.
> 
> diff --git a/Osstest/Serial/guest.pm b/Osstest/Serial/guest.pm
> index 286773d..2511556 100644
> --- a/Osstest/Serial/guest.pm
> +++ b/Osstest/Serial/guest.pm
> @@ -86,7 +86,7 @@ sub keys_shutdown {
>  }
> 
>  sub fetch_logs {
> -    my ($mo);
> +    my ($mo) = @_;
> 
>      logm("$mo->{Target}{Name} (nested host) serial console logs".
>  	 " will be found in guest logs from $mo->{Parent}{Name} (parent)");

[-- Attachment #2: osstest-host2---var-log-xen-osstest-serial-l1.guest.osstest.log --]
[-- Type: application/octet-stream, Size: 98158 bytes --]

[-- Attachment #3: Type: text/plain, Size: 126 bytes --]

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

  reply	other threads:[~2015-11-13  1:54 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <9E79D1C9A97CFD4097BCE431828FDD3102346249@SHSMSX103.ccr.corp.intel.com>
2015-11-10 19:46 ` Osstest nested patch v15 (was RE: [OSSTEST PATCH v14 PART 2 10-26/26] Nested HVM testing) Ian Jackson
2015-11-11  5:23   ` Hu, Robert
2015-11-11  9:35     ` Ian Jackson
2015-11-11 10:15       ` Hu, Robert
2015-11-11 11:08         ` Ian Jackson
2015-11-11 14:05           ` Ian Jackson
2015-11-11 17:00             ` Ian Jackson
2015-11-12  5:43             ` Hu, Robert
2015-11-12 16:10               ` Ian Jackson
2015-11-13  1:53                 ` Hu, Robert [this message]
2015-11-13 10:29                   ` Ian Jackson
2015-11-16  1:49                     ` Hu, Robert
2015-11-16 10:30                       ` Ian Campbell
2015-11-16 10:39                         ` Hu, Robert
2015-11-16 15:20                           ` Ian Jackson
2015-11-16 15:20                         ` Ian Jackson
2015-11-16 15:20                           ` [OSSTEST PATCH 1/2] Nested hosts: Provide hostnamepath and hostnamepath_list Ian Jackson
2015-11-16 15:20                             ` [OSSTEST PATCH 2/2] Nested hosts: Use hostnamepath() in create_webfile Ian Jackson
2015-11-16 15:37                               ` Ian Campbell
2015-11-16 15:37                             ` [OSSTEST PATCH 1/2] Nested hosts: Provide hostnamepath and hostnamepath_list Ian Campbell
2015-11-17  2:14                             ` Hu, Robert
2015-11-17  9:51                               ` Ian Campbell
2015-11-17 10:32                                 ` Hu, Robert

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=9E79D1C9A97CFD4097BCE431828FDD31023862DB@SHSMSX103.ccr.corp.intel.com \
    --to=robert.hu@intel.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=gordon.jin@intel.com \
    --cc=ian.campbell@citrix.com \
    --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.