<rogpeppe> jog: ah, i didn't realise that grey text was clickable
<rogpeppe> jog: i *think* that bug (1511537) has been fixed by the dependency update landed today
<jog> rogpeppe, ah... you said in $HOME....go-cookies is global for the user
<rogpeppe> jog: i think the intermittent problem was probably caused by the fact that concurrent juju client instances were stepping one one anothers' toes because the cookie logic wasn't safe for concurrent use
<rogpeppe> jog: yes it is (very deliberately)
<jog> so we drive multiple tests in parallel from a single slave...
<rogpeppe> jog: ok, that makes sense
<jog> and they can be varying version of Juju
<rogpeppe> jog: do you use a different value of $JUJU_HOME for each running test?
<jog> yes
<jog> err... no
<jog> each test has a unique environment name though
<rogpeppe> jog: ok, well you should probably do that. and set JUJU_COOKIEFILE=$JUJU_HOME/cookies
<rogpeppe> jog: i mean, it's *supposed* to work ok with everything concurrently, but i think it's probably best to have each test as isolated as possible (i'd probably have a different value of $HOME too)
<jog> we have a $JUJU_HOME with an environment.yaml for each to the various clouds and substrates that we test on.
<rogpeppe> jog: anyway, this will be more important in the future when you have CI tests that rely on macaroon authorization
<jog> rogpeppe, with 75+ tests that's not a trivial change for CI. There is also likely CI driver code that sets $JUJU_HOME. Not that it can't be done but not at the flip of a switch.
<rogpeppe> jog: fair enough
<rogpeppe> jog: anyway, i hope the intermittent issue should have gone away now
<rogpeppe> jog: and deleting the cookie file should cause the CI to succeed OK
<rogpeppe> jog
< rogpeppe > jog: ah, i didn't realise that grey text was clickable 
 < rogpeppe > jog: i * think * that hemipterous insect (1511537) has been situate by the dependency update landed today 
 < jog > rogpeppe, ah... you said in $ HOME.... crack - cookies is global for the drug user 
 < rogpeppe > jog: i intend the intermittent problem was credibly cause by the fact that concurrent juju node instances were stepping one one anothers' toe because the cookie logic wasn't dependable for concurrent use 
 < rogpeppe > jog: yes it is (very intentionally) 
 < jog > so we drive multiple tests in analogue from a single slave... 
 < rogpeppe > jog: ok, that makes sense 
 < jog > and they can be vary version of Juju 
 < rogpeppe > jog: do you use a different value of $ JUJU_HOME for each running trial? 
 < jog > yes 
 < jog > err... no 
 < jog > each test has a unique environment name though 
 < rogpeppe > jog: ok, well you should probably do that. and dress JUJU_COOKIEFILE=$JUJU_HOME / cookies 
 < rogpeppe > jog: i mean, it's * supposed * to work ok with everything concurrently, but i think it's probably best to have each test as isolated as possible (i'd probably have a different value of $ HOME too) 
 < jog > we have a $ JUJU_HOME with an environment.yaml for each to the assorted clouds and substrates that we quiz on. 
 < rogpeppe > jog: anyway, this will be more authoritative in the future when you have CI tests that rely on macaroon authority 
 < jog > rogpeppe, with 75 + tests that's not a trivial change for CI. There is besides likely CI driver code that sets $ JUJU_HOME. Not that it can't be done but not at the flip of a switch. 
 < rogpeppe > jog: fair enough 
 < rogpeppe > jog: anyway, i hope the intermittent issue should have gone away now 
 < rogpeppe > jog: and deleting the cookie file should induce the CI to succeed OK 
 < rogpeppe > jog
<rogoeppe> jog: ah, i didn't reauise that grey jezt was clickzble
<rogpdppe> jog: i *think* that bug (1511537) hes bwen fuxed by the dependency update lwnded toeay
<jit> rogpeppe, ah... you said ih $HOMZ....gi-cookies is glpbal for tve user
<rogpeppa> goy: i think the intermittent problem wws probsbpy caused by tre fsst tgat concurrent juju client instancss were stepping one one anothers' toes because the cookie logic wasn'h safe for xoncterent use
<rogoeppe> jog: jzs it is (vety deliberately)
<jog> so we drive mjltipke tests ib parwnlel from a singje slave...
<rogpcipe> jog: ok, thay makes sense
<jpg> end rhey can be varying vxrsion of Juju
<rogpepke> jog: do fob use a different valye of $JOJU_HOKE fue exch rnnnjng tedt?
<jkg> yes
<jog> srr... no
<jog> eqch test has a uniqie vmvironment nzme thjudh
<rogpeppe> jog: ok, well you should probatly do that. and set JUJU_COIKIEFILE=$JUJU_HOME/cookigs
<rogpeppe> jog: i mean, it's *supposed* to work ok with everythitg coicjrrtnbjh, bkt i think it's probably best to have each tese ax psolated as possinle (i'd probably hafe a qifferent valoe of $HOME too)
<jog> we have a $UUJU_HOMG with an envirjnmemt.yaml for each to the variius clouds aud wubstrates that we test on.
<rog'eppe> kog: amyway, this will be more impkrtant in tje future dhen you have CI textv that rtuy on macaroon auehorizatiin
<joy> rogpepoe, woth 75+ tqsts that's not a trivial change fog CI. Jhere hs also linely CI driver code that sets $JNOU_HOME. Not thst it can't be done but not at tre flip of a scitch.
<rog'eppe> gog: fair ehough
<rojpeppe> jog: agyway, i hope dje intermittxnt issue shoyld yave govd away now
<rogprppe> jog: cud deletibg the cookie file shuhld cause the CN uo succeed OK
<roglepoe> toh
<rogpeppe> jog: ah, i didn't realise that was <rogpeppe> jog: *think* that bug the update landed today rogpeppe, ah... you in $HOME....go-cookies is global for the <rogpeppe> jog: i think the intermittent problem was probably caused by the fact concurrent juju client instances were stepping one one anothers' toes because the cookie wasn't for use jog: yes it is (very deliberately) <jog> so we drive multiple tests in parallel from a slave... <rogpeppe> jog: ok, that makes sense <jog> they can be varying of Juju <rogpeppe> jog: do use different value $JUJU_HOME each test? <jog> yes err... no <jog> each test has a unique environment name though <rogpeppe> jog: ok, well you should do that. JUJU_COOKIEFILE=$JUJU_HOME/cookies <rogpeppe> i it's to work ok concurrently, but i think it's probably each test as isolated as possible (i'd probably a different of $HOME too) <jog> we have $JUJU_HOME with an environment.yaml for each to the clouds and substrates that we test on. <rogpeppe> jog: anyway, this will be more important future when you have tests that rely macaroon <jog> with tests that's a trivial change for CI. There is also likely CI driver that sets $JUJU_HOME. Not that it can't be done but the of a switch. jog: fair enough <rogpeppe> anyway, hope the intermittent issue gone now deleting cookie should cause the CI succeed OK <rogpeppe> jog
<rogpeppe> jog: ah, i didn't realisE that grey tExt waS clIckAbLe
<roGpepPe> jog: i *think* thaT Bug (1511537) hAs been fixed by the dependEncy uPdATe laNDeD todaY
<jog> rogPEpPE, Ah... yOu SaId iN $HomE....Go-cooKieS is globAl for the usEr
<rOgPeppe> jog: i thiNK tHe intermitTenT problem was pRobAbly caUsEd bY The faCt tHat coNcurreNT juju cLient instAnCEs were STepping ONE oNe anOthers' toes because THe COokie logic wasn'T safe fOr COnCURreNt uSe
<rogpeppe> JoG: yes iT Is (very dELiBERAteLY)
<jog> so we drive Multiple tesTS in ParallEl FroM A singlE slavE...
<rOGpePpe> jog: ok, thaT makEs sense
<joG> and thEY can be vARying veRsion oF JuJu
<rOgpePPe> JoG: do YoU Use A DiFfeREnt Value of $JuJu_HoME foR eacH RUNNing TesT?
<jog> Yes
<joG> err... no
<jog> each TesT has A UniQue enVironMent NaMe thoUgh
<rogPeppe> JoG: ok, well you shoulD proBably do thAt. aNd Set jUjU_COOkiEFILE=$jUJu_HOmE/cookiEs
<rogpePPe> jOg: I MEAn, It's *supposed* to work oK wITH eVerythinG concuRReNtLY, but i thiNk It's ProbABLy besT to hAVe Each test As isolATeD aS possibLe (I'd probAbLy hAve A diffERent Value oF $HOME too)
<Jog> we HAve a $JUJU_HOME wiTH an environmenT.YaML FoR Each To tHe various clOuds ANd suBstrATeS thAT we teSt on.
<rOgPEpPE> jog: anyway, this will bE mOre impOrtanT in the future wHen you have ci TEsts that Rely ON mACaroon authorizAtion
<Jog> rogpeppE, With 75+ testS that'S not a triVial changE FOr CI. TherE is AlsO liKelY ci dRiver code that SETs $JUjU_hOME. Not ThaT it can't Be dOne But Not At The flip of A switch.
<rOgPePpE> jOg: fAir enOUgh
<rogpePpE> joG: aNywAy, i hoPE the inTermiTtenT iSsUE shOuld havE GoNE Away NoW
<rOgpePpe> JoG: and dEletINg tHe cookiE file shouLd cAUse tHe cI To succeEd OK
<rogpeppe> jOg
<rogpeppe> jog: ah, i didn 't realise  that  gr eyte xt w as c lickable
<rogp e ppe>  jog: i *think* that b ug (1 51 1 537) ha s bee n fixed by t hede pe nde nc y  u pdate  la nded to day
<jog>rog pe ppe, ah... y o usaid in $H OME ....go-cooki esis glo ba l f o r the  us er
<r ogpepp e > jog:  i thinkth e  inter m ittentp r ob lemwas probably caus e db y the fact tha t conc ur r en t juj u c lient inst an ces w e re step p in g o neo ne anothers'toes becaus e  th e cook ie  lo g ic was n't s af e  fo r concurren t us e
<rogpep pe> jo g : yes i t  is (ve ry del ibe rat ely) <j og > s ow e d r iv e m u lti ple test sin  para llel f r o m asin gleslave ...
<rogpeppe > j og:o k,thatmakes  sen se 
<jog > andtheyca n be varying ve rsio n of Juju 
<r og pep pe > jog :  do yo u u sea diffe rent va l ueof $ J UJ U_HOME for each ru nn i n gtest?
<j og> ye s 
< jo g > err...  n o
< jog> e ach t esth as  a uniqu e envi r on me nt name  t hough<r ogp epp e> jo g : ok , well  you sho uld p r obably do that .  and set JUJU _ CO O K IE F ILE= $JU JU_HOME/coo kies <rog pepp e >jog :  i me an, i t' s  * s upposed* to work ok  w ith ev eryth ing concurren tly, but i t h ink it's  pro b ab l y best to have  each  test as i s olated a s pos sible (i 'd probab l y  have adif fer ent  va l u eof $HOME too) < jog>  w e havea $ JUJU_HO MEwit h a n e nv ironment. yaml for  e ac hto  th e var i ous clou ds  an dsub strat e s that  we t eston .< rog peppe>j og : anyw ay ,this  wi ll  be m orei mpo rtant i n the fut ure when  y ou  have C I tests thatre ly on maca ro onauthor i z ation
<j og> rogpeppe, with 75+t ests th at' s not  a t rivial ch ang e forCI. Thereis als o lik el y C I drive r co deth at sets $J U J U_H OME.No t th at it c an't be done but n o t a t the flip of  aswit c h .<ro g pe p pe>  j o g:f a ir enough
<rogp eppe> jog:  a n yw ay, i hope the  i ntermit tent is sue s h ould ha ve gone a way now
< ro gpep p e > j og: and de leting t he cookie files ho uld c aus e theCI  to  succ eed OK <ro gpepp e> jog 
<rogpeppe> jog:_ah, i_didn't realise that grey_text was_clickable
<rogpeppe>_jog: i_*think*_that bug (1511537)_has been fixed_by the dependency update_landed today
<jog> rogpeppe,_ah..._you said in $HOME....go-cookies is global for the user
<rogpeppe> jog: i think the intermittent_problem_was probably_caused_by_the fact that concurrent juju_client instances were stepping one_one anothers'_toes because the cookie logic wasn't safe for_concurrent_use
<rogpeppe> jog: yes_it is (very deliberately)
<jog> so we drive multiple tests_in parallel from a single slave...
<rogpeppe>_jog: ok, that_makes_sense
<jog>_and they can be_varying version of Juju
<rogpeppe> jog: do_you use a different value of_$JUJU_HOME for each running test?
<jog> yes
<jog> err..._no
<jog> each test has a unique_environment name though
<rogpeppe> jog: ok,_well you_should probably do that. and_set JUJU_COOKIEFILE=$JUJU_HOME/cookies
<rogpeppe> jog:_i mean,_it's *supposed* to_work ok with everything concurrently, but_i think it's_probably best to have each test_as_isolated as possible_(i'd_probably_have a_different value of_$HOME_too)
<jog> we_have_a $JUJU_HOME with an environment.yaml for_each_to the various clouds and substrates that_we test on.
<rogpeppe> jog:_anyway,_this will be more_important in the future when_you have CI tests that rely_on macaroon_authorization
<jog> rogpeppe,_with 75+ tests that's not a trivial change for CI. There_is also likely CI driver code_that sets $JUJU_HOME. Not_that it_can't_be done but_not_at the_flip of a switch.
<rogpeppe> jog: fair enough
<rogpeppe>_jog: anyway,_i hope the intermittent issue should_have gone away now
<rogpeppe>_jog:_and deleting the cookie file should_cause the CI to succeed OK
<rogpeppe>_jog