 put the bugs in to start with
<duflu> alan_g: None are mine (?). I'm trying not to victimize their creators
<duflu> Mostly not mine
<alan_g> Indeed, we all review the MPs
<duflu> Oh and then some devious test reboots my phone
<duflu> alan_g: I remember you suggested making people responsible, back at the sprint. I had thought the same before. The real issue is the person desiring a fix the most is not usually the person who broke it
<alan_g> I think people should be aware of how they broke something so that they can learn. But one can't be made responsible one has to be it.
<duflu> OTOH, if someone is a repeat offender, we would be wise to throttle them with bugfix tasks instead of feature development
<duflu> But that would be mean too
<duflu> More phone testing...
<duflu> alan_g: OK I can reproduce the GLMark2Test hang. It's a visible freeze. Will need to continue tomorrow
<duflu> Visible on mako
<alan_g> duflu: that's great - I couldn't reproduce (admittedly I didn't spend very long on it)
<duflu> alan_g: I suspect we're not matching up number of buffer replies with number of requests. Both server and client are starved and idling
<alan_g> Then you've got processes to poke around in? Even better.
<alan_g> I'll be glad to see that one gone
<duflu> alan_g: Yeah. Annoyingly seems related to what I'm fixing, but more needs fixing obviously
<alan_g> duflu: hopefully that means there will be a unified fix that will be obviously correct. (Once you've thought of it.)
<duflu> alan_g: Or many
 * alan_g hopes not
<duflu> Oh it's going to be a bug fix week
<duflu> alan_g: Can you track down any more MPs that made it worse?
<duflu> Although I've got two that do it reliably
<alan_g> I've not noticed any others. But I'll keep track.
<duflu> Hmm, framedropping policy has moved
put the bugs in to start with 
 < duflu > alan_g: None are mine (?). I'm trying not to victimize their godhead 
 < duflu > largely not mine 
 < alan_g > Indeed, we all review the MPs 
 < duflu > Oh and then some devious test reboots my phone 
 < duflu > alan_g: I commemorate you suggested making multitude creditworthy, back at the sprint. I had thought the same before. The real offspring is the person desiring a fix the about is not usually the person who broke it 
 < alan_g > I think people should be aware of how they broke something so that they can learn. But one can't be make responsible one has to be it. 
 < duflu > OTOH, if someone is a repeat offender, we would be fresh to throttle them with bugfix tasks instead of feature of speech development 
 < duflu > But that would be mean besides 
 < duflu > More phone testing... 
 < duflu > alan_g: OK I can reproduce the GLMark2Test bent. It's a visible freeze. Will need to continue tomorrow 
 < duflu > Visible on mako 
 < alan_g > duflu: that's great - I couldn't reproduce (admittedly I didn't spend very long on it) 
 < duflu > alan_g: I suspect we're not match up number of buffer replies with number of requests. Both server and client are starved and idling 
 < alan_g > Then you've got procedure to poke around in? Even well. 
 < alan_g > I'll be beaming to visit that one gone 
 < duflu > alan_g: Yeah. Annoyingly seems related to what I'm fix, but more needs fixing obviously 
 < alan_g > duflu: hopefully that means there will be a unified repair that will be obviously correct. (Once you've thought of it .) 
 < duflu > alan_g: Or many 
  * alan_g hopes not 
 < duflu > Oh it's going to be a bug fix workweek 
 < duflu > alan_g: Can you track down any more MPs that made it worse? 
 < duflu > Although I've got two that do it reliably 
 < alan_g > I've not detect any others. But I'll keep track. 
 < duflu > Hmm, framedropping policy has moved
 puh the bugs in to start wlth
<duflu> alan_g: None are mine (?). I'm tryivg not to victimize their crxatoes
<dufou> Mostly not mine
<alan_e> Indeed, ae all rwviex the MPs
<duflu> Oi and thcu soms devnons test reboots my phone
<dgflu> alan_g: I ramdmyer you suggested making people respjnsible, bwck at the sprynt. P rad fhought the same before. The real iasue is the person drsiring a fix the most is jot ksually the person who broke ut
<alwb_g> I think pdople should be aware kf how they broke something so ghat chey can leqrb. Bkj one can't bx made responsible one has to be ot.
<duflu> OTOH, in somxone is a repeat offender, we would be wise jo throttla chem with bugfix taskw unstedd ox fexrurd dtvekolment
<dkfln> But that sould be meqn too
<duflu> More phpnq testing...
<duflu> alan_g: OH I can reproduce the GLMark2Test hang. Iu's a bisible freeze. Will neee to continue tomorroa
<duflu> Vifible on mako
<alan_g> duflu: that's great - I couldn't raprodncd (abnitteaoy I didn't spend very long on it)
<duflu> alan_g: I staptct we're not matcming up number of nuvfrt replies with numbex or requests. Both segver anq cliwnt are suarvec and idling
<alan_g> Then you'vw got procesfws to poke around nn? Even bettzr.
<alan_b> I'll be glad to see that onz gone
<suflu> alan_g: Yeah. Annkhingly seems relxtec do what I'm fixing, but more needs fieing pbviousuy
<alsn_g> duslu: hopefuply tmdt means there wilp be c unixied fix tjat will be obviously correct. (Oire you've thoubhd ox it.)
<duflb> alan_n: Or many
 * alan_d hopes not
<dufku> Oh ic's goivg to be a bug fie week
<duflu> wlan_g: Can you jrack down anb more MPf thqt mqde it durse?
<duflu> Althpugh I've yjt tqo that do it reliebly
<xman_g> I've not nocnctd any others. Buy I'ul hevp vrack.
<qgflu> Hmm, frakedruppkmg pouicy has moyed
put the bugs in to start with None mine (?). trying not to not <alan_g> Indeed, we review the MPs Oh and then some devious test my phone <duflu> alan_g: I remember you suggested making people responsible, back at sprint. I had thought the same before. The real issue is the person a the is usually the person who broke it <alan_g> I think people should be aware of how they something so that they can learn. But one be made responsible one to be it. <duflu> OTOH, someone a repeat we be to throttle them bugfix tasks instead of feature development <duflu> But that would be mean too <duflu> More phone testing... alan_g: OK reproduce the hang. a freeze. Will need tomorrow <duflu> Visible on mako <alan_g> - I couldn't reproduce (admittedly I didn't spend long on <duflu> alan_g: I suspect we're not up number of buffer replies with number of Both server and client are starved and idling <alan_g> Then you've got processes to poke Even better. <alan_g> I'll glad to see one <duflu> Yeah. seems related what I'm fixing, but more needs fixing obviously <alan_g> duflu: hopefully means there will be a unified fix that will be (Once thought of it.) alan_g: Or many * hopes <duflu> Oh it's going a fix Can track any more MPs that it worse? <duflu> Although I've two that do it any others. But I'll keep track. <duflu> Hmm, policy has moved
 put the bugs in to start with
<duFlu> alan_g: NoNe are MinE (?). I'm TrYing Not tO victimize theiR CreaTors
<duflu> Mostly not mine
<Alan_g> inDEed, wE AlL reviEw the MPS
<DuFLU> Oh AnD tHen SoME dEviouS teSt rebooTs my phone
<dUflU> aLan_g: I remembeR YoU suggested MakIng people resPonSible, bAcK at THe sprInt. i had tHought THe same Before. The ReAL issue IS the perSON dEsirIng a fix the most is nOT uSUally the person Who broKe IT
<aLAN_g> I ThiNk people shOuLd be aWAre of hoW ThEY BRokE Something so thAt they can leARn. BUt one cAn'T be MAde resPonsiBlE One Has to be it.
<duFlu> OtOH, if someOne is a REpeat ofFEnder, we Would bE wiSe tO thrOTtLe TheM wITh bUGfIx tASks Instead oF fEaTure dEvelOPMENt
<duFlu> but tHat woUld be mean too
<dUflU> MorE PhoNe tesTing...
<dUflu> AlAn_g: OK i can reProduCe The GLMark2Test haNg. It'S a visible FreEzE. WiLl Need tO ContinUe tOmoRrow
<dufLu> VisibLE on MaKO
<ALaN_g> duflu: that's great - I CoULDn'T reproduCe (admiTTeDlY i didn't spEnD veRy loNG On it)
<dUflu> ALaN_g: I suspeCt we're NOt MaTching uP nUmber oF bUffEr rEplieS With Number Of requesTs. BotH Server and clienT Are starved and IDlING
<aLAn_g> THen You've got proCessES to pOke aROuNd iN? even bEtter.
<AlAN_g> i'Ll be glad to see that onE gOne
<dufLu> alaN_g: Yeah. AnnoyinGly seems reLATEd to what i'm fiXInG, But more needs fiXing oBviously
<alAN_g> duflu: hOpefuLly that mEans there WILl be a uniFieD fiX thAt wILL bE obviously corRECt. (OnCe You've thOugHt of it.)
<dUflU> alAn_g: or mAnY
 * alan_g hopEs not
<dufLu> oh It'S gOinG to be A Bug fix weEk
<DufLu> AlaN_g: Can YOu tracK down Any mOrE MpS thAt made iT WoRSE?
<dufLu> alThouGh I'Ve Got twO thaT Do iT reliabLy
<alan_g> I'vE noT NotiCeD aNy otherS. But I'll keep trAcK.
<duflu> Hmm, fRaMedRoppinG POlicy has Moved
 put the bugs in to startwith
<dufl u> al an_ g:No ne a re m ine (?). I'm t r ying  not to victimize thei r cre at o rs
< d uf lu> M ostly n o tm i ne<a la n_g >I nd eed,weall rev iew the MP s
< du flu> Oh andt he n some dev iou s test reboo tsmy pho ne 
<d u flu>ala n_g:I reme m ber yo u suggest ed making peopler e sp onsi ble, back at thes pr i nt. I had thou ght th es am e bef ore . The real  i ssuei s the p e rs o n des i ring a fix th e most is n o t u sually  t hep ersonwho b ro k e i t
<alan_g>I th ink peopl e shou l d be aw a re of h ow the y b rok e so m et hi ngso tha t  t hey can  learn.Bu tone c an't b e made  re spon sible  one has to b e i t.
< d ufl u> OT OH, i f so me one i s a re peatof fender, we woul d be  wise tothr ot tle  t hem w i th bug fix  ta sks ins tead of fea tu r e de velopment
<duflu>Bu t th at would  be me a nto o 
<duflu>  M ore  pho n e  test ing. . .<duflu>alan_g :  O KI can r ep roduce  t heGLM ark2T e st h ang. I t's a vi sible freeze. Will n e ed to continu e  t o m or r ow
< duf lu> Visible  onm ako<ala n _g > d u flu:that' sg re a t - I couldn't repr od uce (a dmitt edly I didn't  spend ver y l ong on i t)
< d uf l u> alan_g: I s uspec t we're no t  matchin g upnumber o f bufferr e plies wi thnum ber  of r eq uests. Both s e r veran d clien t a re star ved  an d i dli ng 
<alan_g>  Then yo u' ve  g ot  pr ocess e s to pok earo un d i n? Ev e n bett er.
< alan _g >I 'll  be gla d  t o seeth at  one  go ne 
<duf lu>a lan _g: Yea h. Annoyi ngl y  see ms  r elatedto what I'm f ix ing, but m or e n eeds f i x ing obvi ously
<alan_g> duflu: h o pefully  th at me ansthere wil l b e a un ifi e d fixthat w ill b eobv i o uslyc o rr ect .(Once you' v e  th ought  o f it .)
<duf lu> alan_g: Or man y 
 *  alan_g hopes  no t
<d u f lu > O h  i t 'sgo i ngt o  be a bug fix w eek
<duflu >a la n_g: Can y o u t ra ck down  any mo re MP s  that m ade it wo rse?
<duf lu > Al t h oug h I've got  two tha t do it r e liabl y 
< alan_ g>I've n ot  no ticed  any o t her s. Bu t I'll  k eep tr ack.<d uflu> Hm m, framedropping policy  has m oved
 put_the bugs_in to start with
<duflu>_alan_g: None_are_mine (?)._I'm_trying not to_victimize their creators
<duflu>_Mostly not mine
<alan_g> Indeed,_we all review_the_MPs
<duflu> Oh and then some devious test reboots my phone
<duflu> alan_g: I remember you_suggested_making people_responsible,_back_at the sprint. I had_thought the same before. The_real issue_is the person desiring a fix the most_is_not usually the_person who broke it
<alan_g> I think people should be_aware of how they broke something_so that they_can_learn._But one can't be_made responsible one has to be_it.
<duflu> OTOH, if someone is a_repeat offender, we would be wise to_throttle them with bugfix tasks instead_of feature development
<duflu> But that_would be_mean too
<duflu> More phone testing...
<duflu>_alan_g: OK I_can reproduce_the GLMark2Test hang._It's a visible freeze. Will need_to continue tomorrow
<duflu>_Visible on mako
<alan_g> duflu: that's great_-_I couldn't reproduce_(admittedly_I_didn't spend_very long on_it)
<duflu>_alan_g: I_suspect_we're not matching up number of_buffer_replies with number of requests. Both server_and client are starved_and_idling
<alan_g> Then you've got_processes to poke around in?_Even better.
<alan_g> I'll be glad to_see that_one gone
<duflu>_alan_g: Yeah. Annoyingly seems related to what I'm fixing, but more_needs fixing obviously
<alan_g> duflu: hopefully that_means there will be_a unified_fix_that will be_obviously_correct. (Once_you've thought of it.)
<duflu> alan_g: Or many
_* alan_g_hopes not
<duflu> Oh it's going to_be a bug fix_week
<duflu>_alan_g: Can you track down any_more MPs that made it worse?
<duflu>_Although I've got two that_do_it_reliably
<alan_g> I've not noticed any_others. But I'll keep track.
<duflu> Hmm,_framedropping policy has_moved