* [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test
@ 2018-09-12 6:51 Petri Latvala
2018-09-12 6:56 ` Arkadiusz Hiler
` (2 more replies)
0 siblings, 3 replies; 7+ messages in thread
From: Petri Latvala @ 2018-09-12 6:51 UTC (permalink / raw)
To: igt-dev
The test is basically just testing if the tools work properly with
little relevance to testing if the kernel works properly. If the
purpose was to test the kernel (or hardware), actual tests will be
better suited for the purpose. If the purpose was to test if the tools
work, sanity checks somewhere else for all tools instead of just two
is better suited for the purpose.
In a nutshell, tools_test as such is fairly useless and has thus far
only revealed problems in testing setups (incorrect paths etc) instead
of problems in kernel or hardware.
Signed-off-by: Petri Latvala <petri.latvala@intel.com>
Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
---
tests/Makefile.sources | 1 -
tests/meson.build | 1 -
tests/tools_test.c | 143 -----------------------------------------
3 files changed, 145 deletions(-)
delete mode 100644 tests/tools_test.c
diff --git a/tests/Makefile.sources b/tests/Makefile.sources
index c84933f1..59a9d51f 100644
--- a/tests/Makefile.sources
+++ b/tests/Makefile.sources
@@ -227,7 +227,6 @@ TESTS_progs = \
syncobj_basic \
syncobj_wait \
template \
- tools_test \
vgem_basic \
vgem_slow \
$(NULL)
diff --git a/tests/meson.build b/tests/meson.build
index 17deb945..f31dc29b 100644
--- a/tests/meson.build
+++ b/tests/meson.build
@@ -201,7 +201,6 @@ test_progs = [
'syncobj_basic',
'syncobj_wait',
'template',
- 'tools_test',
'vc4_create_bo',
'vc4_dmabuf_poll',
'vc4_label_bo',
diff --git a/tests/tools_test.c b/tests/tools_test.c
deleted file mode 100644
index a0025bed..00000000
--- a/tests/tools_test.c
+++ /dev/null
@@ -1,143 +0,0 @@
-/*
- * Copyright © 2017 Intel Corporation
- *
- * Permission is hereby granted, free of charge, to any person obtaining a
- * copy of this software and associated documentation files (the "Software"),
- * to deal in the Software without restriction, including without limitation
- * the rights to use, copy, modify, merge, publish, distribute, sublicense,
- * and/or sell copies of the Software, and to permit persons to whom the
- * Software is furnished to do so, subject to the following conditions:
- *
- * The above copyright notice and this permission notice (including the next
- * paragraph) shall be included in all copies or substantial portions of the
- * Software.
- *
- * THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
- * IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
- * FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL
- * THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
- * LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING
- * FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS
- * IN THE SOFTWARE.
- */
-#include "config.h"
-#include "igt.h"
-#include <stdio.h>
-#include <sys/types.h>
-#include <sys/stat.h>
-#include <fcntl.h>
-#include <libgen.h>
-#include <unistd.h>
-
-#define TOOLS "../tools/"
-
-struct line_check {
- int found;
- const char *substr;
-};
-
-/**
- * Our igt_log_buffer_inspect handler. Checks the output of the
- * intel_l3_parity tool and increments line_check::found if a specific
- * substring is found.
- */
-static bool check_cmd_output(const char *line, void *data)
-{
- struct line_check *check = data;
-
- if (strstr(line, check->substr)) {
- check->found++;
- }
-
- return false;
-}
-
-static void assert_cmd_success(int exec_return)
-{
- igt_skip_on_f(exec_return == IGT_EXIT_SKIP,
- "intel_l3_parity not supported\n");
- igt_assert_eq(exec_return, IGT_EXIT_SUCCESS);
-}
-
-igt_main
-{
- igt_skip_on_simulation();
-
- igt_fixture {
- char path[4096];
-
- /* Try to guess where the TOOLS are! */
- if (access(TOOLS, F_OK) &&
- readlink("/proc/self/exe", path, sizeof(path)) > 0)
- chdir(dirname(path));
-
- igt_require_f(chdir(TOOLS) == 0,
- "Unable to determine the tools directory, expecting them in $cwd/" TOOLS " or $path/" TOOLS "\n");
- }
-
- igt_subtest("sysfs_l3_parity") {
- int exec_return;
- struct line_check line;
-
- igt_require(access("intel_l3_parity", X_OK) == 0);
-
- /* Sanity check that l3 parity tool is usable: Enable
- * row,bank,subbank 0,0,0.
- *
- * TODO: Better way to find intel_l3_parity. This path
- * is relative to piglit's path, when run through
- * piglit.
- */
- igt_system_cmd(exec_return,
- "./intel_l3_parity -r 0 -b 0 "
- "-s 0 -e");
- assert_cmd_success(exec_return);
-
- /* Disable row,bank,subbank 0,0,0. */
- igt_system_cmd(exec_return,
- "./intel_l3_parity -r 0 -b 0 "
- "-s 0 -d");
- assert_cmd_success(exec_return);
-
- /* Check that disabling was successful */
- igt_system_cmd(exec_return,
- "./intel_l3_parity -l");
- assert_cmd_success(exec_return);
- line.substr = "Row 0, Bank 0, Subbank 0 is disabled";
- line.found = 0;
- igt_log_buffer_inspect(check_cmd_output, &line);
- igt_assert_eq(line.found, 1);
-
- /* Re-enable row,bank,subbank 0,0,0 */
- igt_system_cmd(exec_return,
- "./intel_l3_parity -r 0 -b 0 "
- "-s 0 -e");
- assert_cmd_success(exec_return);
-
- /* Check that re-enabling was successful:
- * intel_l3_parity -l should now not print that Row 0,
- * Bank 0, Subbank 0 is disabled.
- *
- * The previously printed line is already in the log
- * buffer so we check for count 1.
- */
- igt_system_cmd(exec_return,
- "./intel_l3_parity -l");
- assert_cmd_success(exec_return);
- line.substr = "Row 0, Bank 0, Subbank 0 is disabled";
- line.found = 0;
- igt_log_buffer_inspect(check_cmd_output,
- &line);
- igt_assert_eq(line.found, 1);
- }
-
- igt_subtest("tools_test") {
- igt_require(access("intel_reg", X_OK) == 0);
-
- igt_assert_eq(igt_system_quiet("./intel_reg read 0x4030"),
- IGT_EXIT_SUCCESS);
-
- igt_assert_eq(igt_system_quiet("./intel_reg dump"),
- IGT_EXIT_SUCCESS);
- }
-}
--
2.18.0
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply related [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test
2018-09-12 6:51 [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test Petri Latvala
@ 2018-09-12 6:56 ` Arkadiusz Hiler
2018-09-14 9:28 ` Daniel Vetter
2018-09-12 8:12 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2018-09-12 10:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2 siblings, 1 reply; 7+ messages in thread
From: Arkadiusz Hiler @ 2018-09-12 6:56 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev
On Wed, Sep 12, 2018 at 09:51:24AM +0300, Petri Latvala wrote:
> The test is basically just testing if the tools work properly with
> little relevance to testing if the kernel works properly. If the
> purpose was to test the kernel (or hardware), actual tests will be
> better suited for the purpose. If the purpose was to test if the tools
> work, sanity checks somewhere else for all tools instead of just two
> is better suited for the purpose.
>
> In a nutshell, tools_test as such is fairly useless and has thus far
> only revealed problems in testing setups (incorrect paths etc) instead
> of problems in kernel or hardware.
>
> Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] tests: Remove tools_test
2018-09-12 6:51 [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test Petri Latvala
2018-09-12 6:56 ` Arkadiusz Hiler
@ 2018-09-12 8:12 ` Patchwork
2018-09-12 10:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2018-09-12 8:12 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev
== Series Details ==
Series: series starting with [i-g-t,1/1] tests: Remove tools_test
URL : https://patchwork.freedesktop.org/series/49527/
State : success
== Summary ==
= CI Bug Log - changes from CI_DRM_4807 -> IGTPW_1826 =
== Summary - SUCCESS ==
No regressions found.
External URL: https://patchwork.freedesktop.org/api/1.0/series/49527/revisions/1/mbox/
== Known issues ==
Here are the changes found in IGTPW_1826 that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_suspend@basic-s3:
fi-kbl-soraka: NOTRUN -> INCOMPLETE (fdo#107556, fdo#107774)
==== Possible fixes ====
igt@gem_exec_suspend@basic-s3:
fi-blb-e6850: INCOMPLETE (fdo#107718) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-a:
fi-cfl-8109u: INCOMPLETE (fdo#106070) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-b:
fi-byt-clapper: FAIL (fdo#103191, fdo#107362) -> PASS
igt@kms_pipe_crc_basic@suspend-read-crc-pipe-c:
fi-bxt-dsi: INCOMPLETE (fdo#103927) -> PASS
fdo#103191 https://bugs.freedesktop.org/show_bug.cgi?id=103191
fdo#103927 https://bugs.freedesktop.org/show_bug.cgi?id=103927
fdo#106070 https://bugs.freedesktop.org/show_bug.cgi?id=106070
fdo#107362 https://bugs.freedesktop.org/show_bug.cgi?id=107362
fdo#107556 https://bugs.freedesktop.org/show_bug.cgi?id=107556
fdo#107718 https://bugs.freedesktop.org/show_bug.cgi?id=107718
fdo#107774 https://bugs.freedesktop.org/show_bug.cgi?id=107774
== Participating hosts (46 -> 42) ==
Additional (1): fi-kbl-soraka
Missing (5): fi-ctg-p8600 fi-ilk-m540 fi-byt-squawks fi-bsw-cyan fi-hsw-4200u
== Build changes ==
* IGT: IGT_4639 -> IGTPW_1826
CI_DRM_4807: 55b148b84b254f61adbfeb89c4f6674664f01c46 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_1826: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1826/
IGT_4639: c7fa2ea9fbce87206474748100b825558eebe08e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Testlist changes ==
-igt@tools_test@sysfs_l3_parity
-igt@tools_test@tools_test
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1826/issues.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* [igt-dev] ✓ Fi.CI.IGT: success for series starting with [i-g-t,1/1] tests: Remove tools_test
2018-09-12 6:51 [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test Petri Latvala
2018-09-12 6:56 ` Arkadiusz Hiler
2018-09-12 8:12 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
@ 2018-09-12 10:13 ` Patchwork
2 siblings, 0 replies; 7+ messages in thread
From: Patchwork @ 2018-09-12 10:13 UTC (permalink / raw)
To: Petri Latvala; +Cc: igt-dev
== Series Details ==
Series: series starting with [i-g-t,1/1] tests: Remove tools_test
URL : https://patchwork.freedesktop.org/series/49527/
State : success
== Summary ==
= CI Bug Log - changes from IGT_4639_full -> IGTPW_1826_full =
== Summary - WARNING ==
Minor unknown changes coming with IGTPW_1826_full need to be verified
manually.
If you think the reported changes have nothing to do with the changes
introduced in IGTPW_1826_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://patchwork.freedesktop.org/api/1.0/series/49527/revisions/1/mbox/
== Possible new issues ==
Here are the unknown changes that may have been introduced in IGTPW_1826_full:
=== IGT changes ===
==== Warnings ====
igt@kms_vblank@pipe-b-wait-idle-hang:
shard-snb: PASS -> SKIP +3
== Known issues ==
Here are the changes found in IGTPW_1826_full that come from known issues:
=== IGT changes ===
==== Issues hit ====
igt@gem_exec_await@wide-contexts:
shard-apl: PASS -> FAIL (fdo#106680)
igt@kms_available_modes_crc@available_mode_test_crc:
shard-snb: PASS -> FAIL (fdo#106641)
igt@kms_cursor_legacy@cursor-vs-flip-varying-size:
shard-hsw: PASS -> FAIL (fdo#103355)
igt@kms_plane@plane-panning-bottom-right-suspend-pipe-c-planes:
shard-kbl: PASS -> INCOMPLETE (fdo#103665)
igt@kms_setmode@basic:
shard-glk: PASS -> FAIL (fdo#99912)
igt@testdisplay:
shard-glk: PASS -> INCOMPLETE (k.org#198133, fdo#107093, fdo#103359)
==== Possible fixes ====
igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
shard-hsw: FAIL (fdo#105767) -> PASS
igt@kms_plane_multiple@atomic-pipe-a-tiling-x:
shard-snb: FAIL (fdo#103166) -> PASS
igt@kms_rotation_crc@sprite-rotation-180:
shard-snb: FAIL (fdo#103925) -> PASS
igt@kms_setmode@basic:
shard-apl: FAIL (fdo#99912) -> PASS
shard-kbl: FAIL (fdo#99912) -> PASS
igt@perf_pmu@all-busy-check-all:
shard-snb: INCOMPLETE (fdo#105411) -> PASS
fdo#103166 https://bugs.freedesktop.org/show_bug.cgi?id=103166
fdo#103355 https://bugs.freedesktop.org/show_bug.cgi?id=103355
fdo#103359 https://bugs.freedesktop.org/show_bug.cgi?id=103359
fdo#103665 https://bugs.freedesktop.org/show_bug.cgi?id=103665
fdo#103925 https://bugs.freedesktop.org/show_bug.cgi?id=103925
fdo#105411 https://bugs.freedesktop.org/show_bug.cgi?id=105411
fdo#105767 https://bugs.freedesktop.org/show_bug.cgi?id=105767
fdo#106641 https://bugs.freedesktop.org/show_bug.cgi?id=106641
fdo#106680 https://bugs.freedesktop.org/show_bug.cgi?id=106680
fdo#107093 https://bugs.freedesktop.org/show_bug.cgi?id=107093
fdo#99912 https://bugs.freedesktop.org/show_bug.cgi?id=99912
k.org#198133 https://bugzilla.kernel.org/show_bug.cgi?id=198133
== Participating hosts (5 -> 5) ==
No changes in participating hosts
== Build changes ==
* IGT: IGT_4639 -> IGTPW_1826
* Linux: CI_DRM_4806 -> CI_DRM_4807
CI_DRM_4806: feeccde66999c5e87be3550f2159e5d7eeb61c67 @ git://anongit.freedesktop.org/gfx-ci/linux
CI_DRM_4807: 55b148b84b254f61adbfeb89c4f6674664f01c46 @ git://anongit.freedesktop.org/gfx-ci/linux
IGTPW_1826: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1826/
IGT_4639: c7fa2ea9fbce87206474748100b825558eebe08e @ git://anongit.freedesktop.org/xorg/app/intel-gpu-tools
== Logs ==
For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_1826/shards.html
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test
2018-09-12 6:56 ` Arkadiusz Hiler
@ 2018-09-14 9:28 ` Daniel Vetter
2018-09-14 13:27 ` Jani Nikula
0 siblings, 1 reply; 7+ messages in thread
From: Daniel Vetter @ 2018-09-14 9:28 UTC (permalink / raw)
To: Arkadiusz Hiler; +Cc: igt-dev
On Wed, Sep 12, 2018 at 09:56:24AM +0300, Arkadiusz Hiler wrote:
> On Wed, Sep 12, 2018 at 09:51:24AM +0300, Petri Latvala wrote:
> > The test is basically just testing if the tools work properly with
> > little relevance to testing if the kernel works properly. If the
> > purpose was to test the kernel (or hardware), actual tests will be
> > better suited for the purpose. If the purpose was to test if the tools
> > work, sanity checks somewhere else for all tools instead of just two
> > is better suited for the purpose.
> >
> > In a nutshell, tools_test as such is fairly useless and has thus far
> > only revealed problems in testing setups (incorrect paths etc) instead
> > of problems in kernel or hardware.
> >
> > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Hm, not terribly happy about this. We have blown up the tools in trivial
ways before, that's why I wrote these. And yes it's incomplete coverage.
But we're also not going around deleting other igt tests, just because
they're not yet fully covering a given area.
So maybe add a FIXME here instead that there's work to do?
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test
2018-09-14 9:28 ` Daniel Vetter
@ 2018-09-14 13:27 ` Jani Nikula
2018-09-14 15:26 ` Daniel Vetter
0 siblings, 1 reply; 7+ messages in thread
From: Jani Nikula @ 2018-09-14 13:27 UTC (permalink / raw)
To: Daniel Vetter, Arkadiusz Hiler; +Cc: igt-dev
On Fri, 14 Sep 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> On Wed, Sep 12, 2018 at 09:56:24AM +0300, Arkadiusz Hiler wrote:
>> On Wed, Sep 12, 2018 at 09:51:24AM +0300, Petri Latvala wrote:
>> > The test is basically just testing if the tools work properly with
>> > little relevance to testing if the kernel works properly. If the
>> > purpose was to test the kernel (or hardware), actual tests will be
>> > better suited for the purpose. If the purpose was to test if the tools
>> > work, sanity checks somewhere else for all tools instead of just two
>> > is better suited for the purpose.
>> >
>> > In a nutshell, tools_test as such is fairly useless and has thus far
>> > only revealed problems in testing setups (incorrect paths etc) instead
>> > of problems in kernel or hardware.
>> >
>> > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
>> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
>> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
>> Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
>
> Hm, not terribly happy about this. We have blown up the tools in trivial
> ways before, that's why I wrote these. And yes it's incomplete coverage.
> But we're also not going around deleting other igt tests, just because
> they're not yet fully covering a given area.
I think there's value in ensuring we don't break the tools from an ABI
perspective. But at the same time I don't think we need to test the
tools for every patch posted on the list. I.e. tool testing should be
separated from ABI testing.
So here's an idea. Extend the tools with a test subcommand or --test
parameter, and have the tools themselves check that the ABI they need
works. Centralize that information in the tools.
For example, 'intel_reg dump' is a ridiculously slow and potentially
dangerous way to test if intel_reg works. I've overlooked that in
tools_test; I would never have added something like that in intel_reg.
BR,
Jani.
--
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] 7+ messages in thread
* Re: [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test
2018-09-14 13:27 ` Jani Nikula
@ 2018-09-14 15:26 ` Daniel Vetter
0 siblings, 0 replies; 7+ messages in thread
From: Daniel Vetter @ 2018-09-14 15:26 UTC (permalink / raw)
To: Jani Nikula; +Cc: igt-dev, Daniel Vetter
On Fri, Sep 14, 2018 at 04:27:14PM +0300, Jani Nikula wrote:
> On Fri, 14 Sep 2018, Daniel Vetter <daniel@ffwll.ch> wrote:
> > On Wed, Sep 12, 2018 at 09:56:24AM +0300, Arkadiusz Hiler wrote:
> >> On Wed, Sep 12, 2018 at 09:51:24AM +0300, Petri Latvala wrote:
> >> > The test is basically just testing if the tools work properly with
> >> > little relevance to testing if the kernel works properly. If the
> >> > purpose was to test the kernel (or hardware), actual tests will be
> >> > better suited for the purpose. If the purpose was to test if the tools
> >> > work, sanity checks somewhere else for all tools instead of just two
> >> > is better suited for the purpose.
> >> >
> >> > In a nutshell, tools_test as such is fairly useless and has thus far
> >> > only revealed problems in testing setups (incorrect paths etc) instead
> >> > of problems in kernel or hardware.
> >> >
> >> > Signed-off-by: Petri Latvala <petri.latvala@intel.com>
> >> > Cc: Daniel Vetter <daniel.vetter@ffwll.ch>
> >> > Cc: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> >> Acked-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
> >
> > Hm, not terribly happy about this. We have blown up the tools in trivial
> > ways before, that's why I wrote these. And yes it's incomplete coverage.
> > But we're also not going around deleting other igt tests, just because
> > they're not yet fully covering a given area.
>
> I think there's value in ensuring we don't break the tools from an ABI
> perspective. But at the same time I don't think we need to test the
> tools for every patch posted on the list. I.e. tool testing should be
> separated from ABI testing.
>
> So here's an idea. Extend the tools with a test subcommand or --test
> parameter, and have the tools themselves check that the ABI they need
> works. Centralize that information in the tools.
>
> For example, 'intel_reg dump' is a ridiculously slow and potentially
> dangerous way to test if intel_reg works. I've overlooked that in
> tools_test; I would never have added something like that in intel_reg.
It's not so much the kernel abi, but libdrm that we've blown up. Or is
that what you mean?
But yeah, a more systematic approach to testing this stuff could be good.
A also honestly wonder how much use the reg dumpers still have, since we
never managed to upstream Damien's gen9+ reg dump tooling afaik :-/
-Daniel
--
Daniel Vetter
Software Engineer, Intel Corporation
http://blog.ffwll.ch
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
^ permalink raw reply [flat|nested] 7+ messages in thread
end of thread, other threads:[~2018-09-14 15:26 UTC | newest]
Thread overview: 7+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2018-09-12 6:51 [igt-dev] [PATCH i-g-t 1/1] tests: Remove tools_test Petri Latvala
2018-09-12 6:56 ` Arkadiusz Hiler
2018-09-14 9:28 ` Daniel Vetter
2018-09-14 13:27 ` Jani Nikula
2018-09-14 15:26 ` Daniel Vetter
2018-09-12 8:12 ` [igt-dev] ✓ Fi.CI.BAT: success for series starting with [i-g-t,1/1] " Patchwork
2018-09-12 10:13 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox