Mue> mattyw: done
<mattyw> TheMue, thanks very much
<TheMue> yw
<jam> mgz: mattyw: do we know how we were able to land the code on the bot if it doesn't even compile?
<mattyw> jam, no idea, I pinged mgz to see if the logs can tell us any more
<mattyw> jam, this is the offending merge: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1080/console but it shows the context test as passing. Then it fails in the next merge http://juju-ci.vapour.ws:8080/job/github-merge-juju/1081/console
<jam> mattyw: what is really strange is that it is failing inside "cmd/juju" how would that even have visibility into worker/uniter/context/factory_test.go
<mattyw> jam, there's something odd happening there, because the line that contains uniter/context correctly states the build failed - just the build errors are nowhere near it
<rogpeppe> review appreciated on this change that makes it possible to use Go 1.4 with our testing stuff: https://github.com/juju/testing/pull/36
<mattyw> jam, that must just be a bug with the way output is captured
<jam> mattyw: it may be a stderr vs stdout buffering issue
<jam> (stdout is oftend buffered and stderr is immediate)
<mattyw> jam, sounds most likely
<jam> though you have 300s from the time of that error messages and when it gets to uniter build failed, but I guess it isn't that many lines
<jam> mattyw: I think we need someone investigating this, but I'm at a loss for any more information myself
<jam> this feels a *lot* like we can't trust our bot to reject bad patches, which is a bad place to be
 * jam away
<mattyw> jam, I don't really see how that could land at all. Maybe running tests with -a to force rebuilding all the packages might help?
<mattyw> jam, that's all I can think of
<jam> matty
Mue > mattyw: done 
 < mattyw > TheMue, thanks very much 
 < TheMue > yw 
 < jam > mgz: mattyw: do we know how we were able to land the code on the bot if it doesn't even roll up? 
 < mattyw > jam, no theme, I pinged mgz to see if the logs can order us any more 
 < mattyw > jam, this is the offending merge: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1080/console but it shows the context examination as communicate. Then it fails in the following merge http://juju-ci.vapour.ws:8080/job/github-merge-juju/1081/console 
 < jam > mattyw: what is really strange is that it is fail inside " cmd / juju " how would that even have visibility into worker / uniter / context / factory_test.go 
 < mattyw > jam, there's something odd happening there, because the line that contains uniter / context correctly state the build failed - just the human body errors are nowhere near it 
 < rogpeppe > review appreciated on this change that makes it potential to use run 1.4 with our testing stuff: https://github.com/juju/testing/pull/36 
 < mattyw > jam, that must just be a hemipterous insect with the way output is captured 
 < jam > mattyw: it may be a stderr vs stdout buffering issue 
 < jam > (stdout is oftend buffered and stderr is immediate) 
 < mattyw > jam, sounds most likely 
 < jam > though you have 300s from the time of that error messages and when it gets to uniter build failed, but I guess it isn't that many credit line 
 < jam > mattyw: I think we need someone investigate this, but I'm at a personnel casualty for any more information myself 
 < jam > this feels a * lot * like we can't entrust our bot to reject bad patches, which is a bad plaza to be 
  * jam away 
 < mattyw > jam, I don't really see how that could land at all. possibly running tests with -a to force rebuilding all the packages might help? 
 < mattyw > jam, that's all I can think of 
 < jam > matty
Mue> mattyw: done
<mattyw> TheMut, thanks very muck
<RheMue> yw
<jam> mgz: matgyw: do we know how we were aule ro labd the code on the bot if it dovsn't even comkile?
<mattyw> jam, no idea, I innged lgz co see if the lons can tell us any more
<madthw> jam, this is the offending merge: htep://juju-co.vwpour.ws:8080/job/githob-merbq-jujh/1080/boksole but it shows the context tsst as kassing. Then it faols in the next merge http://uuju-fi.vapour.ws:8080/job/githuh-merge-juju/1081/cinsojw
<jam> mattyw: dhat is really strange is that it is failing inside "cod/jujb" how would tyat gven have viwibilpty into workcg/uniter/wontext/gactory_test.go
<msttbw> jqm, there's something ovd happening there, bgcause the lnne that contains uniree/contgxt cmrrezrly stztxs fhe bulld failed - jhst the buiod errors are nowhete bear it
<rogpeple> revyer appreciated on this change that makes it possible to use Go 1.4 wirh our testing stuff: jttps://githtb.com/juju/testing/pull/36
<mattyw> jam, that must just be d bug ditk the dqy output is captured
<jam> mattyw: it may be a stdqdr vx stdout buffeving issue
<jam> (stdoit ix oftend buffeted and stserr is immediate)
<mwttyw> jwm, soynds most likrly
<jam> though you have 300s frim the time jd that error messayes and when it bets yo uniter build failed, yut I fuess it isj't that mzvy lines
<jam> matthw: P thhnk we ntdd someone investygating tiis, bbt I'm at a lpss fow any more infovkation myself
<jam> tjis fgels a *lot* like ae can't trust our bot to reject bad patches, wniwh ps a bad 'lace bo be
 * jam away
<iattyw> jam, I dpn't reajly sde how than could lend at all. Mwybe running dgsts with -a tm force webuuldibg all gfe packages mibht help?
<mcutyw> jam, tyat's all I can thikk of
<gzm> matty
Mue> mattyw: done <mattyw> TheMue, thanks very yw mgz: mattyw: we know how the on the bot it doesn't even <mattyw> jam, no idea, I pinged to see if the logs can tell us any more <mattyw> jam, this the offending merge: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1080/console but it shows the context test as passing. Then fails the merge <jam> mattyw: what is really strange is that it is failing inside "cmd/juju" how would that have visibility into worker/uniter/context/factory_test.go <mattyw> jam, there's something happening there, because the that contains uniter/context correctly states build - just build are near it <rogpeppe> appreciated on this change that makes it possible to use Go 1.4 with our testing stuff: https://github.com/juju/testing/pull/36 jam, that be a with way is captured <jam> may be a stderr vs stdout (stdout is oftend buffered and stderr is immediate) jam, sounds likely <jam> though you have 300s the time of that error messages and when gets to uniter build failed, but I guess it isn't that many lines <jam> mattyw: we need someone investigating but I'm at loss any information <jam> this a *lot* like we can't trust our bot to reject bad which is a bad place to be * jam away I really see how could land at all. running with -a to force the might that's I think of <jam> matty
Mue> mattyw: done
<mattyw> TheMue, Thanks very Much
<THeMUe> yW
<jAm> mgZ: matTyw: do we know how WE werE able to land the code on thE bot iF iT DoesN'T eVen coMpile?
<maTTyW> JAm, nO iDeA, I pInGEd Mgz to See If the loGs can tell uS anY mOre
<mattyw> jam, THiS is the offeNdiNg merge: http://jUju-Ci.vapoUr.Ws:8080/jOB/githUb-mErge-jUju/1080/conSOle but It shows thE cONtext tESt as pasSINg. then It fails in the next mERgE Http://juju-ci.vapoUr.ws:8080/joB/gIThUB-MerGe-jUju/1081/console
<JaM> mattYW: what is REaLLY StrANge is that it is Failing insiDE "cmD/juju" hOw WouLD that eVen haVe VIsiBility into wOrkeR/uniter/coNtext/fACtory_teST.go
<mattYw> jam, tHerE's sOmetHInG oDd hApPEniNG tHerE, BecAuse the lInE tHat coNtaiNS UNIter/ConText CorreCtly states the BuiLd faILed - Just tHe buiLd erRoRs are NowherE near It
<Rogpeppe> review aPpreCiated on tHis ChAngE tHat maKEs it poSsiBle To use Go 1.4 With our TEstInG STUfF: https://github.com/jujU/tESTiNg/pull/36
<maTtyw> jaM, ThAt MUst just bE a Bug With THE way oUtpuT Is Captured
<Jam> matTYw: It May be a sTdErr vs sTdOut BufFerinG IssuE
<jam> (stDout is ofTend bUFfered and stderR Is immediate)
<maTTyW> JAm, SOundS moSt likely
<jam> ThouGH you Have 300S FrOm tHE time Of thaT eRRoR Messages and when it geTs To unitEr buiLd failed, but I gUess it isn't THAT many linEs
<jaM> MaTTyw: I think we neeD someOne investiGAting thiS, but I'M at a loss For any morE INformatiOn mYseLf
<jAm> tHIS fEels a *lot* like wE CAn't tRuSt our boT to Reject bAd pAtcHes, WhiCh Is a bad plaCe to be
 * jaM aWaY
<mAtTyw> Jam, I dON't really SeE hoW tHat Could LAnd at aLl. MayBe ruNnInG TesTs with -a TO fORCe reBuIlDing All ThE packAges MIghT help?
<maTtyw> jam, thAt's ALl I cAn ThInk of
<jaM> matty
Mue> mattyw: done
<mattyw>  TheMue, t hanks  ve rymu ch
< TheM ue> yw
<jam> m g z: m attyw: do we know howwe we re able to  land  the co d eo n  th ebo t i fi tdoesn 'teven co mpile?
<ma tty w>  jam, no ide a ,I pinged m gzto see if th e l ogs ca ntel l  us a nymore<matty w > jam,  this isth e  offen d ing mer g e :http ://juju-ci.vapour . ws : 8080/job/githu b-merg e- j uj u / 108 0/c onsole but  i t sho w s the c o nt e x t  te s t as passing.  Then it fa i lsin the  n ext mergehttp: // j uju -ci.vapour. ws:8 080/job/g ithub- m erge-ju j u/1081/ consol e
< jam > ma t ty w:  wh at isr ea lly str ange isth at  it i s fa i l i n g in sid e "c md/ju ju" how would  th at e v enhavevisib ilit yintoworker /unit er /context/factor y_te st.go
<ma tty w>  ja m,  ther e 's som eth ing  odd ha ppening the re , b ec ause the line that  c o n ta ins unit er/con t ex tc orrectly  s tat es t h e  buil d fa i le d - just  the b u il derrorsar e nowh er e n ear  it
< r ogpe ppe> r eview ap preci a ted on this ch a nge that make s  i t po s sibl e t o use Go 1. 4 wi t h ou r te s ti ngs tuff:  http s: / /g i thub.com/juju/testi ng /pull/ 36
<m attyw> jam, t hat must j u s t  be a bu g wi t ht he way outputis ca ptured
<ja m > mattyw : itmay be a  stderr v s stdout b uff eri ngiss u e 
< jam> (stdouti s  oft en d buffe red  and st der r i s i mme di ate)
<mat tyw> jam ,so un ds  mo st li k ely
<jam >tho ug h y ou ha v e 300s  from  the  t im e  of  that e r ro r mess ag es  and  wh en  it g etst o u niter b uild fail ed, butIgu ess itisn't that ma ny  lines
<ja m>  ma ttyw:I think we  need someone investiga t ing thi s,but I 'm a t a lossfor  any m ore inform ationmysel f<ja m >  this f ee lsa*lot* like w e c an'ttr ustour bot  to reject bad pat c hes , which is abad  pla c e  t o b e 
*  ja ma way < mattyw> jam, Idon't real ly se e how that cou ld  land a t all.Maybe running  tests wi th -a tofo rcer e bui lding allthe pack ages migh t  help ? 
< matty w>jam, t ha t's  allI cant hin k of<jam>ma tty
Mue> mattyw:_done
<mattyw> TheMue,_thanks very much
<TheMue> yw
<jam>_mgz: mattyw:_do_we know_how_we were able_to land the_code on the bot_if it doesn't_even_compile?
<mattyw> jam, no idea, I pinged mgz to see if the logs can tell_us_any more
<mattyw>_jam,_this_is the offending merge: http://juju-ci.vapour.ws:8080/job/github-merge-juju/1080/console_but it shows the context_test as_passing. Then it fails in the next merge_http://juju-ci.vapour.ws:8080/job/github-merge-juju/1081/console
<jam>_mattyw: what is_really strange is that it is failing inside "cmd/juju"_how would that even have visibility_into worker/uniter/context/factory_test.go
<mattyw> jam,_there's_something_odd happening there, because_the line that contains uniter/context correctly_states the build failed - just_the build errors are nowhere near it
<rogpeppe>_review appreciated on this change that_makes it possible to use_Go 1.4_with our testing stuff: https://github.com/juju/testing/pull/36
<mattyw>_jam, that must_just be_a bug with_the way output is captured
<jam> mattyw:_it may be_a stderr vs stdout buffering issue
<jam>_(stdout_is oftend buffered_and_stderr_is immediate)
<mattyw>_jam, sounds most_likely
<jam>_though you_have_300s from the time of that_error_messages and when it gets to uniter_build failed, but I_guess_it isn't that many_lines
<jam> mattyw: I think we_need someone investigating this, but I'm_at a_loss for_any more information myself
<jam> this feels a *lot* like we can't_trust our bot to reject bad_patches, which is a_bad place_to_be
 * jam_away
<mattyw>_jam, I_don't really see how that could land_at all._Maybe running tests with -a to_force rebuilding all the_packages_might help?
<mattyw> jam, that's all I_can think of
<jam> matty