All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ian Campbell <ian.campbell@citrix.com>
To: Meng Xu <xumengpanda@gmail.com>
Cc: "xen-devel@lists.xenproject.org" <xen-devel@lists.xenproject.org>,
	Dario Faggioli <dario.faggioli@citrix.com>,
	Ian Jackson <Ian.Jackson@eu.citrix.com>,
	Wei Liu <Wei.Liu2@citrix.com>
Subject: Re: [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS
Date: Mon, 29 Jun 2015 09:53:23 +0100	[thread overview]
Message-ID: <1435568003.32500.226.camel@citrix.com> (raw)
In-Reply-To: <CAENZ-+m_3-8ryZ5KoBbJKBAhgJZiiu44EZUgmLqqJkgdOGiB7g@mail.gmail.com>

On Sat, 2015-06-27 at 12:05 -0700, Meng Xu wrote:
> Will I receive the email in cc. list if OSSTest fails?

Test reports are in general only sent to xen-devel. 

While osstest could in theory cc people who touched the branch with e.g.
a branch which tests Linux that would risk spamming a load of Linux
people who would not appreciate that.

AFAIK osstest also has no concept of cc-ing particular people if a
particular job fails, although I suppose that could be added.

> I want/hope to know when/how the RTDS scheduler fails the test so that
> I can also contribute to fix the issue.

I think other than keeping an eye on the reposts on the reports on the
list the only way would be to setup some filters which looked at the
report and noticed rtds failures, the mails are pretty structured so if
you are only interested in the rtds stuff that's likely not too hard.

If something starts failing repeatedly then usually someone will end up
CCing the appropriate maintainer.

Ian.

  reply	other threads:[~2015-06-29  8:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-26 10:58 [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS Dario Faggioli
2015-06-26 11:08 ` Ian Campbell
2015-06-26 11:11   ` Dario Faggioli
2015-06-26 12:02 ` Ian Jackson
2015-06-26 13:43   ` Stop testing SEDF almost at all (at least until Xen 4.2) [was: Re: [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS] Dario Faggioli
2015-06-26 15:24     ` Ian Jackson
2015-06-26 16:09       ` Dario Faggioli
2015-06-26 16:14         ` Ian Campbell
2015-06-29 11:07       ` George Dunlap
2015-06-29 13:31         ` Dario Faggioli
2015-06-27 19:05 ` [PATCH v2] OSSTest: stop testing SEDF, start testing RTDS Meng Xu
2015-06-29  8:53   ` Ian Campbell [this message]
2015-06-29  9:33     ` Dario Faggioli
2015-06-30  4:29       ` Meng Xu
2015-06-30  9:11         ` Ian Jackson
2015-06-30  9:20           ` Ian Campbell
2015-06-30  9:41             ` 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=1435568003.32500.226.camel@citrix.com \
    --to=ian.campbell@citrix.com \
    --cc=Ian.Jackson@eu.citrix.com \
    --cc=Wei.Liu2@citrix.com \
    --cc=dario.faggioli@citrix.com \
    --cc=xen-devel@lists.xenproject.org \
    --cc=xumengpanda@gmail.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.