Bug 106989 - [CI] igt@gvt_basic@invalid-placeholder-test is badly named
Summary: [CI] igt@gvt_basic@invalid-placeholder-test is badly named
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: Petri Latvala
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-06-21 11:22 UTC by Martin Peres
Modified: 2018-08-22 09:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Martin Peres 2018-06-21 11:22:24 UTC
The test really does not mean much. How can a placeholder test be invalid?

Could we rename this test to something like @reload-to-enable-gvt?
Comment 1 Chris Wilson 2018-06-21 11:26:10 UTC
The test doesn't do anything, all it was was a placeholder to show how to reload i915 with gvt enabled. It was meant to be replaced by a suite of tests for gvt, but that never happened and we still have no knowledge of when we break their code.
Comment 2 Chris Wilson 2018-06-30 08:13:50 UTC
I think the right thing to do is to simply remove it from BAT. I still hope that we gain some gvt tests.
Comment 3 Chris Wilson 2018-07-17 13:02:15 UTC
No more intriguingly named tests,

commit 8781fd89a63eabed9359d02b50583cca67ff3673 (HEAD, upstream/master)
Author: Chris Wilson <chris@chris-wilson.co.uk>
Date:   Fri Jul 13 18:55:10 2018 +0100

    igt: Remove gvt_basic
    
    This was always a placeholder for GVT stakeholders to provide some
    better tests. 2 years later and none have been put forward so stop
    wasting CI's time running a placeholder.
    
    Bugzilla: https://bugs.freedesktop.org/show_bug.cgi?id=106989
    Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk>
    Cc: Zhi Wang <zhi.a.wang@intel.com>
    Acked-by: Martin Peres <martin.peres@linux.intel.com>
Comment 4 Lakshmi 2018-08-22 09:29:48 UTC
igt@gvt_basic test is removed. Closing the bug.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.