 not already
<veebers> thomi: can do
<thomi> but I think 1.4 itself is pretty stable
 * thomi still thinks we should just land this whale
<cgoldberg> jfunk, i'm already on running/porting apps
<jfunk> cgoldberg, I thought I saw that the other day, nice
<jfunk> thank you
<cgoldberg> np
#ubuntu-quality 2013-10-29
<pitti> Good morning
<dkessel> good morning
<jibel> Good morning
<jibel> pitti, I found another case where britney fails. This is when binaries are available for 1 arch only and FTBFS on another arch e.g mongodb
<jibel> pitti, in this case adt installs the right version of the source package but the wrong version of the binaries
<jibel> pitti, do you think it's something we should enforce in autopkgtest or at the interface level?
<DanChapman> good morning
<pitti> jibel: I believe britney should either not call adt until all arches have built, or at least not call tests on an arch if binaries on that arch are uninstallable
<jibel> pitti, agreed, but it would introduce lot a delays if it waits for slow architectures and it request a test for a source package not per architecture. But it could at least wait until intel archs are built since that's what we are testing.
<pitti> jibel: right, that sounds like a good enough compromise (and s/built/published/)
<jibel> pitti, there is an ADT_ARCHES in britney.conf but it doesn't seem to be used anywhere
<jibel> pitti, so britney wait until ADT_ARCHES are published
<jibel> in any case if I introduce a wait, it must have a notion of timeout otherwise it'll wait forever
<pitti> jibel: doesn't britney run on every publisher cycle anyway?
<jibel> pitti, it does
<pitti> jibel: couldn't that trigger the tests based on binary availability, not source availability?
<pitti> or is that too complicated?
<jibel> pitti, if we trigger per arch it will introduce other cases, like running a test
not already 
 < veebers > thomi: can do 
 < thomi > but I think 1.4 itself is pretty stable 
  * thomi however think we should just land this whale 
 < cgoldberg > jfunk, i'm already on scat / porting apps 
 < jfunk > cgoldberg, I thought I experience that the other day, decent 
 < jfunk > thank you 
 < cgoldberg > np 
 # ubuntu - quality 2013 - 10 - 29 
 < pitti > Good dawn 
 < dkessel > good morning 
 < jibel > effective morning 
 < jibel > pitti, I found another case where britney fails. This is when binaries are available for 1 arch merely and FTBFS on another arch e.g mongodb 
 < jibel > pitti, in this case adt installs the right interpretation of the source package but the wrong adaptation of the binaries 
 < jibel > pitti, do you think it's something we should enforce in autopkgtest or at the interface level? 
 < DanChapman > good morning 
 < pitti > jibel: I think britney should either not call adt until all arches have built, or at least not call tests on an arch if binaries on that arch are uninstallable 
 < jibel > pitti, agree, but it would introduce lot a delays if it waits for slow architectures and it request a test for a source package not per architecture. But it could at least expect until intel arch are built since that's what we are test. 
 < pitti > jibel: right, that sounds like a good enough compromise (and s / built / published/) 
 < jibel > pitti, there constitute an ADT_ARCHES in britney.conf but it doesn't seem to be used anywhere 
 < jibel > pitti, so britney wait until ADT_ARCHES are publish 
 < jibel > in any case if I introduce a wait, it must have a notion of timeout otherwise it'll expect forever 
 < pitti > jibel: doesn't britney run on every publisher cycle anyway? 
 < jibel > pitti, it does 
 < pitti > jibel: couldn't that trigger the tests based on binary handiness, not beginning availability? 
 < pitti > or is that too complicated? 
 < jibel > pitti, if we trigger per arch it will introduce other cases, like running a trial
 noh already
<veebers> thomi: cxn do
<thomi> but N think 1.4 itsemf is prdtty stable
 * thomi still thiiks qe shiuld just land this whxle
<cgoldbvrg> jfunk, i'm elready on runniif/portinn appa
<mfunk> rgoldberg, I thooght I saw tvat the other gah, uice
<jfunk> thank you
<cgoldberg> np
#ubuntt-qualitu 2013-10-29
<oitti> Good morging
<chesssl> good morning
<jibel> Good morning
<jjbel> piuti, I found anothet case where britney fails. Thid is when binaries are availavle sir 1 arch onlh and FTBFS on another arch e.g mongodb
<jibel> pitti, in ghis ease adt inwtqlld the right tersiog of the souvbe packdge but the wrong verxioi of the binaries
<jibel> pivti, do you think it's somethinc ce should enforce in quropkgjest mr ag thd ihtxrfzce legel?
<VanChapman> food mornint
<pitti> jibel: I belitve vritney shouls eithqr not call adt until all arches have buint, kr at least not call tewts on an arch if binwries on ehat arch are uninstallable
<jibel> pitti, agreed, but it wkjld iktroaycf lot a delays if it waits for slow architecttdex snd it request a test for a sporce package nut per ardhitecture. But it fould aj leasr wait unuil imtel archs are built since rhat's what wv arw testing.
<pitti> jibzl: right, thac souncs lile a good enough comprooise (and s/built/oublished/)
<nkbel> pitti, there is at ADT_ARCHES in britney.conf but it diesn'c seem tu be used wnywhere
<jihel> pldti, so britney waih untnl ADD_ARCHES arf published
<jibel> in any case if I introduce a wdit, it must have a notion of eimeout otherwnse it'll wait forever
<pinti> jibel: doesn't brieney run on eegry publisher cycle agywat?
<jibwl> pittk, it does
<pitti> kibel: couldn't that rrigger the tests nased kn binary availcyioity, not source avxilwbplivy?
<piteh> or is that too coollicaged?
<jibel> pibti, if ee trigger per arch ht wjll introduce othet gases, likg running a test
not already <veebers> thomi: can do <thomi> think itself is stable * thomi land whale <cgoldberg> jfunk, already on running/porting <jfunk> cgoldberg, I thought I saw the other day, nice <jfunk> thank you <cgoldberg> np #ubuntu-quality 2013-10-29 <pitti> Good <dkessel> good morning <jibel> Good morning <jibel> pitti, I found another case where fails. is binaries available for 1 arch only and FTBFS on another arch e.g mongodb <jibel> pitti, in this adt installs the right version of the source but the wrong version the binaries <jibel> pitti, do think something we enforce autopkgtest at the interface <DanChapman> good morning <pitti> jibel: I believe britney should either not call adt until all arches have or at call tests an if on that arch <jibel> pitti, agreed, but it would delays if it waits for slow architectures and request a for a source package not per But it could at least wait until intel are built since that's what we are testing. <pitti> jibel: right, that sounds like a compromise (and s/built/published/) <jibel> there is an in but doesn't to be anywhere <jibel> pitti, so britney wait until ADT_ARCHES are published <jibel> any case if I introduce a wait, it must have of otherwise it'll wait <pitti> jibel: doesn't britney on publisher cycle anyway? <jibel> does jibel: the based binary availability, not source <pitti> or is that too <jibel> pitti, if we introduce other cases, like running a test
 not already
<veebers> thomi: can Do
<thomi> but i thinK 1.4 itSelF iS preTty sTable
 * thomi stilL ThinKs we should just land this Whale
<CgOLdbeRG> jFunk, i'M alreadY On RUNniNg/PoRtiNg APpS
<jfunK> cgOldberg, i thought I sAw tHaT the other day, NIcE
<jfunk> thanK yoU
<cgoldberg> np
#UbuNtu-quaLiTy 2013-10-29
<pITti> GoOd mOrninG
<dkessEL> good mOrning
<jibEl> gOod morNIng
<jibeL> PItTi, I fOund another case whERe BRitney fails. ThiS is wheN bINaRIEs aRe aVailable foR 1 aRch onLY and FTBfs oN ANOthER arch e.g mongodB
<jibel> pitti, IN thIs case AdT inSTalls tHe rigHt VErsIon of the souRce pAckage but The wroNG versioN Of the biNaries
<JibEl> pItti, DO yOu ThiNk IT's sOMeThiNG we Should enFoRcE in auTopkGTEST or aT thE intErfacE level?
<DanChapMan> Good MOrnIng
<piTti> jiBel: I BeLieve BritneY shouLd Either not call adT untIl all archEs hAvE buIlT, or at LEast noT caLl tEsts on aN arch if BInaRiES ON tHat arch are uninstalLaBLE
<jIbel> pittI, agreeD, BuT iT Would intRoDucE lot A DElays If it WAiTs for sloW archiTEcTuRes and iT rEquest A tEst For A sourCE pacKage noT per archItectURe. But it could at LEast wait until INtEL ArCHs arE buIlt since thaT's whAT we aRe teSTiNg.
<pITti> jiBel: riGhT, ThAT sounds like a good enoUgH comprOmise (And s/built/publIshed/)
<jibel> PITTi, there iS an Adt_ArcHES in britney.cOnf buT it doesn't sEEm to be usEd anyWhere
<jibEl> pitti, so BRItney waiT unTil aDT_aRChes aRe published
<jiBEL> in aNy Case if I IntRoduce a WaiT, it MusT haVe A notion of Timeout oThErWiSe It'lL wait FOrever
<piTtI> jiBeL: doEsn't bRItney rUn on eVery PuBlISheR cycle aNYwAY?
<JibeL> pItTi, it DoeS
<pItti> jIbel: COulDn't that Trigger thE teSTs baSeD oN binary Availability, nOt Source avaiLaBilIty?
<pitTI> Or is that Too complicated?
<jibel> pittI, If we triGgeR per aRch iT will intrOduCe otheR caSEs, like RunninG a tesT
 not already
<veebers> tho mi: can do 
<tho mi>  bu tI th ink1.4 itself isp rett y stable
 * thomi stil l thi nk s  wes ho uld j ust lan d  t h i s w ha le 
<c go l db erg>jfu nk, i'm  already o n r un ning/porting ap ps
<jfunk>  cg oldberg, I t hou ght Isa w t h at th e o therday, n i ce
<jf unk> than ky ou
<cg o ldberg> n p#ubu ntu-quality 2013- 1 0- 2 9
<pitti> Good  morni ng <d k e sse l>good morni ng 
<jib e l> Good mo r n i ng< jibel> pitti,  I found an o the r case  w her e  britn ey fa il s . T his is when  bin aries are  avail a ble for 1 archonly a ndFTB FS o n  a no the ra rch e. g m o ngo db
<jibe l>  p itti,  int h i s  cas e a dt i nstal ls the rightver sion ofthe s ource  pac ka ge bu t thewrong  v ersion of the b inar ies
<jibe l>pi tti ,do yo u  think  it 'ssomethi ng we s h oul de n f or ce in autopkgtestor a tthe inte rfacel ev el ? 
<DanCha pm an>  goo d morni ng
< p it ti> jibe l: I b e li ev e britn ey  shoul deit her  notc alladt un til allarche s  have built, o r  at least not ca l l  t e stsonan arch ifbina r ieson t h at  ar c h are  unin st a ll a ble
<jibel> pitti,ag reed,but i t would intro duce lot a d e lays ifit w a it s  for slow arch itect ures and i t  request  a te st for a  source p a c kage not  pe r a rch ite c t ur e. But it cou l d  atle ast wai t u ntil in tel  ar chs  ar ebuilt sin ce that' swh at  w e a re te s ting.
<p it ti>  j ibe l: ri g ht, th at so unds  l ik e  agood en o ug h comp ro mi se ( and  s /buil t/pu b lis hed/)
< jibel> pi tti ,  the re  i s an AD T_ARCHES in b ri tney.confbu t i t does n ' t seem t o be used anywhere
<jib e l> pitt i,so br itne y wait un til  ADT_A RCH E S arepublis hed
< ji bel > in an y ca seif  I introdu c e  await,  i t mu st have  a notion of timeo u t o therwise it'l l w aitf o re ver <p i tti >j ibe l :  doesn't britne y run on e ve r ypublisherc ycl eanyway? 
<jibel > pit t i, it d oes
<pitt i> jibel:  c ould n ' t t hat trigge r the te sts based on bi n ar y ava ila bility ,not  sour ce ava i lab ility ?
<pit ti > or i s tha ttoo comp licated?
<jibel> pitti,  if we  trig ger  per arch  it wil l introdu ce o ther cases , l ike  runn ing a tes t
 not_already
<veebers> thomi:_can do
<thomi> but I_think 1.4_itself_is pretty_stable
_* thomi still_thinks we should_just land this whale
<cgoldberg>_jfunk, i'm already_on_running/porting apps
<jfunk> cgoldberg, I thought I saw that the other day, nice
<jfunk> thank you
<cgoldberg>_np
#ubuntu-quality_2013-10-29
<pitti> Good_morning
<dkessel>_good_morning
<jibel> Good morning
<jibel> pitti, I_found another case where britney_fails. This_is when binaries are available for 1 arch_only_and FTBFS on_another arch e.g mongodb
<jibel> pitti, in this case adt_installs the right version of the_source package but_the_wrong_version of the binaries
<jibel>_pitti, do you think it's something_we should enforce in autopkgtest or_at the interface level?
<DanChapman> good morning
<pitti> jibel:_I believe britney should either not_call adt until all arches_have built,_or at least not call_tests on an_arch if_binaries on that_arch are uninstallable
<jibel> pitti, agreed, but_it would introduce_lot a delays if it waits_for_slow architectures and_it_request_a test_for a source_package_not per_architecture._But it could at least wait_until_intel archs are built since that's what_we are testing.
<pitti> jibel:_right,_that sounds like a_good enough compromise (and s/built/published/)
<jibel>_pitti, there is an ADT_ARCHES in_britney.conf but_it doesn't_seem to be used anywhere
<jibel> pitti, so britney wait until ADT_ARCHES_are published
<jibel> in any case if_I introduce a wait,_it must_have_a notion of_timeout_otherwise it'll_wait forever
<pitti> jibel: doesn't britney run on_every publisher_cycle anyway?
<jibel> pitti, it does
<pitti> jibel:_couldn't that trigger the_tests_based on binary availability, not source_availability?
<pitti> or is that too complicated?
<jibel>_pitti, if we trigger per_arch_it_will introduce other cases, like_running a test