Updated -next
Hi all,
Not much in the first -next update under the new process, I'd like to tests the qa process first. Highligths:
- first part of i9xx_crtc_mode_set refactor from Jesse
- quite a few ajax-is-paranoid patches
- HAS_LLC param from Eugeni
- kill i915_mem.c
For easier testing there's also an updated drm-intel-testing branch with the latest -fixes merged in (i.e. the missed irq patches). Testing feedback highly welcome.
Hi Yi,
Please put the -testing branch through the kernel qa process. Btw I've noticed that the nightly tests are missing a few recent i-g-t tests, please upgrade that.
Cheers, Daniel
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
Quoted 13 lines
Hi all,
Not much in the first -next update under the new process, I'd like to tests the qa process first. Highligths:
- first part ofi9xx_crtc_mode_setrefactor from Jesse
- quite a few ajax-is-paranoid patches
-HAS_LLCparam from Eugeni
- killi915_mem.cFor easier testing there's also an updated drm-intel-testing branch with the latest -fixes merged in (i.e. the missed irq patches). Testing feedback highly welcome.
Quoted 6 lines
Hi Yi,
Please put the -testing branch through the kernel qa process. Btw I've noticed that the nightly tests are missing a few recent i-g-t tests, please upgrade that.
Hi Daniel,
I'm confused about branch drm-intel-testing. Does it mean drm-intel-next branch when you said branch drm-intel-testing?
Thank you for finding the issue in nightly tests, I'll work it out soon.
By the way, we will be in vacation till Jan 30th.
Thanks
--Sun Yi
Quoted 5 lines
Cheers, Daniel
--
Daniel Vetter
Mail: [email protected]
Mobile: +41 (0)79 365 57 48
Quoted 15 lines · Yi
Quoted 15 lines
Hi all,
Not much in the first -next update under the new process, I'd like to tests the qa process first. Highligths:
- first part ofi9xx_crtc_mode_setrefactor from Jesse
- quite a few ajax-is-paranoid patches
-HAS_LLCparam from Eugeni
- killi915_mem.cFor easier testing there's also an updated drm-intel-testing branch with the latest -fixes merged in (i.e. the missed irq patches). Testing feedback highly welcome.
Hi Yi,
Quoted 7 lines
Quoted 4 lines
Please put the -testing branch through the kernel qa process. Btw I've noticed that the nightly tests are missing a few recent i-g-t tests, please upgrade that.
I'm confused about branch drm-intel-testing. Does it mean drm-intel-next branch when you said branch drm-intel-testing?
drm-intel-testing is drm-intel-next and drm-intel-fixes merged together (as the time of when I've pushed things out). Gordon Jin said that he prefers to qa one single branch and that qa will take the job of finding out whether an issue has been introduced in -fixes or in -next. I agree that it makes more sense to test everything together, otherwise you'll miss some of the bugfixes in -fixes.
-Daniel
Signature · 3 lines
Daniel Vetter Mail: [email protected] Mobile: +41 (0)79 365 57 48
Quoted 6 lines · On 2012-01-21 15:12+0100 Daniel Vetter wrote:
drm-intel-testing is drm-intel-next and drm-intel-fixes merged together (as the time of when I've pushed things out). Gordon Jin said that he prefers to qa one single branch and that qa will take the job of finding out whether an issue has been introduced in -fixes or in -next. I agree that it makes more sense to test everything together, otherwise you'll miss some of the bugfixes in -fixes.
As an Intel graphics user whose number-one concern is stability, I have to make a comment here. I fully appreciate that the top priority for qa should be the cutting edge so that Intel developers get quick feedback on their changes. But that leaves the -fixes branch untested _on its own_ by qa, and I urge Gordon Jin to rethink that decision. After all, the -fixes branch is quite important to the end user of Intel graphics since it generally propagates sooner than -intel-testing to the users. Also, doing qa for both -intel-testing and -fixes should not double the burden on the qa group since -fixes is much less volatile so doesn't have to be tested nearly as often as -intel-testing.
In sum, my feeling is that if the -fixes branch is to have any separate meaning at all, it has to go through the same qa process (although not as often) as drm-intel-testing.
My $0.02.
Alan
__________________________
Alan W. Irwin
Astronomical research affiliation with Department of Physics and Astronomy, University of Victoria (astrowww.phys.uvic.ca).
Programming affiliations with the FreeEOS equation-of-state implementation for stellar interiors (freeeos.sf.net); the Time Ephemerides project (timeephem.sf.net); PLplot scientific plotting software package (plplot.sf.net); the libLASi project (unifont.org/lasi); the Loads of Linux Links project (loll.sf.net); and the Linux Brochure Project (lbproject.sf.net).
__________________________
Linux-powered Science
__________________________
Quoted 18 lines
-----Original Message-----
From: [email protected] [mailto:[email protected]] On Behalf Of Alan W. Irwin
Sent: Sunday, January 22, 2012 3:45 AM
To: Daniel Vetter
Cc: Intel Graphics Development
Subject: Re: [Intel-gfx] Updated -nextQuoted 6 lines · On 2012-01-21 15:12+0100 Daniel Vetter wrote:
drm-intel-testing is drm-intel-next and drm-intel-fixes merged together (as the time of when I've pushed things out). Gordon Jin said that he prefers to qa one single branch and that qa will take the job of finding out whether an issue has been introduced in -fixes or in -next. I agree that it makes more sense to test everything together, otherwise you'll miss some of the bugfixes in -fixes.
Quoted 5 lines
As an Intel graphics user whose number-one concern is stability, I have to make a comment here. I fully appreciate that the top priority for qa should be the cutting edge so that Intel developers get quick feedback on their changes. But that leaves the -fixes branch untested
_onitsown_by qa, and I urge Gordon Jin to rethink that decision.
(sorry for the late reply as I just came back from vacation)
QA testing against -fixes is unchanged, i.e. running automated tests (like intel-gpu-tools) nightly, and running more manual tests in release cycle. We call it "stable build", together with release branch of other components (like mesa 8.0 branch).
The testing against "unstable build" (cutting edge code, consisting of master branch of components, like mesa master branch, and -next/-testing for kernel) is also unchanged (automated nightly testing + manual). The only thing noticeable in this transition is I suggested -next (continue) to be super-set of -fixes, to make sure the critical fixes in -fixes also included in -next, and also the expensive manual testing against -next partly covers -fixes. Thus Daniel created -testing to meet my requirement.
Hope this clarifies.
Thanks
Gordon