public inbox for igt-dev@lists.freedesktop.org
 help / color / mirror / Atom feed
From: Antonio Argenziano <antonio.argenziano@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>,
	Patchwork <patchwork@emeril.freedesktop.org>,
	igt-dev@lists.freedesktop.org
Subject: Re: [igt-dev] ✓ Fi.CI.IGT: success for igt/drm_read: Exercise waking up the next waiter
Date: Wed, 27 Feb 2019 13:47:23 -0800	[thread overview]
Message-ID: <232bd524-a987-b1ac-be44-21742c446b0e@intel.com> (raw)
In-Reply-To: <155130257332.5847.11975904025267607447@skylake-alporthouse-com>



On 27/02/19 13:22, Chris Wilson wrote:
> Quoting Antonio Argenziano (2019-02-27 21:18:10)
>>
>>
>> On 27/02/19 03:48, Patchwork wrote:
>>> == Series Details ==
>>>
>>> Series: igt/drm_read: Exercise waking up the next waiter
>>> URL   : https://patchwork.freedesktop.org/series/57285/
>>> State : success
>>>
>>> == Summary ==
>>>
>>> CI Bug Log - changes from CI_DRM_5664_full -> IGTPW_2531_full
>>> ====================================================
>>>
>>> Summary
>>> -------
>>>
>>>     **SUCCESS**
>>>
>>>     No regressions found.
>>>
>>>     External URL: https://patchwork.freedesktop.org/api/1.0/series/57285/revisions/1/
>>>
>>> Possible new issues
>>> -------------------
>>>
>>>     Here are the unknown changes that may have been introduced in IGTPW_2531_full:
>>>
>>> ### IGT changes ###
>>>
>>> #### Possible regressions ####
>>>
>>>     * {igt@drm_read@short-buffer-wakeup} (NEW):
>>>       - shard-apl:          NOTRUN -> FAIL
>>>       - shard-snb:          NOTRUN -> FAIL
>>>       - shard-kbl:          NOTRUN -> FAIL
>>>       - shard-hsw:          NOTRUN -> FAIL
>>>       - shard-glk:          NOTRUN -> FAIL
>>
>> Is it normal to have the run claim success if a new test is added and fails?
> 
> It's expected, let's call it a feature. New tests start as automatically
> suppressed, so it falls out of that logic.
> 
> Now that Martin has the "its a brand spanking new test" bit worked out,
> the next feature would be indeed to identify that an IGT run with a new
> test is probably interested in that test result; and indeed such a
> series should ideally not be committed until the failure has been
> resolved.


OK, that makes sense.

Thanks,
Antonio

> 
> It would also be useful if the NOTRUN -> {FAIL, PASS} be reported in the
> issues.html so that we didn't have to go searching the full view for
> them.
> -Chris
> 
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev

  reply	other threads:[~2019-02-27 21:47 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-27 10:20 [igt-dev] [PATCH i-g-t] igt/drm_read: Exercise waking up the next waiter Chris Wilson
2019-02-27 10:45 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-02-27 11:48 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
2019-02-27 11:50   ` Chris Wilson
2019-02-27 21:18   ` Antonio Argenziano
2019-02-27 21:22     ` Chris Wilson
2019-02-27 21:47       ` Antonio Argenziano [this message]
2019-02-27 20:46 ` [igt-dev] [PATCH i-g-t] " Ville Syrjälä
2019-02-27 21:13   ` Chris Wilson

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=232bd524-a987-b1ac-be44-21742c446b0e@intel.com \
    --to=antonio.argenziano@intel.com \
    --cc=chris@chris-wilson.co.uk \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=patchwork@emeril.freedesktop.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox