 rather than the merged result?
<jam> axw: I have a concern about the merge bot, are you around possibly to discuss?
<axw> jam: I'm here but my wife and kids just got home. I can spare a couple of minutes before I head down
<axw> jam: that when did you see that error? I think I fixed it as a drive by in my PR
<axw> jam: and my PR also removed "stop(c, p)" :)
<axw> so I think that explains that
<axw> jam: linked in the bug, gtg - have a good day
<jam> axw: have a good day. The issue is less about the test failing randomly, and more that the bot seems to be running the test suite against the PR code *rather* than against the merged PR + Develop code
<jam> though maybe you're code landed right in-between run 1 and run 2?
<jam> could be
<balloons> Something weird going on?
<jam> balloons: we've had an intermittent test, and I went to reproduce it, but couldn't get my source tree to line up with the failure lines reported in the merge request
<jam> balloons: but I think I've sorted it out
<balloons> axw, thanks for fixing the vsphere issue, though as you've noted, I still don't know why the DC and vcenter refuse to talk to each other
<jam> Anastasia tried to merge against version X, which failed with intermittent failure. Andrew merged his code which fixed that in passing, then Anastasia landed her code, which now didn't have the failure ethire
<anastasiamac> jam: balloons: thnx for figuring this out \o/
<jam> anastasiamac: well, it seems to be mostly axw doing a driveby fix
<anastasiamac> axw: \o/ (i rescind all previous \o/ on the subject then)
<jam> :,(
<jam> :)
<anastasiamac> jam: but thank you for looking in my absence
<balloons> I just asked a question :-)
<anastasiamac> balloons: and a valid question it was!
<ryebot> I'm trying to bootstrap a controller with strict egress restrictions. I've set up an apt mirror and
rather than the merged result? 
 < jam > axw: I have a business about the merge bot, are you approximately possibly to discuss? 
 < axw > jam: I'm here but my wife and kids barely become home. I can spare a couple of minutes before I head down 
 < axw > jam: that when did you experience that erroneousness? I think I sterilize it as a drive by in my PR 
 < axw > jam: and my public relations also removed " stop(c, phosphorus) " :) 
 < axw > so I think that explains that 
 < axw > jam: connect in the bug, gtg - have a full day 
 < jam > axw: have a good sidereal day. The issue is less about the test fail randomly, and more that the bot appear to be running the examination suite against the PR code * rather * than against the merged public relations + Develop code 
 < jam > though maybe you're code landed right in - between run 1 and run 2? 
 < jam > could be 
 < balloons > Something weird going on? 
 < jam > balloons: we've had an intermittent test, and I went to reproduce it, but couldn't get my source tree to line up with the failure credit line reported in the merge request 
 < jam > balloons: but I intend I've screen it out 
 < balloons > axw, thanks for fixing the vsphere issue, though as you've note, I still don't know why the DC and vcenter refuse to talk to each early 
 < jam > Anastasia tried to merge against version X, which failed with intermittent failure. Andrew merged his code which fixed that in passing, then Anastasia landed her code, which now didn't have the failure ethire 
 < anastasiamac > jam: balloon: thnx for figuring this out \o/ 
 < jam > anastasiamac: well, it look to be mostly axw doing a driveby fix 
 < anastasiamac > axw: \o/ (i rescind all previous \o/ on the national then) 
 < jam >: , (
 < jam > :) 
 < anastasiamac > jam: but thank you for looking in my absence 
 < balloons > I just ask a question :-) 
 < anastasiamac > balloons: and a valid question it was! 
 < ryebot > I'm trying to bootstrap a restrainer with strict egress restriction. I've set up an apposite mirror and
 rahher than the merged resmlt?
<jam> axw: I havg q concxrn aboht the mdrge bot, are you around possmbly to duscuss?
<axw> jam: I'm here cut my wive and kuds oust got home. I rzn sparc a ckmple mh minutes beforg I head dowt
<axw> jam: that fhdn did you see that error? I think I fyxed it ad a drive by ig my [R
<axs> jam: and my PR also removed "stop(c, p)" :)
<axw> vo I think thst explains that
<axw> jam: lijked in the bug, gtg - hwve a good eay
<jwn> axw: have a good day. Uhz issue is mess about the test failing ranaomly, and more jkqt hve bot seemw to fe running tmv test vuite abainst the PR gode *cathwr* than against the mxrged PR + Develop coqe
<jam> thoggk maybe you're code labdwd richt hn-begqeev rhn 1 znd ruj 2?
<jem> could be
<galloons> Sonething weird going og?
<ham> balloons: se've hwd an intermittent test, and I went to repgodude it, but couldn't get mt source tree to line up with ehe failure lines reported in the merge request
<jak> balmuonw: nut K tjink I've sorted it out
<balloons> axw, thanks for ricikg the vsphere ifsue, though ad uju've noted, I rtill bkn'f know why the DC wnd vcegter eefuse to tall to each other
<jam> Anastasiq tried to mvrge against version X, which failzd witn intrrmittent failure. Andrec mergsd his code which fisdd that in passivg, nhen Anastasia landed her code, which nox didu't have ghe gailurq ethire
<anwstasldmac> jam: balloons: hhnx yor fhguring thls out \o/
<jam> anastasiamac: well, iv seems to be mmstny axw djing s driveby fix
<wnastasiamac> arw: \o/ (i rzscind all previkus \o/ oi the subjece then)
<jam> :,(
<jam> :)
<wnastasiamac> jam: but thabk yiu for uuoking in my ansence
<balloons> I juwt asked a questiok :-)
<anarfasiamac> balloour: and a valid qurstkon in wes!
<ryefmt> I'm trying to coogxtrap a controllcr dith strict egress restrhctikns. I've set up an spb mirror qnd
rather than the merged result? <jam> axw: a about the bot, are you jam: here but my and kids just home. I can spare a couple minutes before I head down <axw> jam: that when did you see that I think I fixed it as a drive by in my PR <axw> and PR removed p)" :) <axw> so I think that explains that <axw> jam: linked in the bug, gtg have a good day <jam> axw: have a day. The issue is about the test failing randomly, more the bot to running test suite against PR code *rather* than against the merged PR + Develop code <jam> though maybe you're code landed in-between run run 2? could <balloons> weird going on? we've had an intermittent test, and reproduce it, but couldn't get my source tree line up the failure lines reported in the request <jam> balloons: but I think I've sorted out <balloons> axw, thanks for fixing the vsphere issue, though as you've noted, I still why the DC and refuse to talk each <jam> tried merge against X, which failed with intermittent failure. Andrew merged his code which that in passing, then Anastasia landed her code, which now the ethire <anastasiamac> jam: thnx for figuring this \o/ anastasiamac: well, it seems mostly doing <anastasiamac> \o/ rescind all previous \o/ the subject then) <jam> :,( :) <anastasiamac> jam: but my absence <balloons> I just asked a question <anastasiamac> balloons: and a valid question it <ryebot> I'm trying to bootstrap a controller with strict egress restrictions. I've up an and
 rather than the merged result?
<Jam> axw: I havE a conCerN abOuT the MergE bot, are you arouND posSibly to discuss?
<axw> jam: I'm Here bUt MY wifE AnD kids Just got HOmE. i Can SpArE a cOuPLe Of minUteS before i head down
<aXw> jAm: That when did yOU sEe that erroR? I tHink I fixed it As a Drive bY iN my pr
<axw> jAm: aNd my Pr also rEMoved "sTop(c, p)" :)
<axw> sO I THink thAT explaiNS ThAt
<axW> jam: linked in the buG, GtG - Have a good day
<jaM> axw: haVe A GoOD Day. the Issue is lesS aBout tHE test faILiNG RAndOMly, and more thaT the bot seemS To bE runniNg The TEst suiTe agaInST thE PR code *rathEr* thAn against The merGEd PR + DevELop code
<Jam> thoUgh MayBe yoU'Re CoDe lAnDEd rIGhT in-BEtwEen run 1 anD rUn 2?
<Jam> coUld bE
<BALLoonS> SoMethIng weIrd going on?
<jam> BalLoonS: We'vE had aN inteRmitTeNt tesT, and I wEnt to ReProduce it, but couLdn't Get my sourCe tReE to LiNe up wITh the fAilUre Lines rePorted iN The MeRGE ReQuest
<jam> balloons: buT I THInK I've sortEd it ouT
<BaLlOOns> axw, thAnKs fOr fiXINg the VsphERe Issue, thoUgh as yOU'vE nOted, I stIlL don't kNoW whY thE DC anD VcenTer refUse to talK to eaCH other
<jam> AnastASia tried to merGE aGAInST verSioN X, which failEd wiTH intErmiTTeNt fAIlure. andreW mERgED his code which fixed tHaT in pasSing, tHen Anastasia lAnded her coDE, WHich now dIdn't HAvE The failure ethiRe
<anaStasiamac> jAM: balloonS: thnx For figurIng this ouT \O/
<Jam> anastAsiAmaC: weLl, iT SEeMs to be mostly aXW DoinG a Driveby Fix
<AnastasIamAc> aXw: \o/ (I reScInd all preVious \o/ on ThE sUbJeCt tHen)
<jaM> :,(
<Jam> :)
<anastAsIamAc> Jam: But thANk you fOr looKing In My ABseNce
<ballOOnS> i Just AsKeD a quEstIoN :-)
<anasTasiAMac> BalloonS: and a valiD quEStioN iT wAs!
<ryeboT> I'm trying to boOtStrap a contRoLleR with sTRIct egresS restrictions. I've set up an APt mirroR anD
 rather than the merged re sult?
<jam > axw : I  ha ve  a c once rn about the m e rgebot, are you around po ssibl yt o di s cu ss?
< axw> ja m :I ' m h er ebut  m y  w ife a ndkids ju st got hom e.Ican spare ac ou ple of min ute s before I h ead  down<a xw> jam:tha t whe n didy ou see  that err or ?  I thi n k I fix e d  i t as  a drive by in my PR <axw> jam: and  my PR  a l so r emo ved  "stop(c,p) " :)< axw> so It h i nkt hat explainsthat
<axw>j am:  linke dint he bug , gtg  - hav e a good da y
<j am> axw:have a good da y . The i ssue i s l ess  abo u tth e t es t  fa i li ngr and omly, an dmo re th at t h e b ot s eem s to  be r unning the te stsuit e  ag ainst  thePR c od e *ra ther*thanag ainst the merge d PR  + Develo p c od e
< ja m> th o ugh ma ybe  yo u're co de land e d r ig h t in -between run 1 and  r u n  2 ?
<jam>couldb e<b a lloons>So met hing w eirdgoin g  o n?
<jam>  ballo o ns :we've h ad  an in te rmi tte nt te s t, a nd I w ent to r eprod u ce it, but cou l dn't get my s o ur c e  t r ee t o l ine up with  the fail urel in esr eport ed in  t h em erge request
<jam>ba lloons : but  I think I've  sorted it o u t
<ballo ons> ax w , thanks for f ixing  the vsphe r e issue,  thou gh as yo u've note d ,  I still  do n't  kn oww h ythe DC and vc e n terre fuse to  ta lk to e ach  ot her 
<j am > Anastas ia tried  t ome rg e a gains t  version  X , w hi chfaile d  withinter mitt en tf ail ure. An d re w merg ed  h is c ode  w hichfixe d  th at in p assing, t hen Anas ta si a lande d her code, w hi ch now did n' t h ave th e failureethire
<anastasiamac> j a m: ball oon s: th nx f or figuri ngthis o ut\ o/
<ja m> ana stasi am ac: w ell,i t  s eem sto be most l y  ax w doi ng  a d rivebyfix
<anastasiamac> axw : \o/ (i resc ind  all p re vio u s\ o/on the s ubject then)
<j am> :,(
<j am >  : )
<anastas i ama c>  jam: b ut than k you for loo king in m y absence 
< ball o o ns>  I just as ked a qu estion :- ) 
<ana s ta siama c>balloo ns : a nd avalidq ues tionit was !<ryebo t> I' mtrying t o bootstrap a controlle r with  stri ctegress re str i cti ons. I've  set  up an apt  mi rro r and 
 rather_than the_merged result?
<jam> axw: I_have a_concern_about the_merge_bot, are you_around possibly to_discuss?
<axw> jam: I'm here_but my wife_and_kids just got home. I can spare a couple of minutes before I head_down
<axw>_jam: that_when_did_you see that error? I_think I fixed it as_a drive_by in my PR
<axw> jam: and my PR_also_removed "stop(c, p)"_:)
<axw> so I think that explains that
<axw> jam: linked_in the bug, gtg - have_a good day
<jam>_axw:_have_a good day. The_issue is less about the test_failing randomly, and more that the_bot seems to be running the test_suite against the PR code *rather*_than against the merged PR_+ Develop_code
<jam> though maybe you're code_landed right in-between_run 1_and run 2?
<jam>_could be
<balloons> Something weird going on?
<jam>_balloons: we've had_an intermittent test, and I went_to_reproduce it, but_couldn't_get_my source_tree to line_up_with the_failure_lines reported in the merge request
<jam>_balloons:_but I think I've sorted it out
<balloons>_axw, thanks for fixing_the_vsphere issue, though as_you've noted, I still don't_know why the DC and vcenter_refuse to_talk to_each other
<jam> Anastasia tried to merge against version X, which failed_with intermittent failure. Andrew merged his_code which fixed that_in passing,_then_Anastasia landed her_code,_which now_didn't have the failure ethire
<anastasiamac> jam: balloons:_thnx for_figuring this out \o/
<jam> anastasiamac: well,_it seems to be_mostly_axw doing a driveby fix
<anastasiamac> axw:_\o/ (i rescind all previous \o/_on the subject then)
<jam> :,(
<jam>_:)
<anastasiamac>_jam:_but thank you for looking_in my absence
<balloons> I just asked_a question :-)
<anastasiamac>_balloons: and a valid question it was!
<ryebot>_I'm_trying to bootstrap a controller with_strict_egress restrictions. I've set up an_apt_mirror_and