From: Cyril Hrubis <chrubis@suse.cz>
To: ltp@lists.linux.it
Subject: [LTP] [lkp-robot] [x86/topology] 379a4bb988: dmesg.WARNING:at_arch/x86/events/intel/uncore.c:#uncore_change_type_ctx
Date: Thu, 26 Oct 2017 12:09:11 +0200 [thread overview]
Message-ID: <20171026100911.GD3873@rei> (raw)
In-Reply-To: <48cfd754-886d-38b0-b9e5-55088e5a9665@redhat.com>
Hi!
> > bin/lkp install job.yaml
>
> [root@hpe-dl385gen10-02 lkp-tests]# ls
> allot daemon filters include Makefile pkg repo spec
> bin distro Gemfile jobs monitors plot rootfs stats
> cluster doc Gemfile.lock lib pack Rakefile sbin tests
> _config.yml etc hosts lkp-exec params README.md setup tools
> [root@hpe-dl385gen10-02 lkp-tests]# bin/lkp install ../job.yaml
> Not a supported system, cannot install packages.
> [root@hpe-dl385gen10-02 lkp-tests]#
>
> Well that's useful.
Sorry for the late reply, you may have figured it out already, you can
install and run LTP without the lkp framework and that should be pretty
straightforward, then you can just run it by:
'cd /opt/ltp && ./runltp -f cpuhotplug'
Looking at the test it may need a kernel source unpacked /usr/src/linux
as well.
Short HOWTO for building LTP from git is here:
https://github.com/linux-test-project/ltp/blob/master/doc/mini-howto-building-ltp-from-git.txt
And we do have (unofficional) packages for some SUSE distributions:
https://build.opensuse.org/package/show/benchmark/ltp
--
Cyril Hrubis
chrubis@suse.cz
prev parent reply other threads:[~2017-10-26 10:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1506430406-26121-3-git-send-email-prarit@redhat.com>
[not found] ` <20171012064439.GN26196@yexl-desktop>
2017-10-16 7:50 ` [LTP] [lkp-robot] [x86/topology] 379a4bb988: dmesg.WARNING:at_arch/x86/events/intel/uncore.c:#uncore_change_type_ctx Ingo Molnar
2017-10-18 13:19 ` Prarit Bhargava
2017-10-26 10:09 ` Cyril Hrubis [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=20171026100911.GD3873@rei \
--to=chrubis@suse.cz \
--cc=ltp@lists.linux.it \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox