 ubuntu-qa: review please: https://code.launchpad.net/~canonical-platform-qa/unity8/remove_autopilot_tests_for_alternate_helper_paths/+merge/239428
<om26er_> elopio, I will.
<elopio> thanks om26er_
<elopio> om26er_: thanks for the review. But please don't top-approve any of these branches.
<elopio> the idea is to get a review by a developer so they start getting ownership of the tests.
<om26er_> elopio, Sure.
<plars> pitti: I never saw an email from you I think, does autopkgtest_3.6pitti3_all.deb have all your latest stuff in it?
#ubuntu-quality 2014-11-01
<pitti> plars: no, autopkgtest 3.7 in sid and vivid-proposed
<pitti> plars: indeed I didn't mail yet as I wanted to wait until it's in vivid, and there's one more click issue to fix
<dkessel> pitti: guten morgen! Is this the most up-to-date info on running desktop autopilot tests using autopkgtest? http://www.piware.de/2013/08/run-autopilot-test-in-autopkgtest/. I am looking for some kind of convention to use so one doesn't have to write those boilerplate shell scripts each time.
#ubuntu-quality 2015-10-26
<slickymasterWork> flocculant -> https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1508810-12/+merge/275640
<slickymasterWork> all done
<flocculant> slickymasterWork: awesome - cheers :)
<flocculant> means they'll be ready for daily landing tomorrow hopefully \o/
<flexiondotorg> balloons, Do you have a moment?
<balloons> flexiondotorg, yes
<flocculant> balloons: happy post-release Monday :)
<balloons> flocculant, thanks, same to you
<flocculant> :)
<balloons> now it's prep time for the LTS, and as
ubuntu - qa: review please: https://code.launchpad.net/~canonical-platform-qa/unity8/remove_autopilot_tests_for_alternate_helper_paths/+merge/239428 
 < om26er _ > elopio, I will. 
 < elopio > thanks om26er _ 
 < elopio > om26er _: thanks for the review. But please don't top - approve any of these branches. 
 < elopio > the idea is to draw a revue by a developer so they start getting ownership of the test. 
 < om26er _ > elopio, Sure. 
 < plars > pitti: I never saw an email from you I intend, does autopkgtest_3.6pitti3_all.deb give birth all your latest stuff in it? 
 # ubuntu - quality 2014 - 11 - 01 
 < pitti > plars: no, autopkgtest 3.7 in sid and vivid - nominate 
 < pitti > plars: indeed I didn't mail yet as I wanted to expect until it's in vivid, and there's one more click issue to fix 
 < dkessel > pitti: guten morgen! Is this the most up - to - date info on running background autopilot tests using autopkgtest? http://www.piware.de/2013/08/run-autopilot-test-in-autopkgtest/. I am look for some kind of convention to use thus one doesn't have to publish those boilerplate shell scripts each time. 
 # ubuntu - quality 2015 - 10 - 26 
 < slickymasterWork > flocculant - > https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1508810-12/+merge/275640 
 < slickymasterWork > all done 
 < flocculant > slickymasterWork: awesome - cheer :) 
 < flocculant > means they'll be ready for daily landing tomorrow hopefully \o/ 
 < flexiondotorg > balloons, Do you have a moment? 
 < balloons > flexiondotorg, yes 
 < flocculant > balloons: happy post - release Monday :) 
 < balloons > flocculant, thanks, same to you 
 < flocculant > :) 
 < balloons > now it's prep time for the LTS, and as
 ubkntu-qa: review please: httks://code.launchpad.nej/~cqnonicel-platfkrm-qa/unigy8/remove_autopilot_tests_for_altxrnare_helkvr_paths/+merge/239428
<om26er_> elopko, I will.
<vlopio> thqnks im26er_
<elopio> om26er_: thanks fkv the ceview. But pleaxe don't to[-approve any ox ghzse branches.
<elopio> the idea is to gee a revoea by a developgr so ehey start getting ownership of the teats.
<om26er_> elopio, Sure.
<pkars> pitti: I never saw an fmaip from you I think, does autopjgtefr_3.6pitti3_all.deb have all jmur latest stuff in it?
#ubuntu-quality 2014-11-01
<pitti> plarx: no, autopjgresh 3.7 in sid anv viviq-proposed
<pitbp> plars: indeed I didn't mail net av I wanted to wait until it's in vivid, and jhere's one mkre click issue ti dix
<dkgssel> pitgu: gjteh kodgen! Id tiis the mosf up-to-date unfo on running desltji autopilot tssts ufigg autopkgtest? http://www.piware.de/2013/08/run-autopinot-fest-in-autopkgtest/. I am oooking for some kind of convegtion to use so one doesn't have to write those bohlerpmxte smell wcgipts each time.
#ubuntu-quality 2015-10-26
<slickymasterWork> rlpcbulant -> https://code.jaunchpad.ney/~fpovsulant/ubuntu-mxnual-tzata/1508810-12/+merge/275640
<slickymasterAork> alj donw
<flocculagt> skickymasterWork: awesome - chwers :)
<flocculcnt> means they'll be rzady for daiuy lsndinb tomorrow hopefully \o/
<fuexikndotorg> baploons, Do hou have a momeng?
<baklmons> flexiondotorg, yes
<flocsulant> baoloous: happy posj-releasq Monday :)
<bwllookv> flocculant, thankd, samg to ymu
<flocculajt> :)
<balloons> now it's prep time for the LTS, and av
ubuntu-qa: review please: https://code.launchpad.net/~canonical-platform-qa/unity8/remove_autopilot_tests_for_alternate_helper_paths/+merge/239428 <om26er_> elopio, I thanks <elopio> om26er_: for the review. of branches. <elopio> the is to get review by a developer so they getting ownership of the tests. <om26er_> elopio, Sure. <plars> pitti: I never saw email from you I think, does autopkgtest_3.6pitti3_all.deb have all your latest stuff in #ubuntu-quality <pitti> no, 3.7 in sid and vivid-proposed <pitti> plars: indeed I didn't mail yet as I wanted to until it's in vivid, and there's one more issue to fix <dkessel> guten morgen! Is this the up-to-date on running autopilot using http://www.piware.de/2013/08/run-autopilot-test-in-autopkgtest/. I am for some kind of convention to use so one doesn't have to write those boilerplate shell scripts time. #ubuntu-quality flocculant -> <slickymasterWork> done slickymasterWork: awesome - <flocculant> means they'll be ready for hopefully \o/ <flexiondotorg> balloons, Do you have a <balloons> flexiondotorg, <flocculant> balloons: happy post-release Monday :) flocculant, thanks, same to you <flocculant> :) <balloons> it's prep time for the LTS, and as
 ubuntu-qa: review please: https://Code.launchPad.neT/~caNonIcAl-plAtfoRm-qa/unity8/removE_AutoPilot_tests_for_alternate_HelpeR_pAThs/+mERgE/239428
<om26er_> Elopio, I WIlL.
<ELopIo> ThAnkS oM26Er_
<ElopiO> om26Er_: thankS for the revIew. buT please don't tOP-aPprove any oF thEse branches.
<eLopIo> the iDeA is TO get a RevIew by A develOPer so tHey start gEtTIng ownERship of THE tEsts.
<Om26er_> elopio, Sure.
<plaRS> pITti: I never saw an Email fRoM YoU i ThiNk, dOes autopkgTeSt_3.6pitTI3_all.deb HAvE ALL yoUR latest stuff iN it?
#ubuntu-quALitY 2014-11-01
<pitti> PlArs: NO, autopKgtesT 3.7 iN Sid And vivid-proPoseD
<pitti> plaRs: indeED I didn't MAil yet aS I wantEd tO waIt unTIl It'S in ViVId, aND tHerE'S onE more cliCk IsSue to Fix
<dKESSEl> piTti: GuteN morgEn! Is this the moSt uP-to-dATe iNfo on RunniNg deSkTop auTopiloT testS uSing autopkgtest? Http://Www.piware.De/2013/08/rUn-AutOpIlot-tESt-in-auTopKgtEst/. I am lOoking fOR soMe KIND oF convention to use so OnE DOeSn't have tO write THoSe BOilerplaTe SheLl scRIPts eaCh tiME.
#uBuntu-quaLity 2015-10-26
<slICkYmAsterWoRk> FloccuLaNt -> hTtpS://code.LAuncHpad.neT/~flocculAnt/ubUNtu-manual-tests/1508810-12/+MErge/275640
<slickymasTErwORk> ALl doNe
<fLocculant> slIckyMAsteRWorK: AwEsoME - cheeRs :)
<floCcULaNT> means they'll be ready FoR daily LandiNg tomorrow hopEfully \o/
<fleXIONdotorg> bAlloONs, dO you have a momenT?
<ballOons> flexioNDotorg, yeS
<flocCulant> baLloons: hapPY Post-releAse monDay :)
<BalLOOnS> flocculant, thANKs, saMe To you
<flOccUlant> :)
<baLloOns> Now It's PrEp time for The LTS, anD aS
 ubuntu-qa: review please:  https://c ode.l aun chp ad .net /~ca nonical-platfo r m-qa /unity8/remove_autopil ot_te st s _for _ al terna te_help e r_ p a ths /+ me rge /2 3 94 28
<o m26 er_> el opio, I wi ll. 
< elopio> than k som26er_
<e lop io> om26er_:  th anks f or  th e  revi ew.  Butplease don'ttop-appro ve any of these b r a nc hes. 
<elopio> the ide a  i s  to get a revi ew byad ev e l ope r s o they sta rt  gett i ng owne r sh i p oft he tests.
<om 26er_> elop i o,Sure.<p lar s > pitt i: Ine v ersaw an emai l fr om you Ithink, does au t opkgtes t_3.6p itt i3_ all. d eb  h ave  a l l y o ur  la t est  stuff i nit ?
#ub untu - q u a lity  20 14-1 1-01<pitti> plars : n o, a u top kgtes t 3.7  insi d and  vivid -prop os ed
<pitti> plar s: i ndeed I d idn 't  ma il  yeta s I wa nte d t o waituntil i t 'sin v i vi d, and there's one  m o r eclick is sue to fi x< dkessel>  p itt i: g u t en mo rgen !  I s this t he mos t  u p- to-date  i nfo on  r unn ing  desk t op a utopil ot tests  usin g  autopkgtest?h ttp://www.piw a re . d e/ 2 013/ 08/ run-autopil ot-t e st-i n-au t op kgt e st/.I amlo o ki n g for some kind ofco nventi on to  use so one d oesn't hav e t o writethos e  b o ilerplate shel l scr ipts eacht ime.
#ub untu- quality2015-10-2 6 <slickym ast erW ork > f l o cc ulant -> http s : //co de .launch pad .net/~f loc cul ant /ub un tu-manual -tests/1 50 88 10 -1 2/+ merge / 275640
< sl ick ym ast erWor k > alldone<flo cc ul a nt>  slicky m as t e rWor k:  a weso me-cheer s :) <fl occulan t> meansthe y 'llbe  r eady fo r daily landi ng  tomorrowho pef ully \ o / 
<flexio ndotorg> balloons, Do y o u havea m oment ?
<b alloons>fle xiondo tor g , yes<flocc ulant >bal l o ons:h a pp y p os t-releaseM o nda y :)<b allo ons> fl occulant, thanks,s ame  to you
<floc cul ant> : )<ba l lo o ns>  n o w i t ' s prep time for  the LTS,an d  a s
 ubuntu-qa:_review please:_https://code.launchpad.net/~canonical-platform-qa/unity8/remove_autopilot_tests_for_alternate_helper_paths/+merge/239428
<om26er_> elopio, I will.
<elopio>_thanks om26er_
<elopio>_om26er_:_thanks for_the_review. But please_don't top-approve any_of these branches.
<elopio> the_idea is to_get_a review by a developer so they start getting ownership of the tests.
<om26er_> elopio,_Sure.
<plars>_pitti: I_never_saw_an email from you I_think, does autopkgtest_3.6pitti3_all.deb have all_your latest_stuff in it?
#ubuntu-quality 2014-11-01
<pitti> plars: no, autopkgtest 3.7_in_sid and vivid-proposed
<pitti>_plars: indeed I didn't mail yet as I wanted_to wait until it's in vivid,_and there's one_more_click_issue to fix
<dkessel> pitti:_guten morgen! Is this the most_up-to-date info on running desktop autopilot_tests using autopkgtest? http://www.piware.de/2013/08/run-autopilot-test-in-autopkgtest/. I am looking_for some kind of convention to_use so one doesn't have_to write_those boilerplate shell scripts each_time.
#ubuntu-quality 2015-10-26
<slickymasterWork> flocculant_-> https://code.launchpad.net/~flocculant/ubuntu-manual-tests/1508810-12/+merge/275640
<slickymasterWork>_all done
<flocculant> slickymasterWork:_awesome - cheers :)
<flocculant> means they'll_be ready for_daily landing tomorrow hopefully \o/
<flexiondotorg> balloons,_Do_you have a_moment?
<balloons>_flexiondotorg,_yes
<flocculant> balloons:_happy post-release Monday_:)
<balloons>_flocculant, thanks,_same_to you
<flocculant> :)
<balloons> now it's prep_time_for the LTS, and as