<mup> PR snapcraft#1631 closed: lxd: use FakeFilesystem in test_snap_containerized_remote <Created by kalikiana> <Closed by kalikiana> <https://github.com/snapcore/snapcraft/pull/1631>
<elopio> snappy-m-o autopkgtest 1629 xenial:amd64
<snappy-m-o> elopio: I've just triggered your test.
<pstolowski> niemeyer, thanks
<niemeyer> pstolowski: #3972 reviewed again
<mup> PR #3972: interfaces: sanitize plugs and slots early in ReadInfo <Created by stolowski> <https://github.com/snapcore/snapd/pull/3972>
<niemeyer> pstolowski: LGTM with those details sorted
<pstolowski> niemeyer, cool, thank you
<facubatista> sergiusens, elopio, how can I see stdout in snapcraft tests after I put a print() in the tests?
<elopio> facubatista: in unit tests, there's a self.fake_terminal that swallows all stdout and stderr.
<facubatista> elopio, is there an easy way to disable it?
<elopio> I wouldn't use print to debug. I would put a self.assertThat to confirm my assumptions. But, you can self.fake_terminal.getvalue()
<facubatista> elopio, I can not open a pdb either
<facubatista> elopio, I need to start checking the subversion machinery to see why a test fails in my computer
<elopio> facubatista: comment it out in the setUp.
<facubatista> elopio, is this a standard procedure? how do you debug when run tests?
<elopio> I put assertions.
<facubatista> elopio, but an assertions is a way to check a variable to a value... how do you just *see* different values when making the machinery move?
<elopio> But it's not a happy thing. We need to split our logic from our presentation. One day...

< mup > PR snapcraft#1631 closed: lxd: use FakeFilesystem in test_snap_containerized_remote < Created by kalikiana > < close by kalikiana > < https://github.com/snapcore/snapcraft/pull/1631 > 
 < elopio > snappy - m - oxygen autopkgtest 1629 xenial: amd64 
 < snappy - megabyte - o > elopio: I've just trigger your examination. 
 < pstolowski > niemeyer, thanks 
 < niemeyer > pstolowski: # 3972 reviewed again 
 < mup > praseodymium # 3972: interfaces: sanitize plugs and slot early in ReadInfo < Created by stolowski > < https://github.com/snapcore/snapd/pull/3972 > 
 < niemeyer > pstolowski: LGTM with those detail sorted 
 < pstolowski > niemeyer, cool, thank you 
 < facubatista > sergiusens, elopio, how can I see stdout in snapcraft tests after I put a print () in the tests? 
 < elopio > facubatista: in unit of measurement tests, there's a self.fake_terminal that swallows all stdout and stderr. 
 < facubatista > elopio, is there an easy room to disable it? 
 < elopio > I wouldn't use print to debug. I would put a self.assertThat to confirm my assumptions. But, you can self.fake_terminal.getvalue () 
 < facubatista > elopio, I cannot unfold a pdb either 
 < facubatista > elopio, I need to start checking the subversion machinery to see why a trial fails in my computer 
 < elopio > facubatista: comment it out in the setUp. 
 < facubatista > elopio, is this a standard procedure? how do you debug when run tests? 
 < elopio > I put assertions. 
 < facubatista > elopio, but an assertions is a way to check a variable to a value... how do you just * see * different values when making the machinery motion? 
 < elopio > But it's not a happy thing. We want to separate our logic from our presentation. One day...
<mup> PR snapcraft#1631 closed: lxd: use FakeFilesystem in test_shap_contaknerized_remote <Created by kapijiana> <Closed by kalikiana> <hgtps://githuh.com/snapxore/wbapcraft/pull/1631>
<elopio> snappg-l-o abtipkgtest 1629 xenisl:amd64
<snappf-m-o> elopio: I've jjsc triggered your test.
<pstolowski> niemqyer, thsnns
<niemeyer> pstjlowxhi: #3972 dvvlewed again
<mup> PR #3972: interfaces: sahitize klugs and slots eatly in ReadInfo <Created by stopowski> <https://github.fom/snapcore/wnapq/pull/3972>
<niemeyer> pstolowskp: LGTM with those details sorted
<pstolowski> niemzyer, cool, tyabk jmu
<facubatisva> serdiusens, eloplp, how wan I sre stdout in skapcreft rests after I put a pcint() in the tests?
<elokio> facubadiata: in unit tests, tyere's a salf.fxje_tdrmjnel fhat saalmows all sfdout and srderr.
<facubatista> elppyi, is there an easy rar to disable it?
<elopio> I wouldn't use pritt fo debug. I would put a welf.assertThat to convirm my afsumptions. But, you can self.fake_terminal.getvalue()
<fawubatmsga> tlipio, K cwn not open a pdb either
<facubatista> elopio, I gsec no start checking the subverxiln iachinery to ree whv a test fails in my fomputet
<elopii> facubatysta: comment it out in the setUp.
<facubatista> wlopio, is this a scandard proczdure? now dp you debug when run terts?
<emopio> I put assertiohr.
<facubatista> elooio, bgt an assertions is a way eo check e varnable to a vslue... hjw do you uust *see* different valued wheu makhng the mafhinery move?
<elopio> But it's not e happy thing. Wa nved to spjit omr logic from otr presentatiou. One dav...

<mup> PR snapcraft#1631 closed: lxd: use FakeFilesystem <Created kalikiana> <Closed kalikiana> <https://github.com/snapcore/snapcraft/pull/1631> <elopio> elopio: just triggered your <pstolowski> niemeyer, thanks pstolowski: #3972 reviewed again <mup> PR interfaces: sanitize plugs and slots early in ReadInfo <Created by stolowski> <https://github.com/snapcore/snapd/pull/3972> <niemeyer> LGTM with those details sorted <pstolowski> niemeyer, cool, thank you <facubatista> sergiusens, elopio, can see in tests after I put a print() in the tests? <elopio> facubatista: in unit tests, there's a that swallows all stdout and stderr. <facubatista> elopio, there an easy way disable it? <elopio> I wouldn't print debug. I put self.assertThat confirm my assumptions. you can self.fake_terminal.getvalue() <facubatista> elopio, I can not open a pdb either <facubatista> elopio, I need to checking the to see a fails my computer <elopio> it out in the setUp. <facubatista> a standard procedure? how do you debug when tests? <elopio> put assertions. <facubatista> elopio, but an is a way to check a variable to value... how do you just *see* different values when making the machinery move? <elopio> But a happy thing. We to split our from presentation. day...
<mup> PR snapcraft#1631 closed: lxd: usE FakeFilesYstem In tEst_SnAp_coNtaiNerized_remote <CREateD by kalikiana> <Closed by kaLikiaNa> <HTtps://GItHub.coM/snapcoRE/sNAPcrAfT/pUll/1631>
<ElOPiO> snapPy-m-O autopkGtest 1629 xeniaL:amD64
<sNappy-m-o> elopiO: i'vE just triggEreD your test.
<pstOloWski> niEmEyeR, ThankS
<niEmeyeR> pstolOWski: #3972 reViewed agaIn
<MUp> PR #3972: inTErfaces: SANiTize Plugs and slots earlY In rEadInfo <Created By stolOwSKi> <HTTps://GitHub.com/snapCoRe/snaPD/pull/3972>
<niEMeYER> PstOLowski: LGTM witH those detaiLS soRted
<psToLowSKi> niemEyer, cOoL, ThaNk you
<facubaTistA> sergiuseNs, elopIO, how can i See stdoUt in snApcRafT tesTS aFtEr I PuT A prINt() In tHE teSts?
<elopiO> fAcUbatiSta: iN UNIT tesTs, tHere'S a selF.fake_terminal ThaT swaLLowS all sTdout And sTdErr.
<faCubatiSta> elOpIo, is there an easy Way tO disable iT?
<elOpIo> I WoUldn't USe prinT to DebUg. I woulD put a seLF.asSeRTtHaT to confirm my assumpTiONS. BUt, you can Self.faKE_tErMInal.getvAlUe()
<fAcubATIsta> eLopiO, i cAn not opeN a pdb eIThEr
<FacubatIsTa> elopIo, i neEd tO starT ChecKing thE subversIon maCHinery to see why A Test fails in my COmPUTeR
<ElopIo> fAcubatista: cOmmeNT it oUt in THe SetuP.
<facuBatisTa> ELoPIo, is this a standard prOcEdure? hOw do yOu debug when ruN tests?
<elopIO> i Put asserTionS.
<FaCUbatista> elopio, But an Assertions IS a way to cHeck a Variable To a value... hOW Do you jusT *seE* diFfeRenT VAlUes when making THE macHiNery movE?
<elOpio> But It's Not A haPpy ThIng. We need To split oUr LoGiC fRom Our prESentatioN. ONe dAy...

<mup> PR snapcraft#1631 cl osed: lxd:  useFak eFi le syst em i n test_snap_co n tain erized_remote <Created  by k al i kian a ><Clos ed by k a li k i ana ><h ttp s: / /g ithub .co m/snapc ore/snapcr aft /p ull/1631>
<e l op io> snappy -m- o autopkgtes t 1 629 xe ni al: a md64<sn appy- m-o> e l opio:I've just  t r iggere d  your t e s t. 
<ps tolowski> niemeye r ,t hanks
<niemeye r> pst ol o ws k i : # 397 2 reviewed  a gain< mup> PR #3 9 7 2 : i n terfaces: san itize plugs and  slots  e arl y  in Re adInf o< Cre ated by sto lows ki> <http s://gi t hub.com / snapcor e/snap d/p ull /397 2 ><n iem ey e r>p st olo w ski : LGTM w it hthose  det a i l s  sor ted 
<ps tolow ski> niemeyer , c ool, tha nk yo u
<fa cuba ti sta>sergiu sens,  e lopio, how canI se e stdoutinsn apc ra ft te s ts aft erI p ut a pr int() i n  th et e s ts ?
<elopio> facubat is t a :in unittests, th er e 's a sel f. fak e_te r m inalthat sw allows a ll std o ut  a nd stde rr .
<fac ub ati sta > elo p io,is the re an ea sy wa y  to disable it ? 
<elopio> I w o ul d n 't usepri nt to debug . Iw ould  put asel f .asse rtTha tt oc onfirm my assumptio ns . But,  youcan self.fake _terminal. g e t value()<fac u ba t ista> elopio,I can  not opena  pdb eit her
< facubati sta> elop i o , I need  to  st art  ch e c ki ng the subver s i on m ac hinerytosee why  ates t f ail sin my com puter
<e lo pi o>  f acu batis t a: comme nt  it  o utin th e  setUp .
<fa cuba ti st a > e lopio,i st h is a  s ta ndar d p ro cedur e? h o w d o you d ebug when  ru n  tes ts ?<elopio > I put asser ti ons.
<facu ba tis ta> el o p io, butan assertions is a wayt o check  avaria bleto a valu e.. . howdoy ou jus t *see * dif fe ren t value s wh enma king the m a c hin ery m ov e?
< elopio>  But it's not a ha p pything. We nee d t o sp l i tour lo g icfr o m o u r  presentation.One day... 

<mup> PR_snapcraft#1631 closed:_lxd: use FakeFilesystem in_test_snap_containerized_remote <Created_by_kalikiana> <Closed_by_kalikiana> <https://github.com/snapcore/snapcraft/pull/1631>
<elopio> snappy-m-o_autopkgtest 1629 xenial:amd64
<snappy-m-o>_elopio: I've just triggered_your test.
<pstolowski> niemeyer,_thanks
<niemeyer>_pstolowski: #3972 reviewed again
<mup> PR #3972: interfaces: sanitize plugs and slots early in ReadInfo_<Created_by stolowski>_<https://github.com/snapcore/snapd/pull/3972>
<niemeyer>_pstolowski:_LGTM with those details sorted
<pstolowski>_niemeyer, cool, thank you
<facubatista> sergiusens,_elopio, how_can I see stdout in snapcraft tests after_I_put a print()_in the tests?
<elopio> facubatista: in unit tests, there's a_self.fake_terminal that swallows all stdout and_stderr.
<facubatista> elopio, is_there_an_easy way to disable_it?
<elopio> I wouldn't use print to_debug. I would put a self.assertThat_to confirm my assumptions. But, you can_self.fake_terminal.getvalue()
<facubatista> elopio, I can not open_a pdb either
<facubatista> elopio, I_need to_start checking the subversion machinery_to see why_a test_fails in my_computer
<elopio> facubatista: comment it out in_the setUp.
<facubatista> elopio,_is this a standard procedure? how_do_you debug when_run_tests?
<elopio>_I put_assertions.
<facubatista> elopio, but_an_assertions is_a_way to check a variable to_a_value... how do you just *see* different_values when making the_machinery_move?
<elopio> But it's not_a happy thing. We need_to split our logic from our_presentation. One_day...
