All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien.grall@citrix.com>
To: Ian Campbell <ian.campbell@citrix.com>,
	osstest service owner <osstest-admin@xenproject.org>,
	xen-devel@lists.xensource.com
Cc: Ian Jackson <ian.jackson@eu.citrix.com>
Subject: Re: [linux-3.14 test] 63336: regressions - FAIL
Date: Mon, 2 Nov 2015 11:09:30 +0000	[thread overview]
Message-ID: <5637446A.50502@citrix.com> (raw)
In-Reply-To: <1446459447.3088.5.camel@citrix.com>

Hi Ian,

On 02/11/15 10:17, Ian Campbell wrote:
>> So shall we disable 3.14 job for ARM for once and all?
> 
> Given the above failure I don't think the ability to test the 3.14 kernels
> on the Cambridge instance is all that valuable. So yes, I think we should
> drop ARM from the linux-3.14 flights.

+1

> 
> We should also force push 3.14 if the above was the only failure.

This was the only blocking failure. The rest is under tolerable:

Regressions which are regarded as allowable (not blocking):
 test-amd64-i386-rumpuserxen-i386 15 rumpuserxen-demo-xenstorels/xenstorels.repeat fail like 62648
 test-amd64-amd64-xl-qemuu-win7-amd64 17 guest-stop             fail like 62648
 test-amd64-amd64-xl-qemut-stubdom-debianhvm-amd64-xsm 15 guest-localmigrate.2 fail like 62648
 test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stop             fail like 62648
 test-amd64-i386-xl-qemut-win7-amd64 17 guest-stop              fail like 62648

Regards,

-- 
Julien Grall

  reply	other threads:[~2015-11-02 11:09 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-28 17:31 [linux-3.14 test] 63336: regressions - FAIL osstest service owner
2015-10-28 18:12 ` Julien Grall
2015-11-02 10:17   ` Ian Campbell
2015-11-02 11:09     ` Julien Grall [this message]
2015-11-17 10:58       ` [PATCH OSSTEST v1] make-flight: Stop testing ARM for linux-3.14 flights Ian Campbell
2015-11-17 11:56         ` Ian Jackson

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=5637446A.50502@citrix.com \
    --to=julien.grall@citrix.com \
    --cc=ian.campbell@citrix.com \
    --cc=ian.jackson@eu.citrix.com \
    --cc=osstest-admin@xenproject.org \
    --cc=xen-devel@lists.xensource.com \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.