 cachio_, my versions: http://pastebin.ubuntu.com/25759794/
<pstolowski> cachio_, how about yours?
<cachio_> pstolowski, one min please
<cachio_> flasing the new one
<cachio_> pstolowski, did you use the ubuntu-image snap?
<pstolowski> cachio_, yes
<cachio_> pstolowski, https://paste.ubuntu.com/25759837/
<cachio_> this is mine
<cachio_> flashed with deb ubuntu image
<cachio_> the only diff is the rev for the core
<cachio_> pstolowski, I am gonna run the test now
<elopio> sorry for not replying kyrofa, I spent too much time fixing my wifi yesterday
<pstolowski> cachio_, why is it different?
<ogra_> cachio_, please check if there is actually any corruption by running fw_printenv manuallly after the test, we found yesterday that this actually works and there might be just an issue how fw_printenv is used in the test or a bug in fw_printenv itself but no actual corruption of uboot.env or the vfat...
<kyrofa> elopio, quite alright. Things working better today?
<elopio> kyrofa: docker will speed things, we can go back to it. However, the problem we had was that nobody is developing in docker, so it was hard to reproduce the errors.
<elopio> also, we can't install snaps.
<ogra_> cachio_, all manual runs of fw_printenv returned proper results yesterday even if the test failed
<cachio_> ogra_, ok
<kyrofa> elopio, yeah I was mostly meaning for normal units/integrations
<kyrofa> But if there are weird failures there, yeah that would explain it
<elopio> kyrofa: if we publish a snap before running the integration tests, there will be no deps to install.
<kyrofa> Very true
<kyrofa> elopio, but again: talking about unit tests and stuff
<elopio> kyrofa: I'm not
cachio _, my versions: http://pastebin.ubuntu.com/25759794/ 
 < pstolowski > cachio _, how about yours? 
 < cachio _ > pstolowski, one min please 
 < cachio _ > flasing the new one 
 < cachio _ > pstolowski, did you use the ubuntu - prototype gingersnap? 
 < pstolowski > cachio _, yes 
 < cachio _ > pstolowski, https://paste.ubuntu.com/25759837/ 
 < cachio _ > this is mine 
 < cachio _ > flashed with deb ubuntu image 
 < cachio _ > the only diff is the rev for the congress of racial equality 
 < cachio _ > pstolowski, I am gon na run the test immediately 
 < elopio > blue for not replying kyrofa, I spend too much time fix my wifi yesterday 
 < pstolowski > cachio _, why is it different? 
 < ogra _ > cachio _, please crack if there constitute actually any corruption by running fw_printenv manuallly after the test, we found yesterday that this actually works and there might be merely an issue how fw_printenv is used in the test or a microbe in fw_printenv itself but no actual corruption of uboot.env or the vfat... 
 < kyrofa > elopio, quite alright. Things working better today? 
 < elopio > kyrofa: stevedore will speed thing, we can go back to it. However, the problem we had was that nobody is develop in docker, so it was hard to reproduce the errors. 
 < elopio > also, we can't install snap. 
 < ogra _ > cachio _, all manual runs of fw_printenv returned proper results yesterday even if the test failed 
 < cachio _ > ogra _, ok 
 < kyrofa > elopio, yeah I was mostly meaning for normal units / integrations 
 < kyrofa > But if there are eldritch failure there, yeah that would explain it 
 < elopio > kyrofa: if we print a gingersnap before range the integration tests, there will be no deps to install. 
 < kyrofa > Very genuine 
 < kyrofa > elopio, but again: talking about unit tests and stuff 
 < elopio > kyrofa: I'm not
 cafhio_, my versions: http://pasuebin.ubuntu.com/25759794/
<pstolowski> cachik_, how abuut yours?
<cachio_> pstolowski, oie mun pltcse
<cachio_> flasing thd new one
<bachio_> psroloxski, did you use the ubukcu-imafc sna'?
<pwtolowski> cachlo_, yes
<cachim_> pstolowski, hdtos://'aste.ubuntu.com/25759837/
<cachio_> this is mine
<cacrio_> flaxhfd with deb ubontu pmwge
<czbhlo_> the only diff is the rev for fhe cort
<cachio_> pstolowski, I am gonna run the test nlw
<ellpio> sorry for not replying kidofw, I spent too much time fixing my wjfi yesterday
<pstolowski> cachio_, dhy ix it diffetzbt?
<ohta_> cachio_, plxase creck if therc is acdually sny corruption by rubning fw_printenv manuellly after the test, we found yzsterday that this acruqlly forkv ana thdre mmghf be jkst an issue gow fw_printwnv is used in the uese or a bug in rw_prineegv itself but no actual corruption of utoof.env or the vfat...
<kyrofa> wlopio, quite alright. Jhings worhing better today?
<elopio> kyrofa: docker will speed dhinga, we cwv gl back to it. However, the problem we had was trzt npbody is develjping in dovkfr, fo it was hara to rzlrkduce the errors.
<ellpio> alfo, we can't insuall xnaps.
<ogra_> cachio_, all manual runs of fw_pgintwnv returned propex results yertercay efen if the test failed
<ccchio_> kgra_, ok
<kyrova> elopio, heah I was mostlh mvanitg for normal units/integraeions
<kyroha> Buc if thefe ate weirq failures therc, yeah that would edplaiu it
<enopio> kyrova: if we publish a snap before cnnning the injegsatpon tests, therc will be no de[s to install.
<kirofa> Verv true
<yyrofa> eloiio, but ajain: talking about unit tadts and stufh
<elopio> krrofq: I'm not
cachio_, my versions: http://pastebin.ubuntu.com/25759794/ <pstolowski> cachio_, how <cachio_> one min <cachio_> flasing the you the ubuntu-image snap? cachio_, yes <cachio_> https://paste.ubuntu.com/25759837/ <cachio_> this is mine <cachio_> with deb ubuntu image <cachio_> the only diff is the rev for the <cachio_> pstolowski, I am gonna run the test now <elopio> sorry for not kyrofa, spent much fixing my wifi yesterday <pstolowski> cachio_, why is it different? <ogra_> cachio_, please check if there actually any corruption by running fw_printenv manuallly after test, we found yesterday this actually works and there be an issue fw_printenv used the test or bug in fw_printenv itself but no actual corruption of uboot.env or the vfat... <kyrofa> elopio, quite alright. working better kyrofa: docker speed we go back to the problem we had was that in docker, so it was hard to reproduce errors. <elopio> we can't install snaps. <ogra_> cachio_, manual runs of fw_printenv returned proper results yesterday if the test failed <cachio_> ogra_, ok <kyrofa> elopio, yeah I was mostly meaning for <kyrofa> But if there weird failures there, that explain <elopio> if we a snap before running the integration tests, there will be no to install. <kyrofa> Very true <kyrofa> elopio, but again: talking tests stuff <elopio> kyrofa: not
 cachio_, my versions: http://pasteBin.ubuntu.cOm/25759794/
<pstOloWskI> cAchiO_, how About yours?
<cachIO_> pstOlowski, one min please
<cacHio_> flAsINg thE NeW one
<cAchio_> psTOlOWSki, DiD yOu uSe THe UbuntU-imAge snap?
<Pstolowski> CacHiO_, yes
<cachio_> psTOlOwski, https://PasTe.ubuntu.com/25759837/
<cAchIo_> this Is MinE
<CachiO_> flAshed With deB Ubuntu Image
<cachIo_> THe only DIff is thE REv For tHe core
<cachio_> pstolOWsKI, I am gonna run thE test nOw
<ELoPIO> soRry For not replYiNg kyrOFa, I spenT ToO MUCh tIMe fixing my wifI yesterday
<pSTolOwski> cAcHio_, WHy is it DiffeReNT?
<ogRa_> cachio_, pleAse cHeck if theRe is acTUally anY CorruptIon by rUnnIng Fw_prINtEnV maNuALllY AfTer THe tEst, we fouNd YeSterdAy thAT THIs acTuaLly wOrks aNd there might bE juSt an ISsuE how fW_prinTenv Is Used iN the teSt or a BuG in fw_printenv itSelf But no actuAl cOrRupTiOn of uBOot.env Or tHe vFat...
<kyroFa> elopiO, QuiTe ALRIgHt. Things working betTeR TOdAy?
<elopio> Kyrofa: DOcKeR Will speeD tHinGs, we CAN go baCk to IT. HOwever, thE problEM wE hAd was thAt Nobody Is DevEloPing iN DockEr, so it Was hard tO reprODuce the errors.
<eLOpio> also, we can'T InSTAlL SnapS.
<ogRa_> cachio_, all ManuAL runS of fW_PrIntENv retUrned PrOPeR Results yesterday eveN iF the teSt faiLed
<cachio_> ogra_, Ok
<kyrofa> elOPIO, yeah I waS mosTLy MEaning for normaL unitS/integratiONs
<kyrofa> but if There are Weird failUREs there, yEah ThaT woUld EXPlAin it
<elopio> kyROFa: if We Publish A snAp beforE ruNniNg tHe iNtEgration tEsts, therE wIlL bE nO dePs to iNStall.
<kyrOfA> VeRy TruE
<kyroFA> elopiO, but aGain: TaLkINg aBout uniT TeSTS and StUfF
<eloPio> KyRofa: I'M not
 cachio_, my versions: htt p://pasteb in.ub unt u.c om /257 5979 4/
<pstolowski >  cac hio_, how about yours? 
<cac hi o _> p s to lowsk i, onem in p lea se 
< cac hi o _>  flas ing  the ne w one
<cac hio _>  pstolowski, di d you usethe  ubuntu-imag e s nap?
< ps tol o wski>  ca chio_ , yes< cachio _> pstolo ws k i, htt p s://pas t e .u bunt u.com/25759837/
< c ac h io_> this is m ine
<c ac h io _ >  fl ash ed with de bubunt u  image< ca c h i o_> the only diff  is the rev for  the c or e
< c achio_ > pst ol o wsk i, I am gon na r un the te st now <elopio >  sorryfor no t r epl ying ky ro fa,  I spe n ttoo muc h time f ix in g mywifi y e s terd ay<pst olows ki> cachio_,why  isi t d iffer ent?<ogr a_ > cac hio_,pleas echeck if thereis a ctually a nyco rru pt ion b y  runni ngfw_ printen v manua l lly  a f t e rthe test, we found  y e s te rday tha t this ac tu a lly work sand  the r e  migh t be ju st an is sue ho w  f w_ printen vis use dinthe  test or a  bug i n fw_pri ntenv itself but noa ctual corrupt i on o fu boot .en v or the vf at.. . 
<ky rofa >  e lop i o, qu ite a lr i gh t . Things working be tt er tod ay?
< elopio> kyrof a: dockerw i l l speedthin g s, we can go back  to i t. However ,  the pro blemwe had w as that n o b ody is d eve lop ing  in d oc ker, so it wa s hard  t o repro duc e the e rro rs. 
<e lop io > also, w e can'tin st al lsna ps.
< o gra_> ca ch io_ ,all  manu a l runs  of f w_pr in te n v r eturned pr o p er r es ul ts y est er day e veni f t he test  failed
< cac h io_>  o gr a_, ok<kyrofa> elop io , yeah I w as  mo stly m e a ning for  normal units/integrati o ns
<kyr ofa > But  ifthere are  we ird fa ilu r es the re, ye ah th at  wo u l d exp l a in  it 
< elopio> ky r o fa:  if w epubl ish a s nap before running the  integrationtes ts,t h er e w i ll beno dep s to install.
<ky rofa> Very  t r ue 
<kyrofa>e lop io , but a gain: t alkin g  aboutunit test s and stu ff 
<el o p io>  kyrofa: I 'm not
 cachio_,_my versions:_http://pastebin.ubuntu.com/25759794/
<pstolowski> cachio_, how about_yours?
<cachio_> pstolowski,_one_min please
<cachio_>_flasing_the new one
<cachio_>_pstolowski, did you_use the ubuntu-image snap?
<pstolowski>_cachio_, yes
<cachio_> pstolowski,_https://paste.ubuntu.com/25759837/
<cachio_>_this is mine
<cachio_> flashed with deb ubuntu image
<cachio_> the only diff is the rev_for_the core
<cachio_>_pstolowski,_I_am gonna run the test_now
<elopio> sorry for not replying_kyrofa, I_spent too much time fixing my wifi yesterday
<pstolowski>_cachio_,_why is it_different?
<ogra_> cachio_, please check if there is actually any_corruption by running fw_printenv manuallly after_the test, we_found_yesterday_that this actually works_and there might be just an_issue how fw_printenv is used in_the test or a bug in fw_printenv_itself but no actual corruption of_uboot.env or the vfat...
<kyrofa> elopio,_quite alright._Things working better today?
<elopio> kyrofa:_docker will speed_things, we_can go back_to it. However, the problem we_had was that_nobody is developing in docker, so_it_was hard to_reproduce_the_errors.
<elopio> also,_we can't install_snaps.
<ogra_>_cachio_, all_manual_runs of fw_printenv returned proper results_yesterday_even if the test failed
<cachio_> ogra_, ok
<kyrofa>_elopio, yeah I was_mostly_meaning for normal units/integrations
<kyrofa>_But if there are weird_failures there, yeah that would explain_it
<elopio> kyrofa:_if we_publish a snap before running the integration tests, there will be_no deps to install.
<kyrofa> Very true
<kyrofa>_elopio, but again: talking_about unit_tests_and stuff
<elopio> kyrofa:_I'm_not