From: Philip Li <philip.li@intel.com>
To: lkp@lists.01.org
Subject: Re: [PATCH 0/4] lkp: add initial opensuse support
Date: Mon, 09 Jan 2017 16:48:38 +0800 [thread overview]
Message-ID: <20170109084838.GA5826@intel.com> (raw)
In-Reply-To: <20170106190652.31544-1-mcgrof@kernel.org>
[-- Attachment #1: Type: text/plain, Size: 2684 bytes --]
On Fri, Jan 06, 2017 at 11:06:48AM -0800, 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
> jobs/trinity.yaml: line 1: suite:: command not found
> jobs/trinity.yaml: line 2: testcase:: command not found
> jobs/trinity.yaml: line 4: runtime:: command not found
> jobs/trinity.yaml: line 6: kmsg:: command not found
> jobs/trinity.yaml: line 7: rootfs:: command not found
> jobs/trinity.yaml: line 9: trinity:: command not found
> make: Entering directory '/home/mcgrof/devel/lkp-tests/bin/event'
> klcc -c -o wakeup.o wakeup.c
> klcc -static -o wakeup wakeup.o
> rm -f wakeup.o
> strip wakeup
> make: Leaving directory '/home/mcgrof/devel/lkp-tests/bin/event'
> cpio: lkp: Cannot stat: No such file or directory
> cpio: lkp/scheduled: Cannot stat: No such file or directory
> cpio: blank line ignored
> cpio: File /dev/mqueue/���� shrunk by 20 bytes, padding with zeros
>
> This never complets, it just sits there.
>
> Either way these patches help start to add OpenSUSE support.
>
> Luis R. Rodriguez (4):
> lib/install.sh: fix shell adapt_packages()
> distro: add initial opensuse support
> lib/install.*: make package dependency list uniq
> .gitignore: add bin/event/wakeup
thanks a lot, all 4 patches applied
>
> .gitignore | 1 +
> README.md | 22 ++++++++++++++++++++++
> distro/adaptation/archlinux | 2 +-
> distro/adaptation/fedora | 2 +-
> distro/adaptation/opensuse | 14 ++++++++++++++
> distro/depends/lkp-dev | 4 ++++
> distro/installer/opensuse | 3 +++
> lib/install.rb | 2 +-
> lib/install.sh | 14 +++++++++++---
> 9 files changed, 58 insertions(+), 6 deletions(-)
> create mode 100644 distro/adaptation/opensuse
> create mode 100755 distro/installer/opensuse
>
> --
> 2.11.0
>
prev parent reply other threads:[~2017-01-09 8:48 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
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 ` Philip Li [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=20170109084838.GA5826@intel.com \
--to=philip.li@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.