Bug 108889 - [CI][SHARDS] igt@sw_sync@sync_busy_fork_unixsocket - incomplete - __igt_fork_helper: Assertion `!proc->running' failed.
Summary: [CI][SHARDS] igt@sw_sync@sync_busy_fork_unixsocket - incomplete - __igt_fork_...
Status: NEW
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-28 15:21 UTC by Martin Peres
Modified: 2018-11-28 15:32 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2018-11-28 15:21:49 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5197/shard-iclb5/igt@sw_sync@sync_busy_fork_unixsocket.html

Starting subtest: sync_busy_fork_unixsocket
sw_sync: ../lib/igt_core.c:1592: __igt_fork_helper: Assertion `!proc->running' failed.
Received signal SIGABRT.
Comment 1 Martin Peres 2018-11-28 15:24:06 UTC
Also seen on SKL: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_149/fi-skl-6770hq/igt@sw_sync@sync_busy_fork.html

Starting subtest: sync_busy_fork
sw_sync: ../lib/igt_core.c:1592: __igt_fork_helper: Assertion `!proc->running' failed.
Received signal SIGABRT.
Comment 2 Chris Wilson 2018-11-28 15:27:29 UTC
So why was this marked incomplete and not CRASH?
Comment 3 Martin Peres 2018-11-28 15:32:30 UTC
(In reply to Chris Wilson from comment #2)
> So why was this marked incomplete and not CRASH?

+1


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.