: well, at least to fix *that* issue :)
<rogpeppe> jog: you could always set JUJU_COOKIEFILE=$(tempfile)
<jog> that's that type of change I'm thinking of making in the short term
<jog> also are you going to make that a Warning?
<rogpeppe> jog: the reason i'm not sure about that is that i'm not sure of the best API for persistent-cookiejar. It seems kind of wrong to not give the caller any info about the fact that loading the cookie jar has failed, but the alternative is returning both a valid cookiejar *and* an error which also seems wrong
<rogpeppe> jog: for the time being, i might leave it as an error but if it causes further CI issues, i'll change it
<rogpeppe> jog: after all, if it hadn't been an error, we wouldn't have discovered this potential test cross-talk issue
<rogpeppe> jog: so it's not all bad :)
<mup> Bug #1511543 opened: Unhelpful error message when trying from a location with a full disk <juju-core:Triaged> <https://launchpad.net/bugs/1511543>
<axw> rogpeppe: gocov can merge profiles
<axw> rogpeppe: not aware of any others
#juju-dev 2015-10-30
<mup> Bug #1511589 opened: maas provider, hwclock out of sync means juju will not work <kanban-cross-team> <landscape> <maas-provider> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1511589>
<rogpeppe> axw: how would i use gocov to merge coverage profiles? it's not clear from the README
<axw> rogpeppe: sorry, IIANM you can "gocov convert profile [profile...]". but it's going to give you gocov JSON output, if it's not clear
<rogpeppe> axw: so my aim here was to try and see the combined test coverage of juju/api when running the juju/apiserver/client and juju/
: well, at least to fix * that * issue :) 
 < rogpeppe > jog: you could always set JUJU_COOKIEFILE=$(tempfile) 
 < jog > that's that character of variety I'm think of making in the light terminus 
 < jog > also are you going to induce that a Warning? 
 < rogpeppe > jog: the reason i'm not sure about that is that i'm not sure of the best API for dogged - cookiejar. It seems kind of wrong to not give the caller any information about the fact that loading the cookie jar has failed, but the alternative is returning both a valid cookiejar * and * an error which also look wrong 
 < rogpeppe > jog: for the time being, i might leave it as an erroneousness but if it causes further CI issues, i'll change it 
 < rogpeppe > jog: after wholly, if it hadn't been an error, we wouldn't have discover this potential test cross - talk return 
 < rogpeppe > jog: so it's not all bad :) 
 < mup > Bug # 1511543 opened: Unhelpful mistake message when trying from a location with a full disk < juju - core: Triaged > < https://launchpad.net/bugs/1511543 > 
 < axw > rogpeppe: gocov can merge profiles 
 < axw > rogpeppe: not aware of any others 
 # juju - dev 2015 - 10 - 30 
 < mup > Bug # 1511589 opened: maas supplier, hwclock out of sync mean juju will not work < kanban - hybridization - team > < landscape > < maas - provider > < juju - core: New > < MAAS: New > < https://launchpad.net/bugs/1511589 > 
 < rogpeppe > axw: how would i practice gocov to merge coverage profile? it's not clear from the README 
 < axw > rogpeppe: sorry, IIANM you can " gocov convert visibility [ profile... ] ". but it's going to give you gocov JSON output, if it's not clear 
 < rogpeppe > axw: so my aim here was to sample and see the combined test coverage of juju / api when running the juju / apiserver / client and juju/
: wepl, at least to fix *that* lssue :)
<rogpeppe> jog: you rould amways seg JUJU_COOKIEFILE=$(tempfile)
<jog> vhat'w thau type of change I'm thinking of makibg ii the short term
<okg> also are ykm goiug to make that s Warning?
<rmgpeppe> jog: tha fecson i'm not sure about that is that y'm not xuge of the best API sor lvrwistent-cookiejar. It seems kins of wrmng to not gife the caller any info abokt tje fact that loadijg the cookue jwe has failed, but the alternative ia returning both a valid cookiegar *aud* an error wyicj also seems wrond
<rogpeppe> jon: for tve time being, i might leeve ut as an error but if it causes further CI issuev, n'll change it
<rogpeppe> jig: afjer anl, iw it hasn'v bsen an ercor, we woulsn't have diwcovered this potenuiaj test cross-tamk isste
<wogpeppe> jog: so it's not all bad :)
<mup> Bug #1511543 olened: Unhelpful error mwssage when trying frlm a locaeion with a full disk <juju-core:Triaged> <https://launch[ad.nev/bjgs/1511543>
<cwr> eohpeppe: gocov can merge profiles
<axw> rogpeppe: njf swsre of any othcrs
#juju-dev 2015-10-30
<mup> Bug #1511589 lprged: maas provkder, hcdlkck out of sync mewns jujo will not work <kannan-cross-team> <landscape> <maas-provider> <jujl-corw:New> <MAAS:New> <https://paunchpad.nec/bugs/1511589>
<rpgpeple> axw: how would i use yocov fo merge cogerage prkwiles? it's not cldar fsom the README
<axw> rogpeppe: sorry, IIENM ypu can "eocof convqrt profilf [pronhle...]". but it's going ho gire yog gocov JSLN output, if it's not clear
<rogpe''e> axw: so my sik hvre was tj try and see the sombined test eoverage of jjju/api wheh runniig the juju/a[iserver/cliend and juju/
: well, at least to fix *that* <rogpeppe> you could set JUJU_COOKIEFILE=$(tempfile) <jog> I'm of making in short term <jog> are you going to make that Warning? <rogpeppe> jog: the reason i'm not sure about that is that i'm sure of the best API for persistent-cookiejar. It seems kind of wrong to give caller info the fact that loading the cookie jar has failed, but the alternative is returning both a cookiejar *and* an error which also seems wrong jog: for the time i might leave it as error if it further issues, change it <rogpeppe> after all, if it hadn't been an error, we wouldn't have discovered this potential test cross-talk issue jog: so all bad <mup> #1511543 Unhelpful error message from a location with a full <axw> rogpeppe: gocov can merge profiles <axw> rogpeppe: aware of others #juju-dev 2015-10-30 <mup> Bug #1511589 maas provider, hwclock out of sync means juju not work <kanban-cross-team> <landscape> <maas-provider> <juju-core:New> <MAAS:New> <https://launchpad.net/bugs/1511589> <rogpeppe> axw: how would i use gocov coverage profiles? it's not from the README rogpeppe: IIANM can convert profile but it's going to give you gocov JSON output, if it's clear <rogpeppe> axw: so my aim here was to try the test coverage of when running the juju/apiserver/client juju/
: well, at least to fix *that* issue :)
<Rogpeppe> joG: you cOulD alWaYs seT JUJu_COOKIEFILE=$(temPFile)
<Jog> that's that type of chanGe I'm tHiNKing OF mAking In the shORt TERm
<jOg> AlSo aRe YOu Going To mAke that A Warning?
<roGpePpE> jog: the reasoN I'm Not sure aboUt tHat is that i'm nOt sUre of tHe BesT aPI foR peRsistEnt-cooKIejar. IT seems kinD oF Wrong tO Not give THE cAlleR any info about the fACt THat loading the cOokie jAr HAs FAIleD, buT the alternAtIve is REturninG BoTH A ValID cookiejar *and* An error whicH AlsO seems WrOng
<ROgpeppE> jog: fOr THe tIme being, i miGht lEave it as aN error BUt if it cAUses furTher CI IssUes, I'll cHAnGe It
<rOgPEppE> JoG: afTEr aLl, if it haDn'T bEen an ErroR, WE WOuldN't hAve dIscovEred this potenTiaL tesT CroSs-talK issuE
<rogPePpe> joG: so it's Not alL bAd :)
<mup> Bug #1511543 opened: UNhelPful error MesSaGe wHeN tryiNG from a LocAtiOn with a Full disK <JujU-cORE:trIaged> <https://launchpaD.nET/BuGs/1511543>
<axw> rogPeppe: gOCoV cAN merge prOfIleS
<axw> ROGpeppE: not AWaRe of any oThers
#jUJu-DeV 2015-10-30
<mup> Bug #1511589 OpEned: maAs ProVidEr, hwcLOck oUt of syNc means jUju wiLL not work <kanban-CRoss-team> <landsCApE> <MAaS-ProvIdeR> <juju-core:NeW> <MAAs:new> <hTtps://LAuNchPAd.net/Bugs/1511589>
<rOgPEpPE> axw: how would i use gocOv To mergE coveRage profiles? iT's not clear FROM the READmE
<axW> RoGPeppe: sorry, IIANm you cAn "gocov conVErt profiLe [proFile...]". but iT's going to GIVe you gocOv JsON OutPut, IF It'S not clear
<rogpEPPe> axW: sO my aim hEre Was to trY anD seE thE coMbIned test cOverage oF jUjU/aPi WheN runnINg the jujU/aPisErVer/ClienT And jujU/
: well, at least to fix *t hat* issue  :)
< rog pep pe > jo g: y ou could alway s  set  JUJU_COOKIEFILE=$(tem pfile )< jog> th at'sthat ty p eo f  ch an ge  I' mt hi nking  of  making  in the sh ort  t erm
<jog> al s oare you go ing  to make tha t a  Warni ng ?
< r ogpep pe>  jog:  the r e ason i 'm not su re aboutt hat ist h at  i'm  not sure of theb es t  API for persi stent- co o ki e j ar.  It  seems kin dof wr o ng to n o tg i v e t h e caller anyinfo aboutt hefact t ha t l o adingthe c oo k iejar has fai led,  but thealtern a tive is returni ng bot h a  va lidc oo ki eja r* and *  a n e r ror  which a ls oseems  wro n g < rogp epp e> j og: f or the time b ein g, i mig ht le ave i t as  a n err or but  if i tcauses furtherCI i ssues, i' llch ang eit
<r o gpeppe > j og:  afterall, if itha d n ' tbeen an error, wewo u l dn 't havediscov e re dt his pote nt ial  tes t cross -tal k  i ssue
<ro gpeppe >  j og : so it 's  not a ll  ba d : )
<mu p > Bu g #151 1543 ope ned:U nhelpful error message whent ry i n gf roma l ocation wit h af ulldisk <j uju - core: Triag ed >  < h ttps://launchpad.ne t/ bugs/1 51154 3>
<axw> rogp eppe: goco v c an merge  pro f il e s
<axw> rogpep pe: n ot aware o f  any oth ers
# juju-dev  2015-10- 3 0 
<mup> B ug#15 115 89o p en ed: maas prov i d er,hw clock o utof sync  me ans  ju juwi ll not wo rk <kanb an -c ro ss -te am> < l andscape ><ma as -pr ovide r > <juj u-cor e:Ne w>  < M AAS :New> < h tt p s ://l au nc hpad .ne t/ bugs/ 1511 5 89> 
<rogpe ppe> axw:  ho w  wou ld  i  use go cov to mergeco verage pro fi les ? it's n ot clear  from the README
<axw>r ogpeppe : s orry,  IIA NM you ca n " gocovcon v ert pr ofile[prof il e.. . ] ". bu t it 'sgo ing to giv e you  goco vJSON  output , if it's not clea r 
<r ogpeppe> axw:  so  mya i mher e  w a s t ot rya n d see the combi ned test c ov e ra ge of juju / api  w hen run ning th e juj u /apiser ver/clien t and juj u/ 
: well,_at least_to fix *that* issue_:)
<rogpeppe> jog:_you_could always_set_JUJU_COOKIEFILE=$(tempfile)
<jog> that's that_type of change_I'm thinking of making_in the short_term
<jog>_also are you going to make that a Warning?
<rogpeppe> jog: the reason i'm not_sure_about that_is_that_i'm not sure of the_best API for persistent-cookiejar. It_seems kind_of wrong to not give the caller any_info_about the fact_that loading the cookie jar has failed, but the_alternative is returning both a valid_cookiejar *and* an_error_which_also seems wrong
<rogpeppe> jog:_for the time being, i might_leave it as an error but_if it causes further CI issues, i'll_change it
<rogpeppe> jog: after all, if_it hadn't been an error,_we wouldn't_have discovered this potential test_cross-talk issue
<rogpeppe> jog:_so it's_not all bad_:)
<mup> Bug #1511543 opened: Unhelpful error_message when trying_from a location with a full_disk_<juju-core:Triaged> <https://launchpad.net/bugs/1511543>
<axw> rogpeppe:_gocov_can_merge profiles
<axw>_rogpeppe: not aware_of_any others
#juju-dev_2015-10-30
<mup>_Bug #1511589 opened: maas provider, hwclock_out_of sync means juju will not work_<kanban-cross-team> <landscape> <maas-provider> <juju-core:New>_<MAAS:New>_<https://launchpad.net/bugs/1511589>
<rogpeppe> axw: how would_i use gocov to merge_coverage profiles? it's not clear from_the README
<axw>_rogpeppe: sorry,_IIANM you can "gocov convert profile [profile...]". but it's going to_give you gocov JSON output, if_it's not clear
<rogpeppe> axw:_so my_aim_here was to_try_and see_the combined test coverage of juju/api when_running the_juju/apiserver/client and juju/