Bug 108763 - [CI] Make IGT_runner exit with an error code != 0 when aborting
Summary: [CI] Make IGT_runner exit with an error code != 0 when aborting
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: IGT (show other bugs)
Version: XOrg git
Hardware: Other All
: high normal
Assignee: Default DRI bug account
QA Contact:
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2018-11-15 16:03 UTC by Martin Peres
Modified: 2019-01-04 15:39 UTC (History)
1 user (show)

See Also:
i915 platform: ICL
i915 features:


Attachments

Description Martin Peres 2018-11-15 16:03:45 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5142/shard-iclb6/igt@runner@aborted.html

Aborting.
Previous test: nothing
Next test: kms_frontbuffer_tracking (fbc-2p-shrfb-fliptrack)

Kernel tainted (0x240 -- 200)
Comment 1 Martin Peres 2018-11-16 14:06:39 UTC
Right now, our shards do not reboot after the kernel got tainted because it cannot know if the execution of IGT went well or not.
Comment 2 Petri Latvala 2018-11-16 14:40:24 UTC
https://patchwork.freedesktop.org/series/52615/
Comment 3 Chris Wilson 2018-11-20 12:06:45 UTC
commit 68264891ceee34195839d82d4d87cbae08ef2431 (origin/master, origin/HEAD)
Author: Petri Latvala <petri.latvala@intel.com>
Date:   Fri Nov 16 16:32:52 2018 +0200

    runner: Exit with a nonzero status if aborting
    
    Signed-off-by: Petri Latvala <petri.latvala@intel.com>
    Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>
Comment 4 Martin Peres 2019-01-04 15:39:02 UTC
(In reply to Chris Wilson from comment #3)
> commit 68264891ceee34195839d82d4d87cbae08ef2431 (origin/master, origin/HEAD)
> Author: Petri Latvala <petri.latvala@intel.com>
> Date:   Fri Nov 16 16:32:52 2018 +0200
> 
>     runner: Exit with a nonzero status if aborting
>     
>     Signed-off-by: Petri Latvala <petri.latvala@intel.com>
>     Reviewed-by: Arkadiusz Hiler <arkadiusz.hiler@intel.com>

Thanks!


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.