* [igt-dev] [PATCH i-g-t] Make README more friendly
@ 2019-10-03 13:06 Arkadiusz Hiler
2019-10-03 13:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
` (6 more replies)
0 siblings, 7 replies; 9+ messages in thread
From: Arkadiusz Hiler @ 2019-10-03 13:06 UTC (permalink / raw)
To: igt-dev; +Cc: Petri Latvala
* reorder sections so we have a more newbie friendly reading flow:
requirements -> building -> running
* add links to documentation
* drop mentions of autotools
* drop piglit references
* don't list dependencies, just point to Dockerfiles
* mention IGT containers
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
README.md | 280 ++++++++++++++++++++++--------------------------------
1 file changed, 112 insertions(+), 168 deletions(-)
diff --git a/README.md b/README.md
index b8c4c5a8..b295dc3e 100644
--- a/README.md
+++ b/README.md
@@ -1,6 +1,7 @@
IGT GPU Tools
=============
+
Description
-----------
@@ -12,173 +13,31 @@ complicated build procedures or specific testing environments to get useful
results. Therefore, IGT GPU Tools includes low-level tools and tests
specifically for development and testing of the DRM Drivers.
-IGT GPU Tools is split into several sections:
-
-**benchmarks/**
-
-This is a collection of useful microbenchmarks that can be used to tune
-DRM code in relevant ways.
-
-The benchmarks require KMS to be enabled. When run with an X Server
-running, they must be run as root to avoid the authentication
-requirement.
-
-Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
-
-**tests/**
-
-This is a set of automated tests to run against the DRM to validate
-changes. Many of the tests have subtests, which can be listed by using
-the --list-subtests command line option and then run using the
---run-subtest option. If --run-subtest is not used, all subtests will
-be run. Some tests have futher options and these are detailed by using
-the --help option.
-
-The test suite can be run using the run-tests.sh script available in
-the scripts directory. Piglit is used to run the tests and can either
-be installed from your distribution (if available), or can be
-downloaded locally for use with the script by running:
-
- ./scripts/run-tests.sh -d
-
-run-tests.sh has options for filtering and excluding tests from test
-runs:
-
- -t <regex> only include tests that match the regular expression
- -x <regex> exclude tests that match the regular expression
-
-Useful patterns for test filtering are described in the API
-documentation and the full list of tests and subtests can be produced
-by passing -l to the run-tests.sh script.
-
-Results are written to a JSON file and an HTML summary can also be
-created by passing -s to the run-tests.sh script. Further options are
-are detailed by using the -h option.
-
-
-If not using the script, piglit can be obtained from:
-
- git://anongit.freedesktop.org/piglit
-
-There is no need to build and install piglit if it is only going to be
-used for running i-g-t tests.
-
-Set the IGT_TEST_ROOT environment variable to point to the tests
-directory, or set the path key in the "igt" section of piglit.conf to
-the igt-gpu-tools root directory.
-
-The tests in the i-g-t sources need to have been built already. Then we
-can run the testcases with (as usual as root, no other drm clients
-running):
-
- piglit-sources # ./piglit run igt <results-file>
-
-The testlist is built at runtime, so no need to update anything in
-piglit when adding new tests. See
-
- piglit-sources $ ./piglit run -h
-
-for some useful options.
-
-Piglit only runs a default set of tests and is useful for regression
-testing. Other tests not run are:
-- tests that might hang the gpu, see HANG in Makefile.am
-- gem_stress, a stress test suite. Look at the source for all the
- various options.
-- testdisplay is only run in the default mode. testdisplay has tons of
- options to test different kms functionality, again read the source for
- the details.
-
-**lib/**
-
-Common helper functions and headers used by the other tools.
-
-**man/**
-
-Manpages, unfortunately rather incomplete.
-
-**tools/**
-
-This is a collection of debugging tools that had previously been
-built with the 2D driver but not shipped. Some distros were hacking
-up the 2D build to ship them. Instead, here's a separate package for
-people debugging the driver.
-
-These tools generally must be run as root, except for the ones that just
-decode dumps.
-
-**docs/**
-
-Contains the automatically generated igt-gpu-tools libraries
-reference documentation in docs/reference/. You need to have the
-gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
-to generate this API documentation.
-
-To regenerate the html files when updating documentation, use:
-
- $ ninja -C build igt-gpu-tools-doc
-
-If you've added/changed/removed a symbol or anything else that changes
-the overall structure or indexes, this needs to be reflected in
-igt-gpu-tools-sections.txt. Entirely new sections will also need to be
-added to igt-gpu-tools-docs.xml in the appropriate place.
-
-**include/drm-uapi**
-
-Imported DRM uapi headers from airlied's drm-next branch.
-These should be updated all together by executing "make
-headers_install" from that branch of the kernel and then
-copying the resulting ./usr/include/drm/*.h in and committing
-with a note of which commit on airlied's branch was used to
-generate them.
+Generated documentation for the latest master is published under
+<https://drm.pages.freedesktop.org/igt-gpu-tools/>.
Requirements
------------
-This is a non-exhaustive list of package dependencies required for building
-the default configuration (package names may vary):
+See `Dockerfiles.*` for up-to-date list of packages names in Fedora and
+Debian.
- bison
- gtk-doc-tools
- flex
- libcairo2-dev
- libdrm-dev
- libkmod-dev
- libpixman-1-dev
- libpciaccess-dev
- libprocps-dev
- libudev-dev
- libunwind-dev
- liblzma-dev
- libdw-dev
- python-docutils
- x11proto-dri2-dev
- xutils-dev
+If your distribution packages IGT you can also use your package manager to
+install the dependencies, e.g.:
-The following dependencies are required for building chamelium support
-(package names may vary):
+ # dnf builddep igt-gpu-tools
- libxmlrpc-core-c3-dev
- libudev-dev
- libglib2.0-dev
- libgsl-dev
+But keep in mind that this may be slightly outdated and miss some
+recently added dependencies for building the current master.
-The following dependencies are requires for building audio support
-(package names may vary):
- libasound2-dev
- libgsl-dev
+Building
+--------
-See Dockerfiles.* for package names in different distributions.
+Oneliner to get started:
-Meson build system support
---------------------------
-
-Currently we support both meson and automake as build systems, but meson is the
-recommended choice. Oneliner to get started:
-
- $ mkdir build && meson build && cd build && ninja
+ $ meson build && ninja -C build
Note that meson insist on separate build directories from the source tree.
@@ -186,26 +45,111 @@ Running selfchecks for lib/tests and tests/ is done with
$ ninja -C build test
-Note that this doesn't actually run the testcases in tests/: scripts/run-tests.sh
-should continue to be used for that.
-
Documentation is built using
$ ninja -C build igt-gpu-tools-doc
-Note that this needs meson v0.47 or later, earlier versions of meson do not
-track depencies correctly for the documentation build and need:
- $ ninja -C build && ninja -C build igt-gpu-tools-doc
+Running Tests
+-------------
-Note that there's a setup script similar to ./autogen.sh which creates a
-compatibility Makefile with a few useful default targets:
+In `tests/` you can find a set of automated tests to run against the DRM
+drivers to validate your changes. Many of the tests have subtests, which can
+be listed by using the `--list-subtests` command line option and then run
+using the --run-subtest option. If `--run-subtest` is not used, all subtests
+will be run. Some tests have further options and these are detailed by using
+the `--help` option.
- $ ./meson.sh [make-arguments]
+Most of the test must be run as a root and with no X or Wayland compositor
+running.
-Releases for maintainers
-------------------------
+ # build/tests/core_auth
+ IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
+ Starting subtest: getclient-simple
+ Subtest getclient-simple: SUCCESS (0.001s)
+ Starting subtest: getclient-master-drop
+ Subtest getclient-master-drop: SUCCESS (0.000s)
+ Starting subtest: basic-auth
+ Subtest basic-auth: SUCCESS (0.000s)
+ Starting subtest: many-magics
+ Subtest many-magics: SUCCESS (0.000s)
-(1.14)
+ # build/tests/core_auth --run-subtest getclient-simple
+ IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
+ Starting subtest: getclient-simple
+ Subtest getclient-simple: SUCCESS (0.000s)
-http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
+
+The test suite can be run using the `run-tests.sh` script available in the
+`scripts/` directory. To use it make sure that `igt_runner` is built, e.g.:
+
+ meson -Drunner=enabled build && ninja -C build
+
+`run-tests.sh` has options for filtering and excluding tests from test
+runs:
+
+ -t <regex> only include tests that match the regular expression
+ -x <regex> exclude tests that match the regular expression
+
+Useful patterns for test filtering are described in the [API
+documentation][API] and the full list of tests and subtests can be produced
+by passing `-l` to the `run-tests.sh` script. Further options are are
+detailed by using the `-h` option.
+
+Results are written to a JSON file.
+
+[API]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html
+
+
+IGT Containers
+--------------
+
+IGT is packed into nifty docker-compatible containers for ease of execution
+and to avoid having to install all the dependencies. You can use
+podman/docker to to run it on your system.
+
+Oneliner to get you started with the latest master:
+
+ # podman run --rm --priviledged registry.freedesktop.org/drm/igt-gpu-tools/igt:master
+
+
+Other Things
+------------
+
+### `benchmarks/`
+
+A collection of useful microbenchmarks that can be used to tune DRM code.
+
+The benchmarks require KMS to be enabled. When run with an X Server
+running, they must be run as root to avoid the authentication
+requirement.
+
+Note that a few other microbenchmarks are in tests (e.g. `gem_gtt_speed`).
+
+### `tools/`
+
+A collection of debugging tools. They generally must be run as root, except
+for the ones that just decode dumps.
+
+### `docs/`
+
+Contains the infrastracture to automatically generate igt-gpu-tools libraries
+reference documentation. You need to have the gtk-doc tools installed.
+
+To regenerate the html files when updating documentation, use:
+
+ $ ninja -C build igt-gpu-tools-doc
+
+If you've added/changed/removed a symbol or anything else that changes the
+overall structure or indexes you need to reflect the change in
+`igt-gpu-tools-sections.txt`. Entirely new sections also need to be added to
+`igt-gpu-tools-docs.xml` in the appropriate place.
+
+### `include/drm-uapi/`
+
+Imported DRM uapi headers from airlied's drm-next branch.
+
+These should be updated all together by executing `make headers_install` from
+that branch of the kernel and then copying the resulting
+`./usr/include/drm/*.h` in and committing with a note of which exact commit
+from the airlied's branch was used to generate them.
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for Make README more friendly
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
@ 2019-10-03 13:53 ` Patchwork
2019-10-03 20:05 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
` (5 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2019-10-03 13:53 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
== Series Details ==
Series: Make README more friendly
URL : https://patchwork.freedesktop.org/series/67536/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_6996 -> IGTPW_3532
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
Known issues
------------
Here are the changes found in IGTPW_3532 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_switch@rcs0:
- fi-icl-u2: [PASS][1] -> [INCOMPLETE][2] ([fdo#107713])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-icl-u2/igt@gem_ctx_switch@rcs0.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-icl-u2/igt@gem_ctx_switch@rcs0.html
* igt@gem_exec_suspend@basic-s4-devices:
- fi-blb-e6850: [PASS][3] -> [INCOMPLETE][4] ([fdo#107718])
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-blb-e6850/igt@gem_exec_suspend@basic-s4-devices.html
* igt@gem_mmap_gtt@basic-small-bo:
- fi-icl-u3: [PASS][5] -> [DMESG-WARN][6] ([fdo#107724])
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-icl-u3/igt@gem_mmap_gtt@basic-small-bo.html
* igt@i915_module_load@reload:
- fi-icl-u3: [PASS][7] -> [DMESG-WARN][8] ([fdo#107724] / [fdo#111214])
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-icl-u3/igt@i915_module_load@reload.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-icl-u3/igt@i915_module_load@reload.html
#### Possible fixes ####
* igt@gem_flink_basic@double-flink:
- fi-icl-u3: [DMESG-WARN][9] ([fdo#107724]) -> [PASS][10] +1 similar issue
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-icl-u3/igt@gem_flink_basic@double-flink.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-icl-u3/igt@gem_flink_basic@double-flink.html
* igt@i915_selftest@live_gem_contexts:
- {fi-tgl-u}: [INCOMPLETE][11] -> [PASS][12]
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-tgl-u/igt@i915_selftest@live_gem_contexts.html
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-tgl-u/igt@i915_selftest@live_gem_contexts.html
* igt@i915_selftest@live_hangcheck:
- fi-cfl-8109u: [INCOMPLETE][13] ([fdo#106070]) -> [PASS][14]
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-cfl-8109u/igt@i915_selftest@live_hangcheck.html
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-cfl-8109u/igt@i915_selftest@live_hangcheck.html
#### Warnings ####
* igt@kms_chamelium@hdmi-hpd-fast:
- fi-kbl-7500u: [FAIL][15] ([fdo#111407]) -> [FAIL][16] ([fdo#111045] / [fdo#111096])
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/fi-kbl-7500u/igt@kms_chamelium@hdmi-hpd-fast.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#106070]: https://bugs.freedesktop.org/show_bug.cgi?id=106070
[fdo#106107]: https://bugs.freedesktop.org/show_bug.cgi?id=106107
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111214]: https://bugs.freedesktop.org/show_bug.cgi?id=111214
[fdo#111407]: https://bugs.freedesktop.org/show_bug.cgi?id=111407
Participating hosts (52 -> 45)
------------------------------
Missing (7): fi-ilk-m540 fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5210 -> IGTPW_3532
CI-20190529: 20190529
CI_DRM_6996: 98596d29a3cff9d996c42468eb606036faf42954 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3532: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
IGT_5210: 74f55119f9920b65996535210a09147997804136 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for Make README more friendly
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
2019-10-03 13:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
@ 2019-10-03 20:05 ` Patchwork
2019-10-04 9:23 ` [igt-dev] [PATCH i-g-t] " Rhys Kidd
` (4 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2019-10-03 20:05 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
== Series Details ==
Series: Make README more friendly
URL : https://patchwork.freedesktop.org/series/67536/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_6996_full -> IGTPW_3532_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_3532_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_3532_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3532_full:
### IGT changes ###
#### Possible regressions ####
* igt@gem_mmap_gtt@hang:
- shard-iclb: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb7/igt@gem_mmap_gtt@hang.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@gem_mmap_gtt@hang.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* igt@gem_mmap_gtt@hang:
- {shard-tglb}: [PASS][3] -> [DMESG-WARN][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-tglb5/igt@gem_mmap_gtt@hang.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb2/igt@gem_mmap_gtt@hang.html
* igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend:
- {shard-tglb}: NOTRUN -> [INCOMPLETE][5]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb2/igt@kms_vblank@pipe-b-ts-continuation-dpms-suspend.html
* {igt@perf_pmu@semaphore-busy-rcs0}:
- {shard-tglb}: [PASS][6] -> [INCOMPLETE][7] +1 similar issue
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-tglb2/igt@perf_pmu@semaphore-busy-rcs0.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb6/igt@perf_pmu@semaphore-busy-rcs0.html
Known issues
------------
Here are the changes found in IGTPW_3532_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_isolation@rcs0-s3:
- shard-iclb: [PASS][8] -> [DMESG-WARN][9] ([fdo#111764])
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb3/igt@gem_ctx_isolation@rcs0-s3.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb6/igt@gem_ctx_isolation@rcs0-s3.html
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [PASS][10] -> [SKIP][11] ([fdo#110841])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb5/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb4/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_exec_schedule@independent-bsd2:
- shard-iclb: [PASS][12] -> [SKIP][13] ([fdo#109276]) +15 similar issues
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb2/igt@gem_exec_schedule@independent-bsd2.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb6/igt@gem_exec_schedule@independent-bsd2.html
* igt@gem_exec_schedule@preempt-other-chain-bsd:
- shard-iclb: [PASS][14] -> [SKIP][15] ([fdo#111325]) +6 similar issues
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb3/igt@gem_exec_schedule@preempt-other-chain-bsd.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb4/igt@gem_exec_schedule@preempt-other-chain-bsd.html
* igt@gem_userptr_blits@dmabuf-sync:
- shard-hsw: [PASS][16] -> [DMESG-WARN][17] ([fdo#110789] / [fdo#111870])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw4/igt@gem_userptr_blits@dmabuf-sync.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw1/igt@gem_userptr_blits@dmabuf-sync.html
* igt@gem_userptr_blits@sync-unmap-after-close:
- shard-hsw: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870]) +2 similar issues
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw6/igt@gem_userptr_blits@sync-unmap-after-close.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw8/igt@gem_userptr_blits@sync-unmap-after-close.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-snb: [PASS][20] -> [DMESG-WARN][21] ([fdo#111870]) +4 similar issues
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-snb2/igt@gem_userptr_blits@sync-unmap-cycles.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-snb2/igt@gem_userptr_blits@sync-unmap-cycles.html
- shard-apl: [PASS][22] -> [DMESG-WARN][23] ([fdo#109385] / [fdo#111870]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl3/igt@gem_userptr_blits@sync-unmap-cycles.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl2/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [PASS][24] -> [DMESG-WARN][25] ([fdo#108566]) +3 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl3/igt@i915_suspend@fence-restore-tiled2untiled.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl8/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_color@pipe-b-ctm-blue-to-red:
- shard-apl: [PASS][26] -> [FAIL][27] ([fdo#107201])
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl8/igt@kms_color@pipe-b-ctm-blue-to-red.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl4/igt@kms_color@pipe-b-ctm-blue-to-red.html
- shard-kbl: [PASS][28] -> [FAIL][29] ([fdo#107201])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-kbl3/igt@kms_color@pipe-b-ctm-blue-to-red.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-kbl4/igt@kms_color@pipe-b-ctm-blue-to-red.html
* igt@kms_flip@flip-vs-panning-vs-hang:
- shard-iclb: [PASS][30] -> [INCOMPLETE][31] ([fdo#107713])
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb3/igt@kms_flip@flip-vs-panning-vs-hang.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@kms_flip@flip-vs-panning-vs-hang.html
* igt@kms_flip@flip-vs-suspend-interruptible:
- shard-hsw: [PASS][32] -> [INCOMPLETE][33] ([fdo#103540])
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw4/igt@kms_flip@flip-vs-suspend-interruptible.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw8/igt@kms_flip@flip-vs-suspend-interruptible.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt:
- shard-iclb: [PASS][34] -> [FAIL][35] ([fdo#103167]) +5 similar issues
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb1/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb6/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-shrfb-msflip-blt.html
* igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-draw-render:
- shard-glk: [PASS][36] -> [FAIL][37] ([fdo#103167])
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-glk7/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-draw-render.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-glk1/igt@kms_frontbuffer_tracking@fbc-2p-scndscrn-cur-indfb-draw-render.html
* igt@kms_frontbuffer_tracking@fbcpsr-suspend:
- shard-iclb: [PASS][38] -> [INCOMPLETE][39] ([fdo#106978] / [fdo#107713])
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb4/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@kms_frontbuffer_tracking@fbcpsr-suspend.html
* igt@kms_lease@lease_unleased_connector:
- shard-apl: [PASS][40] -> [INCOMPLETE][41] ([fdo#103927])
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl3/igt@kms_lease@lease_unleased_connector.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl6/igt@kms_lease@lease_unleased_connector.html
* igt@kms_plane_scaling@pipe-c-scaler-with-rotation:
- shard-iclb: [PASS][42] -> [INCOMPLETE][43] ([fdo#107713] / [fdo#110041])
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb1/igt@kms_plane_scaling@pipe-c-scaler-with-rotation.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@kms_plane_scaling@pipe-c-scaler-with-rotation.html
* igt@kms_psr@psr2_suspend:
- shard-iclb: [PASS][44] -> [SKIP][45] ([fdo#109441]) +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb2/igt@kms_psr@psr2_suspend.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb4/igt@kms_psr@psr2_suspend.html
#### Possible fixes ####
* igt@gem_exec_balancer@smoke:
- shard-iclb: [SKIP][46] ([fdo#110854]) -> [PASS][47]
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb8/igt@gem_exec_balancer@smoke.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb4/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@preempt-bsd:
- shard-iclb: [SKIP][48] ([fdo#111325]) -> [PASS][49] +4 similar issues
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb4/igt@gem_exec_schedule@preempt-bsd.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb3/igt@gem_exec_schedule@preempt-bsd.html
* igt@gem_exec_schedule@preempt-queue-bsd1:
- shard-iclb: [SKIP][50] ([fdo#109276]) -> [PASS][51] +11 similar issues
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb8/igt@gem_exec_schedule@preempt-queue-bsd1.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb1/igt@gem_exec_schedule@preempt-queue-bsd1.html
* igt@gem_exec_suspend@basic-s3:
- shard-iclb: [FAIL][52] -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb2/igt@gem_exec_suspend@basic-s3.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb3/igt@gem_exec_suspend@basic-s3.html
* igt@gem_mmap_gtt@basic-small-copy:
- shard-hsw: [DMESG-WARN][54] -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw6/igt@gem_mmap_gtt@basic-small-copy.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw5/igt@gem_mmap_gtt@basic-small-copy.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-kbl: [DMESG-WARN][56] ([fdo#111870]) -> [PASS][57] +2 similar issues
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-kbl4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-kbl4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
- shard-hsw: [DMESG-WARN][58] ([fdo#111870]) -> [PASS][59] +1 similar issue
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw6/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw8/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
- shard-glk: [DMESG-WARN][60] ([fdo#111870]) -> [PASS][61] +1 similar issue
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-glk2/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-glk8/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-iclb: [DMESG-WARN][62] ([fdo#111870]) -> [PASS][63] +1 similar issue
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb5/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb6/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy:
- shard-apl: [DMESG-WARN][64] ([fdo#109385] / [fdo#111870]) -> [PASS][65] +1 similar issue
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl6/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy.html
* igt@gem_userptr_blits@sync-unmap:
- shard-snb: [DMESG-WARN][66] ([fdo#111870]) -> [PASS][67]
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-snb5/igt@gem_userptr_blits@sync-unmap.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-snb7/igt@gem_userptr_blits@sync-unmap.html
* igt@i915_pm_backlight@fade_with_suspend:
- {shard-tglb}: [INCOMPLETE][68] ([fdo#111832]) -> [PASS][69]
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-tglb4/igt@i915_pm_backlight@fade_with_suspend.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb6/igt@i915_pm_backlight@fade_with_suspend.html
* igt@i915_suspend@debugfs-reader:
- {shard-tglb}: [INCOMPLETE][70] ([fdo#111867]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-tglb3/igt@i915_suspend@debugfs-reader.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb6/igt@i915_suspend@debugfs-reader.html
* igt@kms_atomic_transition@plane-all-modeset-transition-fencing:
- shard-apl: [INCOMPLETE][72] ([fdo#103927]) -> [PASS][73] +2 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl3/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl8/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
* igt@kms_flip@2x-flip-vs-suspend:
- shard-hsw: [INCOMPLETE][74] ([fdo#103540]) -> [PASS][75] +1 similar issue
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-hsw6/igt@kms_flip@2x-flip-vs-suspend.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-hsw8/igt@kms_flip@2x-flip-vs-suspend.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-blt:
- shard-iclb: [FAIL][76] ([fdo#103167]) -> [PASS][77] +3 similar issues
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb4/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-blt.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-pri-indfb-draw-blt.html
* igt@kms_frontbuffer_tracking@fbc-shrfb-scaledprimary:
- {shard-tglb}: [FAIL][78] ([fdo#103167]) -> [PASS][79] +5 similar issues
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-tglb7/igt@kms_frontbuffer_tracking@fbc-shrfb-scaledprimary.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-tglb1/igt@kms_frontbuffer_tracking@fbc-shrfb-scaledprimary.html
* igt@kms_vblank@pipe-a-ts-continuation-suspend:
- shard-apl: [DMESG-WARN][80] ([fdo#108566]) -> [PASS][81] +4 similar issues
[80]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-apl2/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
[81]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-apl3/igt@kms_vblank@pipe-a-ts-continuation-suspend.html
#### Warnings ####
* igt@gem_ctx_isolation@vcs1-nonpriv:
- shard-iclb: [SKIP][82] ([fdo#109276]) -> [FAIL][83] ([fdo#111329])
[82]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb5/igt@gem_ctx_isolation@vcs1-nonpriv.html
[83]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb1/igt@gem_ctx_isolation@vcs1-nonpriv.html
* igt@gem_mocs_settings@mocs-isolation-bsd2:
- shard-iclb: [FAIL][84] ([fdo#111330]) -> [SKIP][85] ([fdo#109276]) +1 similar issue
[84]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb1/igt@gem_mocs_settings@mocs-isolation-bsd2.html
[85]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb7/igt@gem_mocs_settings@mocs-isolation-bsd2.html
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [SKIP][86] ([fdo#109276]) -> [FAIL][87] ([fdo#111330])
[86]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6996/shard-iclb3/igt@gem_mocs_settings@mocs-reset-bsd2.html
[87]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/shard-iclb4/igt@gem_mocs_settings@mocs-reset-bsd2.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#102250]: https://bugs.freedesktop.org/show_bug.cgi?id=102250
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103540]: https://bugs.freedesktop.org/show_bug.cgi?id=103540
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#106978]: https://bugs.freedesktop.org/show_bug.cgi?id=106978
[fdo#107201]: https://bugs.freedesktop.org/show_bug.cgi?id=107201
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109385]: https://bugs.freedesktop.org/show_bug.cgi?id=109385
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110041]: https://bugs.freedesktop.org/show_bug.cgi?id=110041
[fdo#110789]: https://bugs.freedesktop.org/show_bug.cgi?id=110789
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111329]: https://bugs.freedesktop.org/show_bug.cgi?id=111329
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111597]: https://bugs.freedesktop.org/show_bug.cgi?id=111597
[fdo#111600]: https://bugs.freedesktop.org/show_bug.cgi?id=111600
[fdo#111646]: https://bugs.freedesktop.org/show_bug.cgi?id=111646
[fdo#111735]: https://bugs.freedesktop.org/show_bug.cgi?id=111735
[fdo#111764]: https://bugs.freedesktop.org/show_bug.cgi?id=111764
[fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
[fdo#111839 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111839
[fdo#111867]: https://bugs.freedesktop.org/show_bug.cgi?id=111867
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
Participating hosts (11 -> 7)
------------------------------
Missing (4): pig-skl-6260u shard-skl pig-hsw-4770r pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5210 -> IGTPW_3532
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_6996: 98596d29a3cff9d996c42468eb606036faf42954 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3532: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
IGT_5210: 74f55119f9920b65996535210a09147997804136 @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3532/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] Make README more friendly
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
2019-10-03 13:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-10-03 20:05 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
@ 2019-10-04 9:23 ` Rhys Kidd
2019-10-04 9:24 ` Petri Latvala
` (3 subsequent siblings)
6 siblings, 0 replies; 9+ messages in thread
From: Rhys Kidd @ 2019-10-04 9:23 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev, Petri Latvala
[-- Attachment #1.1: Type: text/plain, Size: 12843 bytes --]
On Thu, 3 Oct 2019 at 23:07, Arkadiusz Hiler <arkadiusz.hiler@intel.com>
wrote:
> * reorder sections so we have a more newbie friendly reading flow:
> requirements -> building -> running
>
> * add links to documentation
>
> * drop mentions of autotools
>
> * drop piglit references
>
> * don't list dependencies, just point to Dockerfiles
>
> * mention IGT containers
>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> ---
> README.md | 280 ++++++++++++++++++++++--------------------------------
> 1 file changed, 112 insertions(+), 168 deletions(-)
>
> diff --git a/README.md b/README.md
> index b8c4c5a8..b295dc3e 100644
> --- a/README.md
> +++ b/README.md
> @@ -1,6 +1,7 @@
> IGT GPU Tools
> =============
>
> +
> Description
> -----------
>
> @@ -12,173 +13,31 @@ complicated build procedures or specific testing
> environments to get useful
> results. Therefore, IGT GPU Tools includes low-level tools and tests
> specifically for development and testing of the DRM Drivers.
>
> -IGT GPU Tools is split into several sections:
> -
> -**benchmarks/**
> -
> -This is a collection of useful microbenchmarks that can be used to tune
> -DRM code in relevant ways.
> -
> -The benchmarks require KMS to be enabled. When run with an X Server
> -running, they must be run as root to avoid the authentication
> -requirement.
> -
> -Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
> -
> -**tests/**
> -
> -This is a set of automated tests to run against the DRM to validate
> -changes. Many of the tests have subtests, which can be listed by using
> -the --list-subtests command line option and then run using the
> ---run-subtest option. If --run-subtest is not used, all subtests will
> -be run. Some tests have futher options and these are detailed by using
> -the --help option.
> -
> -The test suite can be run using the run-tests.sh script available in
> -the scripts directory. Piglit is used to run the tests and can either
> -be installed from your distribution (if available), or can be
> -downloaded locally for use with the script by running:
> -
> - ./scripts/run-tests.sh -d
> -
> -run-tests.sh has options for filtering and excluding tests from test
> -runs:
> -
> - -t <regex> only include tests that match the regular expression
> - -x <regex> exclude tests that match the regular expression
> -
> -Useful patterns for test filtering are described in the API
> -documentation and the full list of tests and subtests can be produced
> -by passing -l to the run-tests.sh script.
> -
> -Results are written to a JSON file and an HTML summary can also be
> -created by passing -s to the run-tests.sh script. Further options are
> -are detailed by using the -h option.
> -
> -
> -If not using the script, piglit can be obtained from:
> -
> - git://anongit.freedesktop.org/piglit
> -
> -There is no need to build and install piglit if it is only going to be
> -used for running i-g-t tests.
> -
> -Set the IGT_TEST_ROOT environment variable to point to the tests
> -directory, or set the path key in the "igt" section of piglit.conf to
> -the igt-gpu-tools root directory.
> -
> -The tests in the i-g-t sources need to have been built already. Then we
> -can run the testcases with (as usual as root, no other drm clients
> -running):
> -
> - piglit-sources # ./piglit run igt <results-file>
> -
> -The testlist is built at runtime, so no need to update anything in
> -piglit when adding new tests. See
> -
> - piglit-sources $ ./piglit run -h
> -
> -for some useful options.
> -
> -Piglit only runs a default set of tests and is useful for regression
> -testing. Other tests not run are:
> -- tests that might hang the gpu, see HANG in Makefile.am
> -- gem_stress, a stress test suite. Look at the source for all the
> - various options.
> -- testdisplay is only run in the default mode. testdisplay has tons of
> - options to test different kms functionality, again read the source for
> - the details.
> -
> -**lib/**
> -
> -Common helper functions and headers used by the other tools.
> -
> -**man/**
> -
> -Manpages, unfortunately rather incomplete.
> -
> -**tools/**
> -
> -This is a collection of debugging tools that had previously been
> -built with the 2D driver but not shipped. Some distros were hacking
> -up the 2D build to ship them. Instead, here's a separate package for
> -people debugging the driver.
> -
> -These tools generally must be run as root, except for the ones that just
> -decode dumps.
> -
> -**docs/**
> -
> -Contains the automatically generated igt-gpu-tools libraries
> -reference documentation in docs/reference/. You need to have the
> -gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
> -to generate this API documentation.
> -
> -To regenerate the html files when updating documentation, use:
> -
> - $ ninja -C build igt-gpu-tools-doc
> -
> -If you've added/changed/removed a symbol or anything else that changes
> -the overall structure or indexes, this needs to be reflected in
> -igt-gpu-tools-sections.txt. Entirely new sections will also need to be
> -added to igt-gpu-tools-docs.xml in the appropriate place.
> -
> -**include/drm-uapi**
> -
> -Imported DRM uapi headers from airlied's drm-next branch.
> -These should be updated all together by executing "make
> -headers_install" from that branch of the kernel and then
> -copying the resulting ./usr/include/drm/*.h in and committing
> -with a note of which commit on airlied's branch was used to
> -generate them.
> +Generated documentation for the latest master is published under
> +<https://drm.pages.freedesktop.org/igt-gpu-tools/>.
>
>
> Requirements
> ------------
>
> -This is a non-exhaustive list of package dependencies required for
> building
> -the default configuration (package names may vary):
> +See `Dockerfiles.*` for up-to-date list of packages names in Fedora and
>
s/Dockerfiles/Dockerfile/
s/packages/package/
> +Debian.
>
> - bison
> - gtk-doc-tools
> - flex
> - libcairo2-dev
> - libdrm-dev
> - libkmod-dev
> - libpixman-1-dev
> - libpciaccess-dev
> - libprocps-dev
> - libudev-dev
> - libunwind-dev
> - liblzma-dev
> - libdw-dev
> - python-docutils
> - x11proto-dri2-dev
> - xutils-dev
> +If your distribution packages IGT you can also use your package manager to
> +install the dependencies, e.g.:
>
> -The following dependencies are required for building chamelium support
> -(package names may vary):
> + # dnf builddep igt-gpu-tools
>
> - libxmlrpc-core-c3-dev
> - libudev-dev
> - libglib2.0-dev
> - libgsl-dev
> +But keep in mind that this may be slightly outdated and miss some
> +recently added dependencies for building the current master.
>
> -The following dependencies are requires for building audio support
> -(package names may vary):
>
> - libasound2-dev
> - libgsl-dev
> +Building
> +--------
>
> -See Dockerfiles.* for package names in different distributions.
> +Oneliner to get started:
>
> -Meson build system support
> ---------------------------
> -
> -Currently we support both meson and automake as build systems, but meson
> is the
> -recommended choice. Oneliner to get started:
> -
> - $ mkdir build && meson build && cd build && ninja
> + $ meson build && ninja -C build
>
> Note that meson insist on separate build directories from the source tree.
>
> @@ -186,26 +45,111 @@ Running selfchecks for lib/tests and tests/ is done
> with
>
>
In v2, whilst you're here, can you also amend the prior line to properly
format the two folder
references to be consistent with the rest of this README:
Running selfchecks for `lib/tests` and `tests/` is done with
> $ ninja -C build test
>
> -Note that this doesn't actually run the testcases in tests/:
> scripts/run-tests.sh
> -should continue to be used for that.
> -
> Documentation is built using
>
> $ ninja -C build igt-gpu-tools-doc
>
> -Note that this needs meson v0.47 or later, earlier versions of meson do
> not
> -track depencies correctly for the documentation build and need:
>
> - $ ninja -C build && ninja -C build igt-gpu-tools-doc
> +Running Tests
> +-------------
>
> -Note that there's a setup script similar to ./autogen.sh which creates a
> -compatibility Makefile with a few useful default targets:
> +In `tests/` you can find a set of automated tests to run against the DRM
> +drivers to validate your changes. Many of the tests have subtests, which
> can
> +be listed by using the `--list-subtests` command line option and then run
> +using the --run-subtest option. If `--run-subtest` is not used, all
> subtests
> +will be run. Some tests have further options and these are detailed by
> using
> +the `--help` option.
>
> - $ ./meson.sh [make-arguments]
> +Most of the test must be run as a root and with no X or Wayland compositor
> +running.
>
> -Releases for maintainers
> -------------------------
> + # build/tests/core_auth
> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
> + Starting subtest: getclient-simple
> + Subtest getclient-simple: SUCCESS (0.001s)
> + Starting subtest: getclient-master-drop
> + Subtest getclient-master-drop: SUCCESS (0.000s)
> + Starting subtest: basic-auth
> + Subtest basic-auth: SUCCESS (0.000s)
> + Starting subtest: many-magics
> + Subtest many-magics: SUCCESS (0.000s)
>
> -(1.14)
> + # build/tests/core_auth --run-subtest getclient-simple
> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
> + Starting subtest: getclient-simple
> + Subtest getclient-simple: SUCCESS (0.000s)
>
> -http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
> +
> +The test suite can be run using the `run-tests.sh` script available in the
> +`scripts/` directory. To use it make sure that `igt_runner` is built,
> e.g.:
> +
> + meson -Drunner=enabled build && ninja -C build
> +
> +`run-tests.sh` has options for filtering and excluding tests from test
> +runs:
> +
> + -t <regex> only include tests that match the regular expression
> + -x <regex> exclude tests that match the regular expression
> +
> +Useful patterns for test filtering are described in the [API
> +documentation][API] and the full list of tests and subtests can be
> produced
> +by passing `-l` to the `run-tests.sh` script. Further options are are
> +detailed by using the `-h` option.
> +
> +Results are written to a JSON file.
> +
> +[API]:
> https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html
> +
> +
> +IGT Containers
> +--------------
> +
> +IGT is packed into nifty docker-compatible containers for ease of
> execution
> +and to avoid having to install all the dependencies. You can use
> +podman/docker to to run it on your system.
> +
> +Oneliner to get you started with the latest master:
> +
> + # podman run --rm --priviledged
> registry.freedesktop.org/drm/igt-gpu-tools/igt:master
> +
> +
> +Other Things
> +------------
> +
> +### `benchmarks/`
> +
> +A collection of useful microbenchmarks that can be used to tune DRM code.
> +
> +The benchmarks require KMS to be enabled. When run with an X Server
> +running, they must be run as root to avoid the authentication
> +requirement.
> +
> +Note that a few other microbenchmarks are in tests (e.g. `gem_gtt_speed`).
> +
> +### `tools/`
> +
> +A collection of debugging tools. They generally must be run as root,
> except
> +for the ones that just decode dumps.
> +
> +### `docs/`
> +
> +Contains the infrastracture to automatically generate igt-gpu-tools
> libraries
>
s/infrastracture/infrastructure/
> +reference documentation. You need to have the gtk-doc tools installed.
> +
> +To regenerate the html files when updating documentation, use:
> +
> + $ ninja -C build igt-gpu-tools-doc
> +
> +If you've added/changed/removed a symbol or anything else that changes the
> +overall structure or indexes you need to reflect the change in
> +`igt-gpu-tools-sections.txt`. Entirely new sections also need to be added
> to
> +`igt-gpu-tools-docs.xml` in the appropriate place.
> +
> +### `include/drm-uapi/`
> +
> +Imported DRM uapi headers from airlied's drm-next branch.
> +
> +These should be updated all together by executing `make headers_install`
> from
> +that branch of the kernel and then copying the resulting
> +`./usr/include/drm/*.h` in and committing with a note of which exact
> commit
> +from the airlied's branch was used to generate them.
>
s/the//
With these couple of small nits fixed, this gets my:
Reviewed-by: Rhys Kidd <rhyskidd@gmail.com>
> --
> 2.21.0
>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
[-- Attachment #1.2: Type: text/html, Size: 16165 bytes --]
[-- Attachment #2: Type: text/plain, Size: 153 bytes --]
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] Make README more friendly
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
` (2 preceding siblings ...)
2019-10-04 9:23 ` [igt-dev] [PATCH i-g-t] " Rhys Kidd
@ 2019-10-04 9:24 ` Petri Latvala
2019-10-04 11:57 ` Jani Nikula
2019-10-04 14:13 ` [igt-dev] [PATCH v2 " Arkadiusz Hiler
` (2 subsequent siblings)
6 siblings, 1 reply; 9+ messages in thread
From: Petri Latvala @ 2019-10-04 9:24 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
On Thu, Oct 03, 2019 at 04:06:57PM +0300, Arkadiusz Hiler wrote:
> * reorder sections so we have a more newbie friendly reading flow:
> requirements -> building -> running
>
> * add links to documentation
>
> * drop mentions of autotools
>
> * drop piglit references
>
> * don't list dependencies, just point to Dockerfiles
>
> * mention IGT containers
>
> Cc: Petri Latvala <petri.latvala@intel.com>
> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
The diff is horrible to read but the resulting README LGTM.
Acked-by: Petri Latvala <petri.latvala@intel.com>
> ---
> README.md | 280 ++++++++++++++++++++++--------------------------------
> 1 file changed, 112 insertions(+), 168 deletions(-)
>
> diff --git a/README.md b/README.md
> index b8c4c5a8..b295dc3e 100644
> --- a/README.md
> +++ b/README.md
> @@ -1,6 +1,7 @@
> IGT GPU Tools
> =============
>
> +
> Description
> -----------
>
> @@ -12,173 +13,31 @@ complicated build procedures or specific testing environments to get useful
> results. Therefore, IGT GPU Tools includes low-level tools and tests
> specifically for development and testing of the DRM Drivers.
>
> -IGT GPU Tools is split into several sections:
> -
> -**benchmarks/**
> -
> -This is a collection of useful microbenchmarks that can be used to tune
> -DRM code in relevant ways.
> -
> -The benchmarks require KMS to be enabled. When run with an X Server
> -running, they must be run as root to avoid the authentication
> -requirement.
> -
> -Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
> -
> -**tests/**
> -
> -This is a set of automated tests to run against the DRM to validate
> -changes. Many of the tests have subtests, which can be listed by using
> -the --list-subtests command line option and then run using the
> ---run-subtest option. If --run-subtest is not used, all subtests will
> -be run. Some tests have futher options and these are detailed by using
> -the --help option.
> -
> -The test suite can be run using the run-tests.sh script available in
> -the scripts directory. Piglit is used to run the tests and can either
> -be installed from your distribution (if available), or can be
> -downloaded locally for use with the script by running:
> -
> - ./scripts/run-tests.sh -d
> -
> -run-tests.sh has options for filtering and excluding tests from test
> -runs:
> -
> - -t <regex> only include tests that match the regular expression
> - -x <regex> exclude tests that match the regular expression
> -
> -Useful patterns for test filtering are described in the API
> -documentation and the full list of tests and subtests can be produced
> -by passing -l to the run-tests.sh script.
> -
> -Results are written to a JSON file and an HTML summary can also be
> -created by passing -s to the run-tests.sh script. Further options are
> -are detailed by using the -h option.
> -
> -
> -If not using the script, piglit can be obtained from:
> -
> - git://anongit.freedesktop.org/piglit
> -
> -There is no need to build and install piglit if it is only going to be
> -used for running i-g-t tests.
> -
> -Set the IGT_TEST_ROOT environment variable to point to the tests
> -directory, or set the path key in the "igt" section of piglit.conf to
> -the igt-gpu-tools root directory.
> -
> -The tests in the i-g-t sources need to have been built already. Then we
> -can run the testcases with (as usual as root, no other drm clients
> -running):
> -
> - piglit-sources # ./piglit run igt <results-file>
> -
> -The testlist is built at runtime, so no need to update anything in
> -piglit when adding new tests. See
> -
> - piglit-sources $ ./piglit run -h
> -
> -for some useful options.
> -
> -Piglit only runs a default set of tests and is useful for regression
> -testing. Other tests not run are:
> -- tests that might hang the gpu, see HANG in Makefile.am
> -- gem_stress, a stress test suite. Look at the source for all the
> - various options.
> -- testdisplay is only run in the default mode. testdisplay has tons of
> - options to test different kms functionality, again read the source for
> - the details.
> -
> -**lib/**
> -
> -Common helper functions and headers used by the other tools.
> -
> -**man/**
> -
> -Manpages, unfortunately rather incomplete.
> -
> -**tools/**
> -
> -This is a collection of debugging tools that had previously been
> -built with the 2D driver but not shipped. Some distros were hacking
> -up the 2D build to ship them. Instead, here's a separate package for
> -people debugging the driver.
> -
> -These tools generally must be run as root, except for the ones that just
> -decode dumps.
> -
> -**docs/**
> -
> -Contains the automatically generated igt-gpu-tools libraries
> -reference documentation in docs/reference/. You need to have the
> -gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
> -to generate this API documentation.
> -
> -To regenerate the html files when updating documentation, use:
> -
> - $ ninja -C build igt-gpu-tools-doc
> -
> -If you've added/changed/removed a symbol or anything else that changes
> -the overall structure or indexes, this needs to be reflected in
> -igt-gpu-tools-sections.txt. Entirely new sections will also need to be
> -added to igt-gpu-tools-docs.xml in the appropriate place.
> -
> -**include/drm-uapi**
> -
> -Imported DRM uapi headers from airlied's drm-next branch.
> -These should be updated all together by executing "make
> -headers_install" from that branch of the kernel and then
> -copying the resulting ./usr/include/drm/*.h in and committing
> -with a note of which commit on airlied's branch was used to
> -generate them.
> +Generated documentation for the latest master is published under
> +<https://drm.pages.freedesktop.org/igt-gpu-tools/>.
>
>
> Requirements
> ------------
>
> -This is a non-exhaustive list of package dependencies required for building
> -the default configuration (package names may vary):
> +See `Dockerfiles.*` for up-to-date list of packages names in Fedora and
> +Debian.
>
> - bison
> - gtk-doc-tools
> - flex
> - libcairo2-dev
> - libdrm-dev
> - libkmod-dev
> - libpixman-1-dev
> - libpciaccess-dev
> - libprocps-dev
> - libudev-dev
> - libunwind-dev
> - liblzma-dev
> - libdw-dev
> - python-docutils
> - x11proto-dri2-dev
> - xutils-dev
> +If your distribution packages IGT you can also use your package manager to
> +install the dependencies, e.g.:
>
> -The following dependencies are required for building chamelium support
> -(package names may vary):
> + # dnf builddep igt-gpu-tools
>
> - libxmlrpc-core-c3-dev
> - libudev-dev
> - libglib2.0-dev
> - libgsl-dev
> +But keep in mind that this may be slightly outdated and miss some
> +recently added dependencies for building the current master.
>
> -The following dependencies are requires for building audio support
> -(package names may vary):
>
> - libasound2-dev
> - libgsl-dev
> +Building
> +--------
>
> -See Dockerfiles.* for package names in different distributions.
> +Oneliner to get started:
>
> -Meson build system support
> ---------------------------
> -
> -Currently we support both meson and automake as build systems, but meson is the
> -recommended choice. Oneliner to get started:
> -
> - $ mkdir build && meson build && cd build && ninja
> + $ meson build && ninja -C build
>
> Note that meson insist on separate build directories from the source tree.
>
> @@ -186,26 +45,111 @@ Running selfchecks for lib/tests and tests/ is done with
>
> $ ninja -C build test
>
> -Note that this doesn't actually run the testcases in tests/: scripts/run-tests.sh
> -should continue to be used for that.
> -
> Documentation is built using
>
> $ ninja -C build igt-gpu-tools-doc
>
> -Note that this needs meson v0.47 or later, earlier versions of meson do not
> -track depencies correctly for the documentation build and need:
>
> - $ ninja -C build && ninja -C build igt-gpu-tools-doc
> +Running Tests
> +-------------
>
> -Note that there's a setup script similar to ./autogen.sh which creates a
> -compatibility Makefile with a few useful default targets:
> +In `tests/` you can find a set of automated tests to run against the DRM
> +drivers to validate your changes. Many of the tests have subtests, which can
> +be listed by using the `--list-subtests` command line option and then run
> +using the --run-subtest option. If `--run-subtest` is not used, all subtests
> +will be run. Some tests have further options and these are detailed by using
> +the `--help` option.
>
> - $ ./meson.sh [make-arguments]
> +Most of the test must be run as a root and with no X or Wayland compositor
> +running.
>
> -Releases for maintainers
> -------------------------
> + # build/tests/core_auth
> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
> + Starting subtest: getclient-simple
> + Subtest getclient-simple: SUCCESS (0.001s)
> + Starting subtest: getclient-master-drop
> + Subtest getclient-master-drop: SUCCESS (0.000s)
> + Starting subtest: basic-auth
> + Subtest basic-auth: SUCCESS (0.000s)
> + Starting subtest: many-magics
> + Subtest many-magics: SUCCESS (0.000s)
>
> -(1.14)
> + # build/tests/core_auth --run-subtest getclient-simple
> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
> + Starting subtest: getclient-simple
> + Subtest getclient-simple: SUCCESS (0.000s)
>
> -http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
> +
> +The test suite can be run using the `run-tests.sh` script available in the
> +`scripts/` directory. To use it make sure that `igt_runner` is built, e.g.:
> +
> + meson -Drunner=enabled build && ninja -C build
> +
> +`run-tests.sh` has options for filtering and excluding tests from test
> +runs:
> +
> + -t <regex> only include tests that match the regular expression
> + -x <regex> exclude tests that match the regular expression
> +
> +Useful patterns for test filtering are described in the [API
> +documentation][API] and the full list of tests and subtests can be produced
> +by passing `-l` to the `run-tests.sh` script. Further options are are
> +detailed by using the `-h` option.
> +
> +Results are written to a JSON file.
> +
> +[API]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html
> +
> +
> +IGT Containers
> +--------------
> +
> +IGT is packed into nifty docker-compatible containers for ease of execution
> +and to avoid having to install all the dependencies. You can use
> +podman/docker to to run it on your system.
> +
> +Oneliner to get you started with the latest master:
> +
> + # podman run --rm --priviledged registry.freedesktop.org/drm/igt-gpu-tools/igt:master
> +
> +
> +Other Things
> +------------
> +
> +### `benchmarks/`
> +
> +A collection of useful microbenchmarks that can be used to tune DRM code.
> +
> +The benchmarks require KMS to be enabled. When run with an X Server
> +running, they must be run as root to avoid the authentication
> +requirement.
> +
> +Note that a few other microbenchmarks are in tests (e.g. `gem_gtt_speed`).
> +
> +### `tools/`
> +
> +A collection of debugging tools. They generally must be run as root, except
> +for the ones that just decode dumps.
> +
> +### `docs/`
> +
> +Contains the infrastracture to automatically generate igt-gpu-tools libraries
> +reference documentation. You need to have the gtk-doc tools installed.
> +
> +To regenerate the html files when updating documentation, use:
> +
> + $ ninja -C build igt-gpu-tools-doc
> +
> +If you've added/changed/removed a symbol or anything else that changes the
> +overall structure or indexes you need to reflect the change in
> +`igt-gpu-tools-sections.txt`. Entirely new sections also need to be added to
> +`igt-gpu-tools-docs.xml` in the appropriate place.
> +
> +### `include/drm-uapi/`
> +
> +Imported DRM uapi headers from airlied's drm-next branch.
> +
> +These should be updated all together by executing `make headers_install` from
> +that branch of the kernel and then copying the resulting
> +`./usr/include/drm/*.h` in and committing with a note of which exact commit
> +from the airlied's branch was used to generate them.
> --
> 2.21.0
>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* Re: [igt-dev] [PATCH i-g-t] Make README more friendly
2019-10-04 9:24 ` Petri Latvala
@ 2019-10-04 11:57 ` Jani Nikula
0 siblings, 0 replies; 9+ messages in thread
From: Jani Nikula @ 2019-10-04 11:57 UTC (permalink / raw)
To: Petri Latvala, Arkadiusz Hiler; +Cc: igt-dev
On Fri, 04 Oct 2019, Petri Latvala <petri.latvala@intel.com> wrote:
> On Thu, Oct 03, 2019 at 04:06:57PM +0300, Arkadiusz Hiler wrote:
>> * reorder sections so we have a more newbie friendly reading flow:
>> requirements -> building -> running
>>
>> * add links to documentation
>>
>> * drop mentions of autotools
>>
>> * drop piglit references
>>
>> * don't list dependencies, just point to Dockerfiles
>>
>> * mention IGT containers
>>
>> Cc: Petri Latvala <petri.latvala@intel.com>
>> Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
>
>
> The diff is horrible to read but the resulting README LGTM.
FWIW, git format-patch --break-rewrites option with suitable N/M values
to force a rewite patch might be helpful in cases like these.
BR,
Jani.
>
> Acked-by: Petri Latvala <petri.latvala@intel.com>
>
>
>
>> ---
>> README.md | 280 ++++++++++++++++++++++--------------------------------
>> 1 file changed, 112 insertions(+), 168 deletions(-)
>>
>> diff --git a/README.md b/README.md
>> index b8c4c5a8..b295dc3e 100644
>> --- a/README.md
>> +++ b/README.md
>> @@ -1,6 +1,7 @@
>> IGT GPU Tools
>> =============
>>
>> +
>> Description
>> -----------
>>
>> @@ -12,173 +13,31 @@ complicated build procedures or specific testing environments to get useful
>> results. Therefore, IGT GPU Tools includes low-level tools and tests
>> specifically for development and testing of the DRM Drivers.
>>
>> -IGT GPU Tools is split into several sections:
>> -
>> -**benchmarks/**
>> -
>> -This is a collection of useful microbenchmarks that can be used to tune
>> -DRM code in relevant ways.
>> -
>> -The benchmarks require KMS to be enabled. When run with an X Server
>> -running, they must be run as root to avoid the authentication
>> -requirement.
>> -
>> -Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
>> -
>> -**tests/**
>> -
>> -This is a set of automated tests to run against the DRM to validate
>> -changes. Many of the tests have subtests, which can be listed by using
>> -the --list-subtests command line option and then run using the
>> ---run-subtest option. If --run-subtest is not used, all subtests will
>> -be run. Some tests have futher options and these are detailed by using
>> -the --help option.
>> -
>> -The test suite can be run using the run-tests.sh script available in
>> -the scripts directory. Piglit is used to run the tests and can either
>> -be installed from your distribution (if available), or can be
>> -downloaded locally for use with the script by running:
>> -
>> - ./scripts/run-tests.sh -d
>> -
>> -run-tests.sh has options for filtering and excluding tests from test
>> -runs:
>> -
>> - -t <regex> only include tests that match the regular expression
>> - -x <regex> exclude tests that match the regular expression
>> -
>> -Useful patterns for test filtering are described in the API
>> -documentation and the full list of tests and subtests can be produced
>> -by passing -l to the run-tests.sh script.
>> -
>> -Results are written to a JSON file and an HTML summary can also be
>> -created by passing -s to the run-tests.sh script. Further options are
>> -are detailed by using the -h option.
>> -
>> -
>> -If not using the script, piglit can be obtained from:
>> -
>> - git://anongit.freedesktop.org/piglit
>> -
>> -There is no need to build and install piglit if it is only going to be
>> -used for running i-g-t tests.
>> -
>> -Set the IGT_TEST_ROOT environment variable to point to the tests
>> -directory, or set the path key in the "igt" section of piglit.conf to
>> -the igt-gpu-tools root directory.
>> -
>> -The tests in the i-g-t sources need to have been built already. Then we
>> -can run the testcases with (as usual as root, no other drm clients
>> -running):
>> -
>> - piglit-sources # ./piglit run igt <results-file>
>> -
>> -The testlist is built at runtime, so no need to update anything in
>> -piglit when adding new tests. See
>> -
>> - piglit-sources $ ./piglit run -h
>> -
>> -for some useful options.
>> -
>> -Piglit only runs a default set of tests and is useful for regression
>> -testing. Other tests not run are:
>> -- tests that might hang the gpu, see HANG in Makefile.am
>> -- gem_stress, a stress test suite. Look at the source for all the
>> - various options.
>> -- testdisplay is only run in the default mode. testdisplay has tons of
>> - options to test different kms functionality, again read the source for
>> - the details.
>> -
>> -**lib/**
>> -
>> -Common helper functions and headers used by the other tools.
>> -
>> -**man/**
>> -
>> -Manpages, unfortunately rather incomplete.
>> -
>> -**tools/**
>> -
>> -This is a collection of debugging tools that had previously been
>> -built with the 2D driver but not shipped. Some distros were hacking
>> -up the 2D build to ship them. Instead, here's a separate package for
>> -people debugging the driver.
>> -
>> -These tools generally must be run as root, except for the ones that just
>> -decode dumps.
>> -
>> -**docs/**
>> -
>> -Contains the automatically generated igt-gpu-tools libraries
>> -reference documentation in docs/reference/. You need to have the
>> -gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
>> -to generate this API documentation.
>> -
>> -To regenerate the html files when updating documentation, use:
>> -
>> - $ ninja -C build igt-gpu-tools-doc
>> -
>> -If you've added/changed/removed a symbol or anything else that changes
>> -the overall structure or indexes, this needs to be reflected in
>> -igt-gpu-tools-sections.txt. Entirely new sections will also need to be
>> -added to igt-gpu-tools-docs.xml in the appropriate place.
>> -
>> -**include/drm-uapi**
>> -
>> -Imported DRM uapi headers from airlied's drm-next branch.
>> -These should be updated all together by executing "make
>> -headers_install" from that branch of the kernel and then
>> -copying the resulting ./usr/include/drm/*.h in and committing
>> -with a note of which commit on airlied's branch was used to
>> -generate them.
>> +Generated documentation for the latest master is published under
>> +<https://drm.pages.freedesktop.org/igt-gpu-tools/>.
>>
>>
>> Requirements
>> ------------
>>
>> -This is a non-exhaustive list of package dependencies required for building
>> -the default configuration (package names may vary):
>> +See `Dockerfiles.*` for up-to-date list of packages names in Fedora and
>> +Debian.
>>
>> - bison
>> - gtk-doc-tools
>> - flex
>> - libcairo2-dev
>> - libdrm-dev
>> - libkmod-dev
>> - libpixman-1-dev
>> - libpciaccess-dev
>> - libprocps-dev
>> - libudev-dev
>> - libunwind-dev
>> - liblzma-dev
>> - libdw-dev
>> - python-docutils
>> - x11proto-dri2-dev
>> - xutils-dev
>> +If your distribution packages IGT you can also use your package manager to
>> +install the dependencies, e.g.:
>>
>> -The following dependencies are required for building chamelium support
>> -(package names may vary):
>> + # dnf builddep igt-gpu-tools
>>
>> - libxmlrpc-core-c3-dev
>> - libudev-dev
>> - libglib2.0-dev
>> - libgsl-dev
>> +But keep in mind that this may be slightly outdated and miss some
>> +recently added dependencies for building the current master.
>>
>> -The following dependencies are requires for building audio support
>> -(package names may vary):
>>
>> - libasound2-dev
>> - libgsl-dev
>> +Building
>> +--------
>>
>> -See Dockerfiles.* for package names in different distributions.
>> +Oneliner to get started:
>>
>> -Meson build system support
>> ---------------------------
>> -
>> -Currently we support both meson and automake as build systems, but meson is the
>> -recommended choice. Oneliner to get started:
>> -
>> - $ mkdir build && meson build && cd build && ninja
>> + $ meson build && ninja -C build
>>
>> Note that meson insist on separate build directories from the source tree.
>>
>> @@ -186,26 +45,111 @@ Running selfchecks for lib/tests and tests/ is done with
>>
>> $ ninja -C build test
>>
>> -Note that this doesn't actually run the testcases in tests/: scripts/run-tests.sh
>> -should continue to be used for that.
>> -
>> Documentation is built using
>>
>> $ ninja -C build igt-gpu-tools-doc
>>
>> -Note that this needs meson v0.47 or later, earlier versions of meson do not
>> -track depencies correctly for the documentation build and need:
>>
>> - $ ninja -C build && ninja -C build igt-gpu-tools-doc
>> +Running Tests
>> +-------------
>>
>> -Note that there's a setup script similar to ./autogen.sh which creates a
>> -compatibility Makefile with a few useful default targets:
>> +In `tests/` you can find a set of automated tests to run against the DRM
>> +drivers to validate your changes. Many of the tests have subtests, which can
>> +be listed by using the `--list-subtests` command line option and then run
>> +using the --run-subtest option. If `--run-subtest` is not used, all subtests
>> +will be run. Some tests have further options and these are detailed by using
>> +the `--help` option.
>>
>> - $ ./meson.sh [make-arguments]
>> +Most of the test must be run as a root and with no X or Wayland compositor
>> +running.
>>
>> -Releases for maintainers
>> -------------------------
>> + # build/tests/core_auth
>> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
>> + Starting subtest: getclient-simple
>> + Subtest getclient-simple: SUCCESS (0.001s)
>> + Starting subtest: getclient-master-drop
>> + Subtest getclient-master-drop: SUCCESS (0.000s)
>> + Starting subtest: basic-auth
>> + Subtest basic-auth: SUCCESS (0.000s)
>> + Starting subtest: many-magics
>> + Subtest many-magics: SUCCESS (0.000s)
>>
>> -(1.14)
>> + # build/tests/core_auth --run-subtest getclient-simple
>> + IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
>> + Starting subtest: getclient-simple
>> + Subtest getclient-simple: SUCCESS (0.000s)
>>
>> -http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
>> +
>> +The test suite can be run using the `run-tests.sh` script available in the
>> +`scripts/` directory. To use it make sure that `igt_runner` is built, e.g.:
>> +
>> + meson -Drunner=enabled build && ninja -C build
>> +
>> +`run-tests.sh` has options for filtering and excluding tests from test
>> +runs:
>> +
>> + -t <regex> only include tests that match the regular expression
>> + -x <regex> exclude tests that match the regular expression
>> +
>> +Useful patterns for test filtering are described in the [API
>> +documentation][API] and the full list of tests and subtests can be produced
>> +by passing `-l` to the `run-tests.sh` script. Further options are are
>> +detailed by using the `-h` option.
>> +
>> +Results are written to a JSON file.
>> +
>> +[API]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html
>> +
>> +
>> +IGT Containers
>> +--------------
>> +
>> +IGT is packed into nifty docker-compatible containers for ease of execution
>> +and to avoid having to install all the dependencies. You can use
>> +podman/docker to to run it on your system.
>> +
>> +Oneliner to get you started with the latest master:
>> +
>> + # podman run --rm --priviledged registry.freedesktop.org/drm/igt-gpu-tools/igt:master
>> +
>> +
>> +Other Things
>> +------------
>> +
>> +### `benchmarks/`
>> +
>> +A collection of useful microbenchmarks that can be used to tune DRM code.
>> +
>> +The benchmarks require KMS to be enabled. When run with an X Server
>> +running, they must be run as root to avoid the authentication
>> +requirement.
>> +
>> +Note that a few other microbenchmarks are in tests (e.g. `gem_gtt_speed`).
>> +
>> +### `tools/`
>> +
>> +A collection of debugging tools. They generally must be run as root, except
>> +for the ones that just decode dumps.
>> +
>> +### `docs/`
>> +
>> +Contains the infrastracture to automatically generate igt-gpu-tools libraries
>> +reference documentation. You need to have the gtk-doc tools installed.
>> +
>> +To regenerate the html files when updating documentation, use:
>> +
>> + $ ninja -C build igt-gpu-tools-doc
>> +
>> +If you've added/changed/removed a symbol or anything else that changes the
>> +overall structure or indexes you need to reflect the change in
>> +`igt-gpu-tools-sections.txt`. Entirely new sections also need to be added to
>> +`igt-gpu-tools-docs.xml` in the appropriate place.
>> +
>> +### `include/drm-uapi/`
>> +
>> +Imported DRM uapi headers from airlied's drm-next branch.
>> +
>> +These should be updated all together by executing `make headers_install` from
>> +that branch of the kernel and then copying the resulting
>> +`./usr/include/drm/*.h` in and committing with a note of which exact commit
>> +from the airlied's branch was used to generate them.
>> --
>> 2.21.0
>>
> _______________________________________________
> igt-dev mailing list
> igt-dev@lists.freedesktop.org
> https://lists.freedesktop.org/mailman/listinfo/igt-dev
--
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [igt-dev] [PATCH v2 i-g-t] Make README more friendly
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
` (3 preceding siblings ...)
2019-10-04 9:24 ` Petri Latvala
@ 2019-10-04 14:13 ` Arkadiusz Hiler
2019-10-04 15:52 ` [igt-dev] ✓ Fi.CI.BAT: success for Make README more friendly (rev2) Patchwork
2019-10-05 0:44 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
6 siblings, 0 replies; 9+ messages in thread
From: Arkadiusz Hiler @ 2019-10-04 14:13 UTC (permalink / raw)
To: igt-dev; +Cc: Petri Latvala
* reorder sections so we have a more newbie friendly reading flow:
requirements -> building -> running
* add links to documentation
* drop mentions of autotools
* drop piglit references
* don't list dependencies, just point to Dockerfiles
* mention IGT containers
v2: typos, articles and better formatting (Rhys Kidd)
Cc: Petri Latvala <petri.latvala@intel.com>
Signed-off-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Reviewed-by: Rhys Kidd <rhyskidd@gmail.com>
---
delta with v1: https://hiler.eu/p/2874b664
README.md | 366 +++++++++++++++++++++++-------------------------------
1 file changed, 155 insertions(+), 211 deletions(-)
rewrite README.md (81%)
diff --git a/README.md b/README.md
dissimilarity index 81%
index b8c4c5a8..a6a821c0 100644
--- a/README.md
+++ b/README.md
@@ -1,211 +1,155 @@
-IGT GPU Tools
-=============
-
-Description
------------
-
-IGT GPU Tools is a collection of tools for development and testing of the DRM
-drivers. There are many macro-level test suites that get used against the
-drivers, including xtest, rendercheck, piglit, and oglconform, but failures from
-those can be difficult to track down to kernel changes, and many require
-complicated build procedures or specific testing environments to get useful
-results. Therefore, IGT GPU Tools includes low-level tools and tests
-specifically for development and testing of the DRM Drivers.
-
-IGT GPU Tools is split into several sections:
-
-**benchmarks/**
-
-This is a collection of useful microbenchmarks that can be used to tune
-DRM code in relevant ways.
-
-The benchmarks require KMS to be enabled. When run with an X Server
-running, they must be run as root to avoid the authentication
-requirement.
-
-Note that a few other microbenchmarks are in tests (like gem_gtt_speed).
-
-**tests/**
-
-This is a set of automated tests to run against the DRM to validate
-changes. Many of the tests have subtests, which can be listed by using
-the --list-subtests command line option and then run using the
---run-subtest option. If --run-subtest is not used, all subtests will
-be run. Some tests have futher options and these are detailed by using
-the --help option.
-
-The test suite can be run using the run-tests.sh script available in
-the scripts directory. Piglit is used to run the tests and can either
-be installed from your distribution (if available), or can be
-downloaded locally for use with the script by running:
-
- ./scripts/run-tests.sh -d
-
-run-tests.sh has options for filtering and excluding tests from test
-runs:
-
- -t <regex> only include tests that match the regular expression
- -x <regex> exclude tests that match the regular expression
-
-Useful patterns for test filtering are described in the API
-documentation and the full list of tests and subtests can be produced
-by passing -l to the run-tests.sh script.
-
-Results are written to a JSON file and an HTML summary can also be
-created by passing -s to the run-tests.sh script. Further options are
-are detailed by using the -h option.
-
-
-If not using the script, piglit can be obtained from:
-
- git://anongit.freedesktop.org/piglit
-
-There is no need to build and install piglit if it is only going to be
-used for running i-g-t tests.
-
-Set the IGT_TEST_ROOT environment variable to point to the tests
-directory, or set the path key in the "igt" section of piglit.conf to
-the igt-gpu-tools root directory.
-
-The tests in the i-g-t sources need to have been built already. Then we
-can run the testcases with (as usual as root, no other drm clients
-running):
-
- piglit-sources # ./piglit run igt <results-file>
-
-The testlist is built at runtime, so no need to update anything in
-piglit when adding new tests. See
-
- piglit-sources $ ./piglit run -h
-
-for some useful options.
-
-Piglit only runs a default set of tests and is useful for regression
-testing. Other tests not run are:
-- tests that might hang the gpu, see HANG in Makefile.am
-- gem_stress, a stress test suite. Look at the source for all the
- various options.
-- testdisplay is only run in the default mode. testdisplay has tons of
- options to test different kms functionality, again read the source for
- the details.
-
-**lib/**
-
-Common helper functions and headers used by the other tools.
-
-**man/**
-
-Manpages, unfortunately rather incomplete.
-
-**tools/**
-
-This is a collection of debugging tools that had previously been
-built with the 2D driver but not shipped. Some distros were hacking
-up the 2D build to ship them. Instead, here's a separate package for
-people debugging the driver.
-
-These tools generally must be run as root, except for the ones that just
-decode dumps.
-
-**docs/**
-
-Contains the automatically generated igt-gpu-tools libraries
-reference documentation in docs/reference/. You need to have the
-gtk-doc tools installed and use the "--enable-gtk-doc" configure flag
-to generate this API documentation.
-
-To regenerate the html files when updating documentation, use:
-
- $ ninja -C build igt-gpu-tools-doc
-
-If you've added/changed/removed a symbol or anything else that changes
-the overall structure or indexes, this needs to be reflected in
-igt-gpu-tools-sections.txt. Entirely new sections will also need to be
-added to igt-gpu-tools-docs.xml in the appropriate place.
-
-**include/drm-uapi**
-
-Imported DRM uapi headers from airlied's drm-next branch.
-These should be updated all together by executing "make
-headers_install" from that branch of the kernel and then
-copying the resulting ./usr/include/drm/*.h in and committing
-with a note of which commit on airlied's branch was used to
-generate them.
-
-
-Requirements
-------------
-
-This is a non-exhaustive list of package dependencies required for building
-the default configuration (package names may vary):
-
- bison
- gtk-doc-tools
- flex
- libcairo2-dev
- libdrm-dev
- libkmod-dev
- libpixman-1-dev
- libpciaccess-dev
- libprocps-dev
- libudev-dev
- libunwind-dev
- liblzma-dev
- libdw-dev
- python-docutils
- x11proto-dri2-dev
- xutils-dev
-
-The following dependencies are required for building chamelium support
-(package names may vary):
-
- libxmlrpc-core-c3-dev
- libudev-dev
- libglib2.0-dev
- libgsl-dev
-
-The following dependencies are requires for building audio support
-(package names may vary):
-
- libasound2-dev
- libgsl-dev
-
-See Dockerfiles.* for package names in different distributions.
-
-Meson build system support
---------------------------
-
-Currently we support both meson and automake as build systems, but meson is the
-recommended choice. Oneliner to get started:
-
- $ mkdir build && meson build && cd build && ninja
-
-Note that meson insist on separate build directories from the source tree.
-
-Running selfchecks for lib/tests and tests/ is done with
-
- $ ninja -C build test
-
-Note that this doesn't actually run the testcases in tests/: scripts/run-tests.sh
-should continue to be used for that.
-
-Documentation is built using
-
- $ ninja -C build igt-gpu-tools-doc
-
-Note that this needs meson v0.47 or later, earlier versions of meson do not
-track depencies correctly for the documentation build and need:
-
- $ ninja -C build && ninja -C build igt-gpu-tools-doc
-
-Note that there's a setup script similar to ./autogen.sh which creates a
-compatibility Makefile with a few useful default targets:
-
- $ ./meson.sh [make-arguments]
-
-Releases for maintainers
-------------------------
-
-(1.14)
-
-http://www.x.org/wiki/Development/Documentation/ReleaseHOWTO/
+IGT GPU Tools
+=============
+
+
+Description
+-----------
+
+IGT GPU Tools is a collection of tools for development and testing of the DRM
+drivers. There are many macro-level test suites that get used against the
+drivers, including xtest, rendercheck, piglit, and oglconform, but failures from
+those can be difficult to track down to kernel changes, and many require
+complicated build procedures or specific testing environments to get useful
+results. Therefore, IGT GPU Tools includes low-level tools and tests
+specifically for development and testing of the DRM Drivers.
+
+Generated documentation for the latest master is published under
+<https://drm.pages.freedesktop.org/igt-gpu-tools/>.
+
+
+Requirements
+------------
+
+See `Dockerfile.*` for up-to-date list of package names in Fedora and
+Debian.
+
+If your distribution packages IGT you can also use your package manager to
+install the dependencies, e.g.:
+
+ # dnf builddep igt-gpu-tools
+
+But keep in mind that this may be slightly outdated and miss some
+recently added dependencies for building the current master.
+
+
+Building
+--------
+
+Oneliner to get started:
+
+ $ meson build && ninja -C build
+
+Note that meson insist on separate build directories from the source tree.
+
+Running selfchecks for `lib/tests` and `tests/` is done with
+
+ $ ninja -C build test
+
+Documentation is built using
+
+ $ ninja -C build igt-gpu-tools-doc
+
+
+Running Tests
+-------------
+
+In `tests/` you can find a set of automated tests to run against the DRM
+drivers to validate your changes. Many of the tests have subtests, which can
+be listed by using the `--list-subtests` command line option and then run
+using the --run-subtest option. If `--run-subtest` is not used, all subtests
+will be run. Some tests have further options and these are detailed by using
+the `--help` option.
+
+Most of the test must be run as a root and with no X or Wayland compositor
+running.
+
+ # build/tests/core_auth
+ IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
+ Starting subtest: getclient-simple
+ Subtest getclient-simple: SUCCESS (0.001s)
+ Starting subtest: getclient-master-drop
+ Subtest getclient-master-drop: SUCCESS (0.000s)
+ Starting subtest: basic-auth
+ Subtest basic-auth: SUCCESS (0.000s)
+ Starting subtest: many-magics
+ Subtest many-magics: SUCCESS (0.000s)
+
+ # build/tests/core_auth --run-subtest getclient-simple
+ IGT-Version: 1.24 (x86_64) (Linux: 5.3.0 x86_64)
+ Starting subtest: getclient-simple
+ Subtest getclient-simple: SUCCESS (0.000s)
+
+
+The test suite can be run using the `run-tests.sh` script available in the
+`scripts/` directory. To use it make sure that `igt_runner` is built, e.g.:
+
+ meson -Drunner=enabled build && ninja -C build
+
+`run-tests.sh` has options for filtering and excluding tests from test
+runs:
+
+ -t <regex> only include tests that match the regular expression
+ -x <regex> exclude tests that match the regular expression
+
+Useful patterns for test filtering are described in the [API
+documentation][API] and the full list of tests and subtests can be produced
+by passing `-l` to the `run-tests.sh` script. Further options are are
+detailed by using the `-h` option.
+
+Results are written to a JSON file.
+
+[API]: https://drm.pages.freedesktop.org/igt-gpu-tools/igt-gpu-tools-Core.html
+
+
+IGT Containers
+--------------
+
+IGT is packed into nifty docker-compatible containers for ease of execution
+and to avoid having to install all the dependencies. You can use
+podman/docker to to run it on your system.
+
+Oneliner to get you started with the latest master:
+
+ # podman run --rm --priviledged registry.freedesktop.org/drm/igt-gpu-tools/igt:master
+
+
+Other Things
+------------
+
+### `benchmarks/`
+
+A collection of useful microbenchmarks that can be used to tune DRM code.
+
+The benchmarks require KMS to be enabled. When run with an X Server
+running, they must be run as root to avoid the authentication
+requirement.
+
+Note that a few other microbenchmarks are in tests (e.g. `gem_gtt_speed`).
+
+### `tools/`
+
+A collection of debugging tools. They generally must be run as root, except
+for the ones that just decode dumps.
+
+### `docs/`
+
+Contains the infrastructure to automatically generate igt-gpu-tools libraries
+reference documentation. You need to have the gtk-doc tools installed.
+
+To regenerate the html files when updating documentation, use:
+
+ $ ninja -C build igt-gpu-tools-doc
+
+If you've added/changed/removed a symbol or anything else that changes the
+overall structure or indexes you need to reflect the change in
+`igt-gpu-tools-sections.txt`. Entirely new sections also need to be added to
+`igt-gpu-tools-docs.xml` in the appropriate place.
+
+### `include/drm-uapi/`
+
+Imported DRM uapi headers from airlied's drm-next branch.
+
+These should be updated all together by executing `make headers_install` from
+that branch of the kernel and then copying the resulting
+`./usr/include/drm/*.h` in and committing with a note of which exact commit
+from airlied's branch was used to generate them.
--
2.21.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 9+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for Make README more friendly (rev2)
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
` (4 preceding siblings ...)
2019-10-04 14:13 ` [igt-dev] [PATCH v2 " Arkadiusz Hiler
@ 2019-10-04 15:52 ` Patchwork
2019-10-05 0:44 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
6 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2019-10-04 15:52 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
== Series Details ==
Series: Make README more friendly (rev2)
URL : https://patchwork.freedesktop.org/series/67536/
State : success
== Summary ==
CI Bug Log - changes from CI_DRM_7010 -> IGTPW_3536
====================================================
Summary
-------
**SUCCESS**
No regressions found.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
Known issues
------------
Here are the changes found in IGTPW_3536 that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_cpu_reloc@basic:
- fi-icl-u3: [PASS][1] -> [DMESG-WARN][2] ([fdo#107724])
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/fi-icl-u3/igt@gem_cpu_reloc@basic.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/fi-icl-u3/igt@gem_cpu_reloc@basic.html
#### Possible fixes ####
* igt@core_auth@basic-auth:
- fi-icl-u3: [DMESG-WARN][3] ([fdo#107724]) -> [PASS][4]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/fi-icl-u3/igt@core_auth@basic-auth.html
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/fi-icl-u3/igt@core_auth@basic-auth.html
* igt@gem_ctx_create@basic-files:
- fi-icl-u3: [INCOMPLETE][5] ([fdo#107713] / [fdo#109100]) -> [PASS][6]
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/fi-icl-u3/igt@gem_ctx_create@basic-files.html
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/fi-icl-u3/igt@gem_ctx_create@basic-files.html
* igt@gem_exec_suspend@basic:
- fi-icl-u2: [FAIL][7] ([fdo#111699]) -> [PASS][8]
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/fi-icl-u2/igt@gem_exec_suspend@basic.html
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/fi-icl-u2/igt@gem_exec_suspend@basic.html
* igt@gem_exec_suspend@basic-s3:
- fi-blb-e6850: [INCOMPLETE][9] ([fdo#107718]) -> [PASS][10]
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/fi-blb-e6850/igt@gem_exec_suspend@basic-s3.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo#107713]: https://bugs.freedesktop.org/show_bug.cgi?id=107713
[fdo#107718]: https://bugs.freedesktop.org/show_bug.cgi?id=107718
[fdo#107724]: https://bugs.freedesktop.org/show_bug.cgi?id=107724
[fdo#109100]: https://bugs.freedesktop.org/show_bug.cgi?id=109100
[fdo#111045]: https://bugs.freedesktop.org/show_bug.cgi?id=111045
[fdo#111096]: https://bugs.freedesktop.org/show_bug.cgi?id=111096
[fdo#111699]: https://bugs.freedesktop.org/show_bug.cgi?id=111699
Participating hosts (51 -> 44)
------------------------------
Additional (1): fi-icl-guc
Missing (8): fi-ilk-m540 fi-tgl-u fi-hsw-4200u fi-byt-squawks fi-bsw-cyan fi-icl-y fi-byt-clapper fi-bdw-samus
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5211 -> IGTPW_3536
CI-20190529: 20190529
CI_DRM_7010: 0d2c0d7bfb5246b27ab8d9601ac1251501afe827 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3536: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
IGT_5211: 1601e1571eb0f29a06b64494040b3ea7859a650f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
* [igt-dev] ✗ Fi.CI.IGT: failure for Make README more friendly (rev2)
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
` (5 preceding siblings ...)
2019-10-04 15:52 ` [igt-dev] ✓ Fi.CI.BAT: success for Make README more friendly (rev2) Patchwork
@ 2019-10-05 0:44 ` Patchwork
6 siblings, 0 replies; 9+ messages in thread
From: Patchwork @ 2019-10-05 0:44 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
== Series Details ==
Series: Make README more friendly (rev2)
URL : https://patchwork.freedesktop.org/series/67536/
State : failure
== Summary ==
CI Bug Log - changes from CI_DRM_7010_full -> IGTPW_3536_full
====================================================
Summary
-------
**FAILURE**
Serious unknown changes coming with IGTPW_3536_full absolutely need to be
verified manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_3536_full, please notify your bug team to allow them
to document this new failure mode, which will reduce false positives in CI.
External URL: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
Possible new issues
-------------------
Here are the unknown changes that may have been introduced in IGTPW_3536_full:
### IGT changes ###
#### Possible regressions ####
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-iclb: [PASS][1] -> [DMESG-WARN][2]
[1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb5/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
[2]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb3/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
#### Suppressed ####
The following results come from untrusted machines, tests, or statuses.
They do not affect the overall result.
* {igt@gem_eio@kms}:
- {shard-tglb}: NOTRUN -> [INCOMPLETE][3]
[3]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb6/igt@gem_eio@kms.html
Known issues
------------
Here are the changes found in IGTPW_3536_full that come from known issues:
### IGT changes ###
#### Issues hit ####
* igt@gem_ctx_shared@exec-single-timeline-bsd:
- shard-iclb: [PASS][4] -> [SKIP][5] ([fdo#110841])
[4]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb6/igt@gem_ctx_shared@exec-single-timeline-bsd.html
[5]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb1/igt@gem_ctx_shared@exec-single-timeline-bsd.html
* igt@gem_exec_balancer@smoke:
- shard-iclb: [PASS][6] -> [SKIP][7] ([fdo#110854])
[6]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb1/igt@gem_exec_balancer@smoke.html
[7]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb8/igt@gem_exec_balancer@smoke.html
* igt@gem_exec_schedule@in-order-bsd:
- shard-iclb: [PASS][8] -> [SKIP][9] ([fdo#111325]) +5 similar issues
[8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb8/igt@gem_exec_schedule@in-order-bsd.html
[9]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb4/igt@gem_exec_schedule@in-order-bsd.html
* igt@gem_mmap_gtt@hang:
- shard-snb: [PASS][10] -> [INCOMPLETE][11] ([fdo#105411])
[10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-snb2/igt@gem_mmap_gtt@hang.html
[11]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-snb7/igt@gem_mmap_gtt@hang.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-glk: [PASS][12] -> [DMESG-WARN][13] ([fdo#111870])
[12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-glk4/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[13]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-glk6/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
* igt@gem_userptr_blits@sync-unmap-cycles:
- shard-snb: [PASS][14] -> [DMESG-WARN][15] ([fdo#111870]) +1 similar issue
[14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-snb4/igt@gem_userptr_blits@sync-unmap-cycles.html
[15]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-snb7/igt@gem_userptr_blits@sync-unmap-cycles.html
- shard-hsw: [PASS][16] -> [DMESG-WARN][17] ([fdo#111870])
[16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-hsw8/igt@gem_userptr_blits@sync-unmap-cycles.html
[17]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-hsw6/igt@gem_userptr_blits@sync-unmap-cycles.html
- shard-kbl: [PASS][18] -> [DMESG-WARN][19] ([fdo#111870])
[18]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-kbl3/igt@gem_userptr_blits@sync-unmap-cycles.html
[19]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-kbl6/igt@gem_userptr_blits@sync-unmap-cycles.html
- shard-iclb: [PASS][20] -> [DMESG-WARN][21] ([fdo#111870]) +1 similar issue
[20]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb2/igt@gem_userptr_blits@sync-unmap-cycles.html
[21]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb1/igt@gem_userptr_blits@sync-unmap-cycles.html
* igt@i915_suspend@fence-restore-tiled2untiled:
- shard-apl: [PASS][22] -> [DMESG-WARN][23] ([fdo#108566]) +1 similar issue
[22]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-apl1/igt@i915_suspend@fence-restore-tiled2untiled.html
[23]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-apl6/igt@i915_suspend@fence-restore-tiled2untiled.html
* igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render:
- shard-iclb: [PASS][24] -> [FAIL][25] ([fdo#103167]) +4 similar issues
[24]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb5/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render.html
[25]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb2/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-render.html
* igt@kms_psr@psr2_primary_page_flip:
- shard-iclb: [PASS][26] -> [SKIP][27] ([fdo#109441]) +1 similar issue
[26]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb2/igt@kms_psr@psr2_primary_page_flip.html
[27]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb8/igt@kms_psr@psr2_primary_page_flip.html
* igt@kms_setmode@basic:
- shard-hsw: [PASS][28] -> [FAIL][29] ([fdo#99912])
[28]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-hsw1/igt@kms_setmode@basic.html
[29]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-hsw5/igt@kms_setmode@basic.html
* igt@prime_vgem@fence-wait-bsd2:
- shard-iclb: [PASS][30] -> [SKIP][31] ([fdo#109276]) +16 similar issues
[30]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb1/igt@prime_vgem@fence-wait-bsd2.html
[31]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb5/igt@prime_vgem@fence-wait-bsd2.html
#### Possible fixes ####
* igt@gem_exec_schedule@preemptive-hang-bsd:
- shard-iclb: [SKIP][32] ([fdo#111325]) -> [PASS][33] +7 similar issues
[32]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb2/igt@gem_exec_schedule@preemptive-hang-bsd.html
[33]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb8/igt@gem_exec_schedule@preemptive-hang-bsd.html
* igt@gem_mmap_gtt@hang:
- shard-kbl: [DMESG-WARN][34] -> [PASS][35]
[34]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-kbl2/igt@gem_mmap_gtt@hang.html
[35]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-kbl4/igt@gem_mmap_gtt@hang.html
- shard-iclb: [DMESG-WARN][36] -> [PASS][37]
[36]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb8/igt@gem_mmap_gtt@hang.html
[37]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb5/igt@gem_mmap_gtt@hang.html
* igt@gem_mocs_settings@mocs-settings-ctx-render:
- {shard-tglb}: [FAIL][38] ([fdo#111645] / [fdo#111723]) -> [PASS][39]
[38]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb4/igt@gem_mocs_settings@mocs-settings-ctx-render.html
[39]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb5/igt@gem_mocs_settings@mocs-settings-ctx-render.html
* igt@gem_userptr_blits@coherency-sync:
- shard-hsw: [DMESG-WARN][40] ([fdo#111870]) -> [PASS][41] +4 similar issues
[40]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-hsw2/igt@gem_userptr_blits@coherency-sync.html
[41]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-hsw2/igt@gem_userptr_blits@coherency-sync.html
* igt@gem_userptr_blits@dmabuf-unsync:
- {shard-tglb}: [DMESG-WARN][42] ([fdo#111870]) -> [PASS][43]
[42]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb4/igt@gem_userptr_blits@dmabuf-unsync.html
[43]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb6/igt@gem_userptr_blits@dmabuf-unsync.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy:
- shard-snb: [DMESG-WARN][44] ([fdo#111870]) -> [PASS][45] +1 similar issue
[44]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-snb7/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
[45]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy.html
* igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup:
- shard-glk: [DMESG-WARN][46] ([fdo#111870]) -> [PASS][47] +1 similar issue
[46]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-glk8/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
[47]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-glk1/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
- shard-kbl: [DMESG-WARN][48] ([fdo#111870]) -> [PASS][49]
[48]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-kbl3/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
[49]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-kbl3/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
- shard-iclb: [DMESG-WARN][50] ([fdo#111870]) -> [PASS][51]
[50]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb2/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
[51]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb5/igt@gem_userptr_blits@map-fixed-invalidate-overlap-busy-gup.html
* igt@gem_userptr_blits@sync-unmap-after-close:
- shard-hsw: [DMESG-WARN][52] ([fdo#110789] / [fdo#111870]) -> [PASS][53]
[52]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-hsw1/igt@gem_userptr_blits@sync-unmap-after-close.html
[53]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-hsw5/igt@gem_userptr_blits@sync-unmap-after-close.html
* igt@kms_color@pipe-a-ctm-red-to-blue:
- {shard-tglb}: [FAIL][54] ([fdo#111859]) -> [PASS][55]
[54]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb7/igt@kms_color@pipe-a-ctm-red-to-blue.html
[55]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb8/igt@kms_color@pipe-a-ctm-red-to-blue.html
* igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen:
- {shard-tglb}: [INCOMPLETE][56] -> [PASS][57]
[56]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb6/igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen.html
[57]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb6/igt@kms_cursor_crc@pipe-c-cursor-256x85-offscreen.html
* igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw:
- shard-iclb: [FAIL][58] ([fdo#103167]) -> [PASS][59] +2 similar issues
[58]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb8/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
[59]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb3/igt@kms_frontbuffer_tracking@fbc-1p-pri-indfb-multidraw.html
* igt@kms_frontbuffer_tracking@fbc-suspend:
- shard-apl: [DMESG-WARN][60] ([fdo#108566]) -> [PASS][61] +3 similar issues
[60]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
[61]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-apl4/igt@kms_frontbuffer_tracking@fbc-suspend.html
* igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt:
- {shard-tglb}: [FAIL][62] ([fdo#103167]) -> [PASS][63] +8 similar issues
[62]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb5/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt.html
[63]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb6/igt@kms_frontbuffer_tracking@fbcpsr-1p-primscrn-indfb-plflip-blt.html
* igt@kms_plane_cursor@pipe-a-primary-size-256:
- shard-apl: [INCOMPLETE][64] ([fdo#103927]) -> [PASS][65] +3 similar issues
[64]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-apl1/igt@kms_plane_cursor@pipe-a-primary-size-256.html
[65]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-apl6/igt@kms_plane_cursor@pipe-a-primary-size-256.html
* igt@kms_psr@psr2_cursor_plane_onoff:
- shard-iclb: [SKIP][66] ([fdo#109441]) -> [PASS][67] +2 similar issues
[66]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb6/igt@kms_psr@psr2_cursor_plane_onoff.html
[67]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb2/igt@kms_psr@psr2_cursor_plane_onoff.html
* igt@kms_psr@suspend:
- {shard-tglb}: [INCOMPLETE][68] ([fdo#111832]) -> [PASS][69] +2 similar issues
[68]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-tglb2/igt@kms_psr@suspend.html
[69]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-tglb3/igt@kms_psr@suspend.html
* igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend:
- shard-kbl: [INCOMPLETE][70] ([fdo#103665]) -> [PASS][71]
[70]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-kbl4/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
[71]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-kbl3/igt@kms_vblank@pipe-a-ts-continuation-dpms-suspend.html
* igt@prime_busy@hang-bsd2:
- shard-iclb: [SKIP][72] ([fdo#109276]) -> [PASS][73] +20 similar issues
[72]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb7/igt@prime_busy@hang-bsd2.html
[73]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb1/igt@prime_busy@hang-bsd2.html
#### Warnings ####
* igt@gem_mocs_settings@mocs-reset-bsd2:
- shard-iclb: [FAIL][74] ([fdo#111330]) -> [SKIP][75] ([fdo#109276])
[74]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb1/igt@gem_mocs_settings@mocs-reset-bsd2.html
[75]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb8/igt@gem_mocs_settings@mocs-reset-bsd2.html
* igt@gem_mocs_settings@mocs-settings-bsd2:
- shard-iclb: [SKIP][76] ([fdo#109276]) -> [FAIL][77] ([fdo#111330]) +1 similar issue
[76]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-iclb8/igt@gem_mocs_settings@mocs-settings-bsd2.html
[77]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-iclb2/igt@gem_mocs_settings@mocs-settings-bsd2.html
* igt@gem_userptr_blits@map-fixed-invalidate-busy-gup:
- shard-snb: [DMESG-WARN][78] ([fdo#111870]) -> [DMESG-WARN][79] ([fdo#110789] / [fdo#111870]) +1 similar issue
[78]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7010/shard-snb1/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
[79]: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/shard-snb4/igt@gem_userptr_blits@map-fixed-invalidate-busy-gup.html
{name}: This element is suppressed. This means it is ignored when computing
the status of the difference (SUCCESS, WARNING, or FAILURE).
[fdo# 111852 ]: https://bugs.freedesktop.org/show_bug.cgi?id= 111852
[fdo#102250]: https://bugs.freedesktop.org/show_bug.cgi?id=102250
[fdo#103167]: https://bugs.freedesktop.org/show_bug.cgi?id=103167
[fdo#103665]: https://bugs.freedesktop.org/show_bug.cgi?id=103665
[fdo#103927]: https://bugs.freedesktop.org/show_bug.cgi?id=103927
[fdo#105411]: https://bugs.freedesktop.org/show_bug.cgi?id=105411
[fdo#108566]: https://bugs.freedesktop.org/show_bug.cgi?id=108566
[fdo#109276]: https://bugs.freedesktop.org/show_bug.cgi?id=109276
[fdo#109441]: https://bugs.freedesktop.org/show_bug.cgi?id=109441
[fdo#110789]: https://bugs.freedesktop.org/show_bug.cgi?id=110789
[fdo#110841]: https://bugs.freedesktop.org/show_bug.cgi?id=110841
[fdo#110854]: https://bugs.freedesktop.org/show_bug.cgi?id=110854
[fdo#111325]: https://bugs.freedesktop.org/show_bug.cgi?id=111325
[fdo#111330]: https://bugs.freedesktop.org/show_bug.cgi?id=111330
[fdo#111645]: https://bugs.freedesktop.org/show_bug.cgi?id=111645
[fdo#111646]: https://bugs.freedesktop.org/show_bug.cgi?id=111646
[fdo#111671]: https://bugs.freedesktop.org/show_bug.cgi?id=111671
[fdo#111723]: https://bugs.freedesktop.org/show_bug.cgi?id=111723
[fdo#111781]: https://bugs.freedesktop.org/show_bug.cgi?id=111781
[fdo#111832]: https://bugs.freedesktop.org/show_bug.cgi?id=111832
[fdo#111839 ]: https://bugs.freedesktop.org/show_bug.cgi?id=111839
[fdo#111850]: https://bugs.freedesktop.org/show_bug.cgi?id=111850
[fdo#111859]: https://bugs.freedesktop.org/show_bug.cgi?id=111859
[fdo#111870]: https://bugs.freedesktop.org/show_bug.cgi?id=111870
[fdo#99912]: https://bugs.freedesktop.org/show_bug.cgi?id=99912
Participating hosts (11 -> 7)
------------------------------
Missing (4): pig-skl-6260u shard-skl pig-hsw-4770r pig-glk-j5005
Build changes
-------------
* CI: CI-20190529 -> None
* IGT: IGT_5211 -> IGTPW_3536
* Piglit: piglit_4509 -> None
CI-20190529: 20190529
CI_DRM_7010: 0d2c0d7bfb5246b27ab8d9601ac1251501afe827 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_3536: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
IGT_5211: 1601e1571eb0f29a06b64494040b3ea7859a650f @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
piglit_4509: fdc5a4ca11124ab8413c7988896eec4c97336694 @ git://anongit.freedesktop.org/piglit
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3536/index.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 9+ messages in thread
end of thread, other threads:[~2019-10-05 0:44 UTC | newest]
Thread overview: 9+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2019-10-03 13:06 [igt-dev] [PATCH i-g-t] Make README more friendly Arkadiusz Hiler
2019-10-03 13:53 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-10-03 20:05 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
2019-10-04 9:23 ` [igt-dev] [PATCH i-g-t] " Rhys Kidd
2019-10-04 9:24 ` Petri Latvala
2019-10-04 11:57 ` Jani Nikula
2019-10-04 14:13 ` [igt-dev] [PATCH v2 " Arkadiusz Hiler
2019-10-04 15:52 ` [igt-dev] ✓ Fi.CI.BAT: success for Make README more friendly (rev2) Patchwork
2019-10-05 0:44 ` [igt-dev] ✗ Fi.CI.IGT: failure " Patchwork
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.