xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Marek Marczykowski <marmarek@invisiblethingslab.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Simon Gaiser <simon@invisiblethingslab.com>,
	Ian Jackson <ian.jackson@citrix.com>,
	xen-devel <xen-devel@lists.xen.org>
Subject: Re: Test for osstest, features used in Qubes OS
Date: Fri, 18 May 2018 18:19:25 +0200	[thread overview]
Message-ID: <20180518161925.GE11683@mail-itl> (raw)
In-Reply-To: <5AFEF73D02000078001C425D@prv1-mh.provo.novell.com>


[-- Attachment #1.1: Type: text/plain, Size: 1008 bytes --]

On Fri, May 18, 2018 at 09:54:37AM -0600, Jan Beulich wrote:
> >>> On 18.05.18 at 17:33, <marmarek@invisiblethingslab.com> wrote:
> > Yes, I'm happy to help with that. As I've said, the basic test is very
> > simple (rtcwake command) and already very useful. The fact that it is(?)
> > broken on staging doesn't make it easier,
> 
> Details on the breakage would be appreciated (on a separate thread),
> unless you plan to address it yourself. I recall Simon(?) mentioning this as
> well, but also not providing sufficient data to consider looking into it
> (perhaps simply because it wasn't easy to obtain useful data, as
> frequently is the case with S3 resume). I think it would be nice if we could
> release 4.11 without a regression here.

I only know that Simon have tested it and it fails. Cc'ing him.

-- 
Best Regards,
Marek Marczykowski-Górecki
Invisible Things Lab
A: Because it messes up the order in which people normally read text.
Q: Why is top-posting such a bad thing?

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[-- Attachment #2: Type: text/plain, Size: 157 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xenproject.org
https://lists.xenproject.org/mailman/listinfo/xen-devel

  reply	other threads:[~2018-05-18 16:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-05-16 21:54 Test for osstest, features used in Qubes OS Marek Marczykowski-Górecki
2018-05-17 12:26 ` Ian Jackson
2018-05-17 14:59   ` Marek Marczykowski-Górecki
2018-05-17 15:12     ` Ian Jackson
2018-05-17 18:00       ` Sander Eikelenboom
2018-05-18 15:44         ` Marek Marczykowski-Górecki
2018-05-18 15:33       ` Marek Marczykowski-Górecki
2018-05-18 15:54         ` Jan Beulich
2018-05-18 16:19           ` Marek Marczykowski [this message]
2018-05-21 15:48             ` George Dunlap
2018-05-21 16:17               ` Andrew Cooper
2018-05-21 16:28                 ` George Dunlap
2018-05-21 17:18                   ` George Dunlap
2018-05-22 22:21               ` Simon Gaiser
2018-05-24 13:15                 ` Jan Beulich
2018-05-24 13:39                   ` Simon Gaiser
2018-05-21 11:04       ` George Dunlap
2018-05-21 11:52         ` Dario Faggioli
2018-05-21 13:57           ` Ian Jackson
2018-05-21 14:11             ` George Dunlap
2018-05-22  7:51             ` Dario Faggioli
2018-05-21 11:49       ` Dario Faggioli

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=20180518161925.GE11683@mail-itl \
    --to=marmarek@invisiblethingslab.com \
    --cc=JBeulich@suse.com \
    --cc=ian.jackson@citrix.com \
    --cc=simon@invisiblethingslab.com \
    --cc=xen-devel@lists.xen.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;
as well as URLs for NNTP newsgroup(s).