Re: [Xen-devel] S3 is broken again in xen-unstable

[Ben Guthro <ben@xxxxxxxxxx>]

On Mon, Apr 29, 2013 at 4:45 AM, Jan Beulich <JBeulich@xxxxxxxx> wrote:
>>>> On 25.04.13 at 14:00, Ben Guthro <ben@xxxxxxxxxx> wrote:
>> I don't have time to bisect this, currently - but just thought I'd let
>> the list know that, while xen-4.2 works (with the recent S3 changes
>> I've submitted) - 4.3 is broken again.
>>
>> I'm not sure if it is the hypervisor, or the kernel, since I upgraded
>> both in my "unstable" build environment.
>>
>> Since this is something that XenClient really relies on working, it
>> has been a pain point with every upgrade of Xen for us.
>
> Perhaps one point here also is that you upgrade in too big steps?

Indeed. Unfortunately, realities in shipping product, and staffing to
this effort also need to be considered, that are out of individual
engineer's control (me)
Since I am not on the open source platform team in Citrix, I am unable
to dedicate my time strictly to the open source development on this,
as much as I would like to.

Also - when a product is stable, and the newer versions are focused on
features we tend not to make use of, it is a tough sell to management
to come up with a reason to upgrade. We stayed on the 4.0.y release
train because it was stable.

>
> More regular participation in development and patch review
> would very likely also help keeping down the number of
> regressions here.

The breakage tends to be out of my expertise, until I have to debug it.
Consequently, I've been learning a lot about schedulers, lately.

That said, these breakages have happened in paths that went through
reviews, and were not caught.
In development of XenClient, test automation is where we tend to
uncover S3 related bugs that are not caught in the review process,
because these problems are indidious in breaking in unexpected ways.

I'll try to participate in reviews in the future though, where I can,
though, since I do appreciate the value in doing so.


Ben

>
> Jan
>
>> It is enormously time consuming to debug on every upgrade, and has a
>> long tail in discovering problems (I started debugging S3 last Aug on
>> xen-unstable, prior to 4.2 being cut)
>>
>> How can we work with the community to try to get some sort of
>> regression testing for this feature that we rely on in our product?
>>
>> Ben
>
>

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel