All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [PATCH 0/4] lkp: add initial opensuse support
Date: Tue, 10 Jan 2017 10:11:57 +0800	[thread overview]
Message-ID: <20170110021157.GY690@yexl-desktop> (raw)
In-Reply-To: <20170109142608.GZ13946@wotan.suse.de>

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

On 01/09, Luis R. Rodriguez wrote:
>On Mon, Jan 09, 2017 at 03:49:14PM +0800, Ye Xiaolong wrote:
>> Hi, Luis
>> 
>> On 01/06, Luis R. Rodriguez wrote:
>> >I received a failed test results notice from 0-day LKP test suite
>> >using trinity, however it was pretty hard to get reproduce given
>> >the LKP did not have OpenSUSE support to start off with, but the
>> >second issue I've stubmled upon is beyond me -- running either:
>> >
>> >./bin/lkp qemu -k ~mcgrof/linux-next/arch/x86/boot/bzImage job-script
>> >
>> >or
>> >
>> >lkp qemu jobs/trinity.yaml 
>> >
>> >ends up creating calling a few subroutines or files which are
>> >clearly not present, then tries to create a cpio archive but
>> >clearly there are a few files which LKP tree expects you to have
>> >and are not present such as lkp and lkp/scheduled.
>> >
>> >This is a run on OpenSUSE, first we install the dependencies for
>> >trinity.yaml deps:
>> >
>> > # lkp install jobs/trinity.yaml 
>> >
>> >Then we try to run it:
>> >
>> > # lkp qemu jobs/trinity.yaml 
>> 
>> Actually we don't use yaml file for lkp qemu, you could try "lkp run jobs/trinity.yaml"
>> instead.
>
>OK that runs, but that beats my actual machine with trinity, which is not
>desirable. I am trying to reproduce a reported error caught by lpk tests
>with trinity on my tree and that was with qemu. I have the job-script but
>that produces the same error with missing files. Can you help me with that?

Sure, could you paste the exact error log when you tried
"./bin/lkp qemu -k ~mcgrof/linux-next/arch/x86/boot/bzImage job-script"?

Thanks,
Xiaolong
>
>  Luis

  reply	other threads:[~2017-01-10  2:11 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-06 19:06 [PATCH 0/4] lkp: add initial opensuse support Luis R. Rodriguez
2017-01-06 19:06 ` [PATCH 1/4] lib/install.sh: fix shell adapt_packages() Luis R. Rodriguez
2017-01-09  7:39   ` Ye Xiaolong
2017-01-06 19:06 ` [PATCH 2/4] distro: add initial opensuse support Luis R. Rodriguez
2017-01-09  7:40   ` Ye Xiaolong
2017-01-06 19:06 ` [PATCH 3/4] lib/install.*: make package dependency list uniq Luis R. Rodriguez
2017-01-09  7:40   ` Ye Xiaolong
2017-01-06 19:06 ` [PATCH 4/4] .gitignore: add bin/event/wakeup Luis R. Rodriguez
2017-01-09  7:40   ` Ye Xiaolong
2017-01-06 19:58 ` [PATCH 0/4] lkp: add initial opensuse support Luis R. Rodriguez
2017-01-09  7:49 ` Ye Xiaolong
2017-01-09 14:26   ` Luis R. Rodriguez
2017-01-10  2:11     ` Ye Xiaolong [this message]
2017-01-10 14:25       ` Luis R. Rodriguez
2017-01-11  1:52         ` Ye Xiaolong
2017-01-11 14:34           ` Luis R. Rodriguez
2017-02-21  1:56             ` WARNING:at_lib/test_linktables/test-linktables.c:#test_linktable_init Ye Xiaolong
2017-01-09  8:48 ` [PATCH 0/4] lkp: add initial opensuse support Philip Li

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=20170110021157.GY690@yexl-desktop \
    --to=xiaolong.ye@intel.com \
    --cc=lkp@lists.01.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.