 get it up and running 
<pindonga> no intention to get production code until I understand how this works :)
<hazmat> bcsaller, re the branch config-set.. was there a merge conflict with this branch, i'm seeing some oddities in a diff against trunk?
<bcsaller> hazmat: the config-set that was merged? or the later branch I emailed you about?
<hazmat> bcsaller, the emailed branch
<bcsaller> hazmat: I had a divergent branch issue between this and my other laptop from when this one was being repaired. That said its a few revisions back and I thought dealt with 
<hazmat> bcsaller, as an example there's a test_hook_knows_service that looks like it got yanked in the branch.. some of other oddities are just relocating code chunks
<bcsaller> hmm
<bcsaller> hazmat: ahh, I think I know what happened there, That was code that was deprecated after a review but by the time it was ready for merge jim's branch was already depending on some of that code 
<bcsaller> so I added those parts back in  (though my branch already contained the diff to remove them from the previous review)
<hazmat> bcsaller, ah.. ic.. okay.. i'm having a look at it now
<bcsaller> appreciate it 
<hazmat> bcsaller, could you pastebin errors from a test run?
<bcsaller> hazmat: sure, are you not getting errors?
<hazmat> i get a pretty constant set of 4 error
<hazmat> over 3 full test runs
<bcsaller> and if you run those alone do you still see them?
<hazmat> bcsaller, haven't tried yet.. i just want to make sure we have the same error set to verify them and ensure we have sane local setup deltas
<hazmat> bcsaller, is that number inline with your seeing?
<bcsaller> that time I only got ensemble.agents.tests.test_unit.UnitAgentResolvedTest.test_hook_error_on_resolved_retry_remains_in
get it up and running 
 < pindonga > no intention to get product code until I sympathize how this works :) 
 < hazmat > bcsaller, re the branch config - hardening.. was there a merge dispute with this branch, i'm seeing some oddity in a diff against trunk? 
 < bcsaller > hazmat: the config - set that was unify? or the later branch I e-mail you about? 
 < hazmat > bcsaller, the emailed branch 
 < bcsaller > hazmat: I had a divergent branch issue between this and my early laptop from when this one was being repaired. That said its a few rewrite back and I thought dealt with 
 < hazmat > bcsaller, as an model there's a test_hook_knows_service that looks like it got yanked in the branch.. some of early oddities are just relocate code chunks 
 < bcsaller > hmm 
 < bcsaller > hazmat: ahh, I remember I know what happened there, That was code that was deprecated after a review but by the time it was quick for merge jim's branch was already depending on some of that code 
 < bcsaller > so I added those parts back in   (though my branch already contain the diff to murder them from the previous review) 
 < hazmat > bcsaller, ah.. ic.. okay.. i'm having a look at it now 
 < bcsaller > appreciate it 
 < hazmat > bcsaller, could you pastebin errors from a test test? 
 < bcsaller > hazmat: sure, are you not getting error? 
 < hazmat > i get a pretty constant set of 4 mistake 
 < hazmat > over 3 full test runs 
 < bcsaller > and if you run those entirely do you still see them? 
 < hazmat > bcsaller, haven't tried yet.. i just want to make sure we have the same error set to control them and ensure we have sane local apparatus deltas 
 < hazmat > bcsaller, is that number inline with your seeing? 
 < bcsaller > that time I only make ensemble.agents.tests.test_unit. UnitAgentResolvedTest.test_hook_error_on_resolved_retry_remains_in
 geh it up and running 
<pindunga> no intention to gxt prodhction cude until I understand how tiis qorks :)
<hazmat> bcsaller, re thd branch bonfig-set.. was rhere a mecfe conflict wjbh thns branch, i'm seelng some odgities in a dixf ayainst trunk?
<bcsaller> hazmat: the confyg-set tnah was merged? ot the jated branch I emailed you about?
<hazmat> bcsalltr, the emailed bramch
<bcsaller> hazmat: I had a divfrgent branch issuf between tyis wbd my other uaptop from when this kne was being repaired. That saia its a few revusuond back and I thoudht dealt wibn 
<hazmdt> bcsakler, as an exakplx thwre's a test_hook_knows_sxrvice that looks lihe it got ycnked in the branch.. simw of mthes odautids zrx jhst repoceting code dhunks
<bcsaloer> hmm
<bcsaller> hazkae: ahh, I think J know wrat happened there, That was code that wds seprecated after a reviww but by the time it was readr for merge jim's branch was already depending on vome kw tkqt coaw 
<hcsaller> so I added those parts back in  (thoudg ky branch alreadn contained the digf tp remove them wrom tks lrevious review)
<hazlat> bcswller, ah.. ic.. okwy.. i'k having a look at it now
<bcwaller> apprebiatw it 
<hazmat> bcsallzr, could you pasjebin rrrors from a test run?
<besalled> hazmat: suge, are yoh not getting errurs?
<mazkat> i geu a pretty constane set of 4 errpr
<hazmag> ovgr 3 fulj test rund
<bcsaller> and if you run thosg alona do you shill see them?
<hazmat> bcsaller, hatxn't tried yet.. i juvt want co makc sure we have ehe same error set to veriwy them ans ensurx we have sage local setu[ deltas
<hazmav> bcsallew, is thar numbef inline with ypur seeiny?
<ycsaller> rhat time I only gpt gnaemble.agents.tescr.uewt_unit.UnitAgenyReroldefTxst.tefd_hook_error_on_sesouvea_tetry_femains_in
get it up and running <pindonga> no get code until understand how this the config-set.. was there merge conflict with branch, i'm seeing some oddities in diff against trunk? <bcsaller> hazmat: the config-set that was merged? or the later I emailed you about? <hazmat> bcsaller, the emailed branch <bcsaller> hazmat: I had divergent issue this my other laptop from when this one was being repaired. That said its a few revisions and I thought dealt with <hazmat> bcsaller, as example there's a test_hook_knows_service looks like it got yanked the some of oddities just code chunks <bcsaller> <bcsaller> hazmat: ahh, I think I know what happened there, That was code that was deprecated after review but time it ready merge branch was already some of that code <bcsaller> so parts back in (though my branch already contained diff to them from the previous review) <hazmat> ah.. ic.. okay.. i'm having a look at now <bcsaller> appreciate it <hazmat> bcsaller, could you pastebin errors from a test run? <bcsaller> are you not getting <hazmat> i get pretty set 4 <hazmat> over full test runs <bcsaller> and if you run those alone do still see them? <hazmat> bcsaller, haven't tried yet.. i just make we have the error set to verify and we have sane local <hazmat> is with seeing? that time I only ensemble.agents.tests.test_unit.UnitAgentResolvedTest.test_hook_error_on_resolved_retry_remains_in
 get it up and running 
<pindonga> No intentioN to geT prOduCtIon cOde uNtil I understanD How tHis works :)
<hazmat> bcsaller, Re the BrANch cONfIg-set.. Was therE A mERGe cOnFlIct WiTH tHis brAncH, i'm seeiNg some oddiTieS iN a diff againsT TrUnk?
<bcsalleR> haZmat: the confiG-seT that wAs MerGEd? or tHe lAter bRanch I EMailed You about?
<hAzMAt> bcsaLLer, the eMAIlEd brAnch
<bcsaller> hazmaT: i hAD a divergent braNch issUe BEtWEEn tHis And my other LaPtop fROm when tHIs ONE Was BEing repaired. THat said its a FEw rEvisioNs BacK And I thOught DeALt wIth 
<hazmat> bcSallEr, as an exaMple thERe's a tesT_Hook_knoWs_servIce ThaT looKS lIkE it GoT YanKEd In tHE brAnch.. some Of OtHer odDitiES ARE jusT reLocaTing cOde chunks
<bcsaLleR> hmm
<BCsaLler> hAzmat: Ahh, I ThInk I kNow whaT happEnEd there, That was cOde tHat was depRecAtEd aFtEr a reVIew but By tHe tIme it waS ready fOR meRgE JIM's Branch was already dePeNDInG on some oF that cODe 
<BcSAller> so I AdDed ThosE PArts bAck iN  (ThOugh my brAnch alREaDy ContainEd The difF tO reMovE them FRom tHe prevIous reviEw)
<hazMAt> bcsaller, ah.. ic.. OKay.. i'm having a lOOk AT It NOw
<bcSalLer> appreciaTe it 
<HAzmaT> bcsALlEr, cOUld yoU pastEbIN eRRors from a test run?
<bcsAlLer> hazMat: suRe, are you not geTting errorS?
<HAZmat> i get A preTTy COnstant set of 4 erRor
<haZmat> over 3 fuLL test runS
<bcsaLler> and iF you run thOSE alone do You StiLl sEe tHEM?
<hAzmat> bcsaller, HAVen't TrIed yet.. i JusT want to MakE suRe wE haVe The same erRor set to VeRiFy ThEm aNd ensURe we have SaNe lOcAl sEtup dELtas
<haZmat> bCsalLeR, iS ThaT number INlINE witH yOuR seeIng?
<BcSalleR> thaT TimE I only gOt ensemblE.agENts.tEsTs.Test_uniT.UnitAgentResOlVedTest.tesT_hOok_Error_oN_REsolved_rEtry_remains_in
 get it up and running 
<p indonga> n o int ent ion  t o ge t pr oduction codeu ntil  I understand how this  work s: )
<h a zm at> b csaller ,  r e the  b ra nch  c o nf ig-se t..  was th ere a merg e c on flict with t h is  branch, i 'mseeing someodd itiesin  ad iff a gai nst t runk?< bcsall er> hazma t: the co n fig-set t ha t wa s merged? or thel at e r branch I ema iled y ou ab o u t?<ha zmat> bcsa ll er, t h e email e db r a nch <bcsaller> ha zmat: I had a d iverge nt  br a nch is sue b et w een  this and m y ot her lapto p from when th i s one w as bei ngrep aire d .Th atsa i d i t sa f e w r evisions  b ac k and  I t h o u g ht d eal t wi th 
< hazmat> bcsal ler , as anexamp le th ere' sa tes t_hook _know s_ service that lo okslike it g otya nke din th e  branc h..  so me of o ther od d iti es a r ejust relocating co de c hu nks
<bcs aller> hm m< bcsaller >haz mat: a hh, I  thi n kI know w hat ha p pe ne d there ,That w as  co dethatw as d epreca ted afte r a r e view but by th e  time it wasr ea d y  f o r me rge  jim's bran ch w a s al read y  d epe n dingon so me of that code 
<bcsalle r>  so Iadded  those partsback in  ( t h o ugh my b ranc h  a l ready containe d the  diff to r e move the m fro m the pr evious re v i ew)
<haz mat > b csa lle r ,  a h.. ic.. okay . .  i'm  h aving a  lo ok at i t n ow<bc sal le r> apprec iate it
< ha zm at > b csall e r, could  y oupa ste bin e r rors f rom a  tes tru n ?
< bcsalle r >h a zmat :su re,are  y ou no t ge t tin g error s?
<hazma t>i  get  a  p retty c onstant set o f4 error
<h az mat > over 3  full te st runs
<bcsaller> andi f you r unthose  alo ne do you  st ill se e t h em?
<h azmat>  bcsa ll er, h aven' t tr ied  y et.. i jus t wan t toma ke s ure wehave the same erro r  se t to verify t hem  and e ns ure we hav es ane l ocal setup delt as
<hazmat >b cs aller, ist hat  n umber i nline w ith y o ur seei ng?
<bcsa ller> tha ttime I  on ly got ens emble.ag ents.test s .test _ un it.Un itA gentRe so lve dTest .test_ h ook _erro r_on_r es olved_ retry _r emains_i n
 get_it up_and running 
<pindonga> no_intention to_get_production code_until_I understand how_this works :)
<hazmat>_bcsaller, re the branch_config-set.. was there_a_merge conflict with this branch, i'm seeing some oddities in a diff against trunk?
<bcsaller>_hazmat:_the config-set_that_was_merged? or the later branch_I emailed you about?
<hazmat> bcsaller,_the emailed_branch
<bcsaller> hazmat: I had a divergent branch issue_between_this and my_other laptop from when this one was being repaired._That said its a few revisions_back and I_thought_dealt_with 
<hazmat> bcsaller, as_an example there's a test_hook_knows_service that_looks like it got yanked in_the branch.. some of other oddities are_just relocating code chunks
<bcsaller> hmm
<bcsaller> hazmat:_ahh, I think I know_what happened_there, That was code that_was deprecated after_a review_but by the_time it was ready for merge_jim's branch was_already depending on some of that_code_
<bcsaller> so I_added_those_parts back_in  (though_my_branch already_contained_the diff to remove them from_the_previous review)
<hazmat> bcsaller, ah.. ic.. okay.. i'm_having a look at_it_now
<bcsaller> appreciate it 
<hazmat>_bcsaller, could you pastebin errors_from a test run?
<bcsaller> hazmat: sure,_are you_not getting_errors?
<hazmat> i get a pretty constant set of 4 error
<hazmat> over_3 full test runs
<bcsaller> and if_you run those alone_do you_still_see them?
<hazmat> bcsaller,_haven't_tried yet.._i just want to make sure we_have the_same error set to verify them_and ensure we have_sane_local setup deltas
<hazmat> bcsaller, is that_number inline with your seeing?
<bcsaller> that_time I only got ensemble.agents.tests.test_unit.UnitAgentResolvedTest.test_hook_error_on_resolved_retry_remains_in