filters/need_kconfig.rb: clear kconfig_error_message

as of now, if a kernel doesn't open needed kconfig, will output
------
2019-07-23 08:09:30 +0800 afcaa234edafee2f7cb706432ac6bc90c0818468 /lkp/jobs/scheduled/lkp-skl-d01/kernel_selftests-kselftests-03-debian-x86_64-2019-05-14.cgz-539bca535d-20190723-73252-12przht-0.yaml removed by param constraints: CONFIG_MPLS_ROUTING=m is not satisfied by v5.2-rc4, it is only satisfied by kernel matching v(4\.[1-9]|4\.1[0-9]|4\.20|5\.) regexp
------

error log is not clear, it looks like kernel doesn' support this kconfig.
In fact kernel support this kconfig just not compile it.

after this patch
------
2019-07-24 16:45:46 +0800 f5e1848bf7f5f77d06b526983a2b5911b3e0755f /lkp/jobs/scheduled/vm-snb-8G-aa9aa08d95b6/kernel_selftests-kselftests-00-debian-x86_64-2018-04-03.cgz-5f9e832c1370-20190724-67215-krlscl-0.yaml removed by param constraints: CONFIG_LYD_DEBUG=m has not been compiled by v5.3-rc1, it is supported by kernel matching v(4\.[3-9]|4\.1[0-9]|4\.20|5\.) regexp
------

Signed-off-by: Liu Yiding <yidingx.liu@intel.com>
Signed-off-by: Philip Li <philip.li@intel.com>
1 file changed
tree: 9ae2f928a195fc58c277684e6da6ed8796b7296a
  1. allot/
  2. bin/
  3. cluster/
  4. daemon/
  5. distro/
  6. doc/
  7. etc/
  8. filters/
  9. hosts/
  10. include/
  11. jobs/
  12. lib/
  13. lkp-exec/
  14. mailing-list/
  15. monitors/
  16. pack/
  17. params/
  18. pkg/
  19. plot/
  20. repo/
  21. rootfs/
  22. sbin/
  23. setup/
  24. spec/
  25. stats/
  26. tests/
  27. tools/
  28. .gitignore
  29. .rubocop.yml
  30. _config.yml
  31. COPYING
  32. Gemfile
  33. Makefile
  34. Rakefile
  35. README.md
README.md

Linux Kernel Performance tests

Getting started

	git clone https://github.com/intel/lkp-tests.git

	cd lkp-tests
	make install

	lkp help

Install packages for a job

	# browse and select a job you want to run, for example, jobs/hackbench.yaml
	ls lkp-tests/jobs
	
	# install the common dependencies for lkp
	lkp install

Run one atomic job

	lkp split-job lkp-tests/jobs/hackbench.yaml
	# output is:
	# jobs/hackbench.yaml => ./hackbench-1600%-process-pipe.yaml
	# jobs/hackbench.yaml => ./hackbench-1600%-process-socket.yaml
	# jobs/hackbench.yaml => ./hackbench-1600%-threads-pipe.yaml
	# jobs/hackbench.yaml => ./hackbench-1600%-threads-socket.yaml
	# jobs/hackbench.yaml => ./hackbench-50%-process-pipe.yaml
	# jobs/hackbench.yaml => ./hackbench-50%-process-socket.yaml
	# jobs/hackbench.yaml => ./hackbench-50%-threads-pipe.yaml
	# jobs/hackbench.yaml => ./hackbench-50%-threads-socket.yaml

	# install the remaining dependencies for the splited job
	lkp install ./hackbench-50%-threads-socket.yaml

	lkp run ./hackbench-50%-threads-socket.yaml

Run your own disk partitions

Specify disk partitions by defining hdd_partitions/sdd_partitions in host file named with local hostname and then lkp split-job will write the disk partitions information to split job file automatically.

Please note that disk partitions may be formatted/corrupted to run job.

	echo "hdd_partitions: /dev/sda /dev/sdb" >> lkp-tests/hosts/$(hostname | sed -r 's/-[0-9]+$//g' | sed -r 's/-[0-9]+-/-/g')
	lkp split-job lkp-tests/jobs/blogbench.yaml
	# output is:
	# lkp-tests/jobs/blogbench.yaml => ./blogbench-1HDD-ext4.yaml
	# lkp-tests/jobs/blogbench.yaml => ./blogbench-1HDD-xfs.yaml
	# ...
	lkp install ./blogbench-1HDD-ext4.yaml
	lkp run ./blogbench-1HDD-ext4.yaml

Run your own benchmarks

To run your own benchmarks that are not part of lkp-tests, you can use mytest job.

	lkp split-job lkp-tests/jobs/mytest.yaml
	# output is:
	# jobs/mytest.yaml => ./mytest-defaults.yaml
	lkp run ./mytest-defaults.yaml -- <command> <argument> ...

Check result

	lkp result hackbench

Supported Distributions

Most test cases should install/run well in

  • Debian sid
  • Archlinux
  • CentOS7

There is however some initial support for:

  • OpenSUSE:
    • jobs/trinity.yaml
  • Fedora
  • Clear Linux(>=22640)

As for now, lkp-tests still needs to run as root.

Adding distribution support

If you want to add support for your Linux distribution you will need an installer file which allows us to install dependencies per job. For examples look at: distro/installer/* files.

Since packages can have different names we provide an adaptation mapping for a base Ubuntu package (since development started with that) to your own distribution package name, for example adaptation files see: distro/adaptation/*. For now adaptation files must have the architecture dependent packages (ie, that ends with the postfix :i386) towards the end of the adaptation file.

You will also want to add a case for your distribution on sync_distro_sources() on the file lib/install.sh.

Contributing

  1. Fork it
  2. Create your feature branch (git checkout -b my-new-feature)
  3. Commit your changes (git commit -am 'Add some feature')
  4. Push to the branch (git push origin my-new-feature)
  5. Create new Pull Request