From: Ye Xiaolong <xiaolong.ye@intel.com>
To: lkp@lists.01.org
Subject: Re: [x86/copy_user] adb402cd14: will-it-scale.per_process_ops -12.7% regression
Date: Mon, 14 Nov 2016 22:37:11 +0800 [thread overview]
Message-ID: <20161114143711.GB2852@yexl-desktop> (raw)
In-Reply-To: <20161107095631.truqvpqong3ixwp3@pd.tnic>
[-- Attachment #1: Type: text/plain, Size: 2580 bytes --]
On 11/07, Borislav Petkov wrote:
>On Mon, Nov 07, 2016 at 10:50:38AM +0800, kernel test robot wrote:
>> To reproduce:
>>
>> git clone git://git.kernel.org/pub/scm/linux/kernel/git/wfg/lkp-tests.git
>> cd lkp-tests
>> bin/lkp install job.yaml # job file is attached in this email
>
>./bin/lkp install job.yaml
>Use: /root/lkp/lkp-tests/distro/installer/debian install bc gawk time kmod gzip make automake gcc build-essential libtool patch git openssl ca-certificates rsync cpio wget libklibc-dev linux-libc-dev linux-libc-dev:i386 libc6-dev libc6-dev:i386
>Reading package lists... Done
>Building dependency tree
>Reading state information... Done
>E: Unable to locate package linux-libc-dev
>E: Unable to locate package libc6-dev
>Cannot install some packages in /root/lkp/lkp-tests/distro/depends/lkp
>
>This wants i386 flavors and can't find them for some reason...
>
Below cmd should help on it:
dpkg --add-architecture i386 && apt-get update
>> bin/lkp run job.yaml
>
>With your scripts I get:
>
>$ ./bin/lkp run job.yaml
>/usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require': cannot load such file -- git (LoadError)
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /root/lkp/lkp-tests/lib/git_ext.rb:7:in `<top (required)>'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /root/lkp/lkp-tests/lib/lkp_git.rb:14:in `<top (required)>'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /root/lkp/lkp-tests/lib/stats.rb:9:in `<top (required)>'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /usr/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
> from /root/lkp/lkp-tests/bin/run-local:15:in `<main>'
>
>and that line is:
>
>require 'git'
>
It requires to install ruby-git package, try
sudo apt-get install ruby-git
Thanks,
Xiaolong
>but I already have ruby git bindings installed.
>
>So how can I run the benchmark directly, without the ruby glue? I
>already have a debian partition on this SNB box so I can run it
>natively.
>
>Thanks.
>
>--
>Regards/Gruss,
> Boris.
>
>Good mailing practices for 400: avoid top-posting and trim the reply.
next prev parent reply other threads:[~2016-11-14 14:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-07 2:50 [x86/copy_user] adb402cd14: will-it-scale.per_process_ops -12.7% regression kernel test robot
2016-11-07 2:50 ` [lkp] " kernel test robot
2016-11-07 9:56 ` Borislav Petkov
2016-11-07 9:56 ` [lkp] " Borislav Petkov
2016-11-14 14:37 ` Ye Xiaolong [this message]
2016-11-15 10:01 ` Borislav Petkov
2016-11-14 14:19 ` Ye Xiaolong
2016-11-15 15:10 ` Borislav Petkov
2016-11-16 9:58 ` Borislav Petkov
2016-11-16 12:38 ` Ye Xiaolong
2016-11-09 12:42 ` Borislav Petkov
2016-11-09 12:42 ` [lkp] " Borislav Petkov
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=20161114143711.GB2852@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.