=== chihchun_afk is now known as chihchun
pittiGood morning05:49
jibelGood morning07:55
=== chihchun is now known as chihchun_afk
=== chihchun_afk is now known as chihchun
slickymastermorning all09:37
=== _salem is now known as salem_
=== salem_ is now known as _salem
davmor2Morning all11:00
slickymastermorning davmor211:03
=== chihchun is now known as chihchun_afk
=== _salem is now known as salem_
=== chihchun_afk is now known as chihchun
rbasakpitti, jibel: do you have any thoughts on adding armhf dep8 testing to -proposed migration gating, please? I presume you need hardware, of course, but if I could provide a suitable chassis, then are there any other implications to doing this?12:44
pittirbasak: we actuall had that running for a while, but tore it down again because it was too unreliable12:44
pittiat least at that time there was no suitable virtualization technology, and RAM/storage was too small even for LXC12:45
pittirbasak: with a Calxeda box that should probably work; do we have one available now?12:45
rbasakpitti: we may do. I'm trying to figure that out. What hardware were you running on before?12:45
pittirbasak: Panda boards12:46
rbasakI see.12:46
pittirbasak: I take it we'd start with adt-virt-lxc?12:46
pitti(as there's no qemu)12:46
rbasakI'm not sure. That's up for discussion, I guess.12:46
pittirbasak: I think tests without "Restrictions: needs-root" should probably mostly get along with lxc12:46
pittithings like udisks, upstart, or gvfs won't12:46
rbasakWe do have rudimentary qemu now I believe, but that would require an A15 box, and I'm not sure about availability of those.12:47
pittibut I think the majority of our tests don't need root, so having at least those covered by ARM would be great12:47
rbasakAn alternative would be to do bare metal, and reinstall every time. Depending on how many nodes are available that may not be too bad.12:47
pittirbasak: well, it's better to start small anyway; so if we have a box big enough to run lxc on, that'd already be something12:47
pittirbasak: no, we tried that, and it was maintenance hell12:47
pittithat's what we did with the panda12:47
rbasakI have had automated install running well and reliably on highbanks in the lab for years12:48
pittithose would be nice for running the needs-root tests, of course12:48
rbasakThis hardware needs to go into a dedicated lab, right? So it can't share resources with anywhere else?12:49
pittirbasak: I don't know much about the lab organization, I'm afraid12:49
rbasakWho do I need to ask about that?12:49
pittirbasak: my gut feeling is that having reliable network access to them is sufficient12:49
pittirbasak: retoaded and jibel are good people to talk about that, I think12:50
pittirbasak: that'd be great indeed12:50
rbasakIf remote, then do the nodes still need to be permanently allocated to Jenkins?12:50
rbasakOr is there any opportunity for a more dynamic mechanism?12:50
pittirbasak: also, I haven't yet tried running tests in the ubuntu emulator; that might also be worth a try at least for the no-root ones12:50
pittirbasak: I think you can add/remove executors to jenkins fairly dynamically; but again, that's jibel's area12:51
rbasakI think I can get you a suitable chassis or access to one. It's not certain yet, though, but I'd like to progress further with figuring out how this would work.12:51
pittirbasak: nice! thanks for that12:51
rbasakI'll wait for jibel to see this I guess. Thanks!12:52
jibelrbasak, autopkgtest have been running on pandaboards in LXC with external drives for a while. But they were constantly dying under load and required most of the time required manual intervention. Maintenance cost was clearly too high compared to the benefit.12:55
jibelif there is something more reliable why not12:55
pittiah, they already used lxc12:55
jibelrbasak, the other point is that we'll want to not gate everything on ARM testing because that'd would slow down the whole publication12:56
jibeland we'd need to be able to select which package to run on which architecture12:57
rbasakjibel: that makes sense. Is it possible to have a list of packages that we care about, and just test those?12:57
pittiI think at first we want to run all (non-root) tests but don't gate on them12:58
jibelrbasak, it is possible, but requires changes in the interface with britney12:58
pittito see how many tests need adjusting and how stable the system is12:58
jibelpitti, that's easy because it is how it was running before I disabled it12:59
rbasakjibel: OK, so what should we do next? If I get you a chassis, would that be useful, or would it need to sit unused while we sort out the infrastructure changes?12:59
rbasakjibel: also, does the chassis need to go to a particular lab, or is remote access OK?13:00
retoadedpitti, we do have a Calxeda available within the lab and have 4 nodes on it allocated for jibel13:00
retoadedpitti, with a possibility of allocating a few more if needed13:01
pittiretoaded: nice! I guess they are beefy enough to host one or two GB (temporarily)?13:01
retoadedpitti, should be13:01
retoadedpitti you can log into cyclops-node02 if you want to check one of the nodes out13:03
pittiretoaded: Host cyclops-node02.ubuntu-ci not found: 3(NXDOMAIN)13:04
pittiretoaded: I guess I need some other gateway?13:04
pittiretoaded: sorry, forgot to start VPN after reboot13:05
retoadedpitti, shouldn't. let me check it; may not have added the shotname cname value to DNS13:05
pittiretoaded: asks me for password13:05
retoadedpitti, ahhh, that could explain it too13:05
pittiretoaded: (as pitti)13:05
retoadedpitti, see PM13:05
pitti/dev/sda2        46G  1.6G   42G   4% /13:06
pittiholy crap, 42 GB? that's an ARM machine! :-)13:06
pitti/dev/sda3       409G   71M  388G   1% /data13:06
pittiretoaded: can I install lxc and autopkgtest on that, etc.?13:07
retoadedpitti, yep. that is one of the systems allocated to jibel so do what you want :-)13:08
pittiretoaded: so even dist-upgrade to saucy, or even trusty? (not sure how much maintenance their base systems get from you)13:08
pittiretoaded: sweet, thanks13:08
retoadedpitti, I haven't done anything with them since the base install13:08
retoadedpitti, you have node02 to node05 allocated atm13:09
pittirbasak, jibel: I'll set up cyclops-node02 for saucy, create a trusty LXC container on it and run a few autopkgtests to get a feeling13:09
pittiretoaded: ah, packages seem a bit broken, running apt-get -f install; is "reboot" safe?13:10
pitti(/boot is full, cleaning up a few old kernels)13:11
pittiretoaded: ok, reboot worked fine, and kernels cleaned up13:18
retoadedpitti, ack13:18
jibelretoaded, ah, I completely forgot this system, thanks for reminding me :)13:32
pittijibel: I'll fix and upgrade node03 in the meantime13:33
jibelretoaded, are we free to do what we want with these nodes and there is some kind of CI procedure to follow?13:33
WebbyITHey balloons :-)13:43
pittijibel, retoaded: meh, I'm afraid I already killed cyclops02 -- it seems it doesn't like the saucy kernel?13:48
pittisorry about that13:48
jibelpitti, ah, it wasn't long :)13:49
jibelrbasak, that's how it goes with testing on ARM ;)13:49
pittiI'll try and keep the raring kernel on cyclops0313:49
retoadedjibel, yes, you are completely free to do what you need with those 4 nodes13:50
rbasakWhat you want is a one-command "restore this machine" tool, that works out-of-band so doesn't care about the state of the machine.13:50
rbasakIMHO, this should be the case for any deployment anywhere. I wrote this for pandaboards and later extended to the highbanks. Then breaking a node no longer matters :)13:51
pitti$ fix-machine --boot-raring-kernel cyclops-node0213:51
rbasakPretty much, yeah. My command took URLs or paths to d-i kernel, initrd, kernel parameters, etc, ran expect on the serial console, and exited with a zero status on success.13:52
balloonshey WebbyIT14:23
WebbyITballoons, I hope you are fine :-) What's about https://code.launchpad.net/~sergiusens/ubuntu-calculator-app/cmake/+merge/202176?14:25
balloonsWebbyIT, using cmake is going to allow you to test easier using a new tool sergio wrote14:28
balloonshe used calculator as the test14:28
WebbyITballoons, interesting! So, I leave to you the honour to review it ;-)14:28
balloonsWebbyIT, :-) I'll leave some details about how it works14:29
WebbyITyeah, awesome, thanks!14:29
pittirbasak: hey, maybe you know: I dist-upgraded that arm node from raring to saucy, but I want it to boot with the raring kernel14:40
pittirbasak: i. e. I'd move the /boot/vmlinuz and initrd.img symlinks to the old kernel14:41
pittirbasak: do I need to run anything else to activate that, or will the boot loader just work? (that's /boot/boot.scr apparently, and just says "vmlinuz")14:41
pittiI might need to run flash-kernel for that?14:43
pittiretoaded: ^ or maybe you know14:43
pittiretoaded: so cyclops-node02 is fully upgraded to saucy (3.11.0-15 kernel) and didn't come back after reboot; node04 is just a plain upgrade to current raring (-35 kernel), and came back; node03 is upgraded to saucy, but didn't reboot yet; I'd like to reboot with the raring kernel to avoid the same fate as node0214:44
retoadedpitti, hmmm .....14:44
pittiretoaded: ah, I'll ask ogra about that, he'll know14:45
retoadedpitti, ack. in the mean time I'll look at node0214:45
rbasakpitti: I don't recall, off the top of my head. Running "sudo flash-kernel" won't hurt.14:46
rbasakpitti: can you pastebin boot.scr and `ls /boot`?14:46
pittirbasak: /etc/kernel/postrm.d/zz-flash-kernel calls that with an ABI14:48
pittirbasak: I haven't changed anythign yet, doing now14:48
retoadedpitti, node02 did come back up but assigned the wrong interface in the default route14:50
retoadedit's fixed now14:50
pittiretoaded: ah, good to know14:51
pittiretoaded: what did you change, so that I can do the same change to node03 before I reboot?14:51
retoadedpitti, I set eth1 to manual in /etc/network/interfaces14:53
pittiindeed, I wonder what the second one is14:53
rbasakpitti: IIRC, on highbank, flash-kernel does very little, since U-Boot can read /boot/vmlinuz directly. I think the boot.scr just points to it and sets parameters and that's all. But it's been a while.14:53
pittirbasak: right; now that I know that both kernels work and it's due to /e/network/interfaces, I can verify that safely :)14:53
pitti10.98.3.0   U     0      0        0 eth014:55
pitti10.98.3.0   U     0      0        0 eth114:55
pittiretoaded: ^ indeed, that's from the (not yet rebooted) node03; that looks wrong14:55
retoadedthat is does14:56
pittiretoaded: nice trick with ipmitool; node05 isn't reachable via network (and I haven't touched that at all yet); I salvaged that as well15:09
retoadedpitti, sweet15:09
pittiso same old by now, fix overflowing /boot, fix apt, upgrade to saucy15:09
pittirbasak: ah, too bad -- adt-virt-lxc only works with a cloud image (we really need to fix that), and lxc-create -t ubuntu-cloud barfs with "confused by argument: armhf"15:26
pittiI take it we don't have armhf cloud images?15:26
pittihm, actually we do on http://cloud-images.ubuntu.com/trusty/current/15:26
=== om26er is now known as om26e
=== om26e is now known as om26er
rbasakpitti: is that an lxc bug? I think lxc-create should work with armhf on -t ubuntu-cloud.15:35
pittirbasak: figured it out; I took trusty's cloud-image-utils, worked now15:35
pittisaucy's is too old for armhf15:35
rbasakAh, OK.15:35
pittirbasak: adt-virt-lxc still doesn't seem to like them, though :(15:39
pittiRuntimeError: Failed to find host root directory for container 'adt-virt-lxc-qcayey'.15:40
pitti"sudo lxc-start-ephemeral -o trusty-cloud" works perfectly, though15:40
pitti        host_guest_root = '/var/lib/lxc/%s/%s' % (lxc_name, subdir)15:42
pittithat's not true, I have containers in /data/lxc/15:42
pittiwe need to teach that to read the LXC config15:42
rbasakThat whole area of the code is a hack.15:44
rbasakThe moment we can have lxc-wait support, it can all go away15:45
rbasakbug 126680815:45
ubot5bug 1266808 in lxc (Ubuntu) "No mechanism to wait until a started container is ready and has finished booting" [Wishlist,Triaged] https://launchpad.net/bugs/126680815:45
pittimeh, cloud images' apt sources use archive.u.c. instead of ports15:47
slickymasterhey DanChapman15:52
=== chihchun is now known as chihchun_afk
DanChapmanhey slickymaster :-)16:02
pittiretoaded, jibel: so cyclops-node0[2345] are now running up-to-date saucy and reboot reliably; cyclops-node0[23] have lxc installed and "trusty" and "trusty-cloud" (cloud-image) containers16:04
pitti$ sudo adt-run -B libpng_1.2.49-5ubuntu1.dsc --- adt-virt-lxc --ephemeral trusty-cloud16:04
pittijibel, rbasak ^ succeeds at last \o/16:04
pittiI had to fix and upgrade the trusty cloud image16:04
slickymasterDanChapman: thanks for that, mate. I really appreciate it16:04
retoadedpitti \o/16:04
jibelpitti, wow16:04
* jibel is impressed16:04
pittiI'll set up apt-cacher-ng on node2/3 to speed up things16:05
DanChapmanslickymaster, No worries when is the membership meeting? I will try to turn up aswell :-)16:05
jibelpitti, they should have access to apt proxy on tachash16:06
pittijibel: ah, is that squid or apt-cacher-ng or something else?16:06
jibelit is running on port 800016:06
jibelpitti, squid16:07
slickymasterDanChapman: the meeting will be held on February 6th, 2014 at 22:00:00 UTC in #ubuntu-meeting on irc.freenode.net16:07
slickymasterDanChapman: if you're willing, which I thank you, I'll ping you coming the day16:08
pittijibel: works fine, thanks; I'll configure it on all four nodes16:08
jibelpitti, that's what upgrade tests are using and it works quite well16:08
pittijibel: done16:13
* pitti tries the postgresql-plsh autopkgtest, that's more elaborate16:15
pittijibel: that looks quite promising indeed!16:20
pittijibel: want me to set up the other two nodes while I'm at it?16:20
jibelpitti, if you have time for it,  go ahead16:21
pittijibel: I suggest we don't create fresh trusty-cloud containers daily, but instead dist-upgrade that instance16:45
pittijibel: today's armhf cloud instance is horribly outdated (dist-upgrade takes like 20 mins), and it needs some adjustment after creation16:45
pittijibel: ok, all four nodes are now ready to run autopkgtests; I tested libpng on all four16:55
pittijibel: in case you wonder, containers are in /data/lxc/, /etc/lxc/lxc.conf configures that16:55
pittijibel: as /data/ has tons of space16:55
pittirbasak: ^ FYI16:56
rbasakutlemming: ^^ - I guess we need to sort these out?16:56
pittiutlemming: ah, are you building the armhf cloud images? their apt sources use archive.u.c. instead of ports.u.c., and are very outdated (trusty)16:57
pittiwell, either it's the cloud images themselves, or the lxc-create ubuntu-cloud template (not sure what creates the apt sources)16:58
pittisorry, need to run to Taekwondo now, have a nice evening everyone!16:58
utlemmingpitti: er, they use ports now, not archive. IF not then there is an issue16:58
utlemmingpitti: or an issue with cloud-init16:59
slickymasterbbl ->17:12
=== spineau is now known as spineau_afk
=== jodh` is now known as jodh
elfyballoons: ok - how about "Proceed with the test in your native language. Note that the testcase will remain in English and you will need to translate instructions to suit"19:18
balloonshmm.. a bit wordy.. Perhaps we place in italics?19:19
balloonswordy as in long, but if we shorten it's likely to be confusing.. it's well said, just the explaination is long :-)19:19
elfyProceed in your native language. Instructions will remain in English19:19
elfyProceed in your native language if you wish. Instructions will remain in English19:19
elfyballoons: 2 more to choose from then ^^ :p19:21
balloonsi like the shortest I guess :-)19:21
elfyok - so who to italicise it ?19:21
elfyhow ...19:22
balloonsmm strong bolds it19:26
balloonsI think <i> still works19:26
elfyI'll plan to get them done by the time your about tomorrow then19:28
knomefor emphasize19:29
balloons^^ knome's got it19:31
balloonsI know <b> and <i> are SO old school19:31
balloonsty much elfy19:31
elfyyou know more than me balloons - it's all voodoo as you are aware :p19:31
knomewell <b> and <i> should still work i guess, but they refer to specific *style* rather than the *purpose*19:32
knome<strong> and <em> are meaningful for screen-readers too, because they know to read something in a *strong* or *emphasized* way, rather than read something... "bold" or "italic" ?19:33
elfystuck in the wall above my head that is :p19:33
knomehooray for more semantic web!19:33
Letozaf_balloons, hello19:47
balloonsLetozaf_, hello19:48
Letozaf_balloons, I've fixed some autopilot calendar app tests that failed for localization problems, but I think I have found a bug on other tests19:49
balloonsLetozaf_, I'm working on calendar still today as well.. What did you find?19:49
balloonsI'm confused why it's failing on dashboard atm19:49
Letozaf_balloons, for instance if I run calendar_app.tests.test_weekview.TestWeekView.test_current_week_is_selected test19:49
Letozaf_balloons, it fails because calendar app gets sunday as fist day of weed but in Italy it's supposed to be monday19:50
balloonsLetozaf_, ahh.. ok, that is supposed to be accounted for in the test19:52
balloonssee _get_first_day_of_week19:52
balloonswhat day of the week does it say is the first day19:52
Letozaf_balloons, I get "Locale has Sunday as first day of week"19:52
Letozaf_balloons, but it should be monday19:52
Letozaf_balloons, the value of daystart property is wrong19:53
=== bfiller is now known as bfiller_afk
balloonsahh, well.. weird. Does the calendar show Sunday as first or Monday as first?19:54
elfygood job I'm not doing that - my week starts on a Thursday :(19:54
Letozaf_balloons, if I open calendar app with autopilot launch the first day of weed is Monday, but let me try agian just to be sure19:54
Letozaf_elfy, :D19:55
balloonselfy, :-P Nice!19:55
balloonsLetozaf_, yes confirm it. It should be reading it correctly from the app. The app itself should be reading the locale19:55
Letozaf_balloons, that's why I'm a bit confused as the app launched with autopilot launch is right, the first day of week is monday19:56
balloonsok.. heh.19:56
balloonsthat's good, so the app is getting it correct :-)19:56
Letozaf_balloons, but firstDay = self.week_view.firstDay.datetime is wrong19:56
Letozaf_balloons, it should be 20 jan instead it's 1919:57
Letozaf_balloons, so the test fails with MismatchError: 19 != 2019:57
balloonsright.. the dayStart comes from the qml file, have a look19:57
balloonsproperty var firstDay: dayStart.weekStart(Qt.locale().firstDayOfWeek);19:58
balloonsproperty var dayStart: new Date()19:58
balloonswe need the firstDay property19:58
=== jackson is now known as Guest4739
balloonsohh, lol.. I thought it was wrong for a second.. looks ojk19:58
* Letozaf_ is looking at qml file19:59
Letozaf_balloons, yes thanks20:00
=== Ursinha_ is now known as Ursinha
Letozaf_balloons, I'm not so good in QML so I'm googling a bit :P20:06
balloonsLetozaf_, I don't think the answer is in the qml.. the firstDay is set according to the locale20:07
balloonswe should make sure it's telling us Monday in the test.. if so, then the test isn't working properly20:07
Letozaf_balloons,  I saw that in the test the value of firstDay is 19 instead of 20, but have to find out why now20:08
balloonsadd a couple debug prints, see what values we get from the qml, etc20:09
Letozaf_balloons, yes I did it but maybe I will try again to see if I can find the reason why the test fails20:10
Letozaf_balloons, now I'm quite sure I'm doing it right :P20:11
balloonschihchun_afk, i greet you nonetheless. hola mi amigo20:25
=== bfiller_afk is now known as bfiller
balloonsLetozaf_, so what have you learned?20:30
Letozaf_balloons, the fistDay property contains 19 jan (I used print to get it's value) : self.week_view.firstDay.datetime it must come from qml -  I am trying to figure out how to transform the value 1390172400 in the property (got this with autopilot vis) in a formatted date20:30
balloons1390172400 sounds like a unix timstamp20:30
Letozaf_balloons, I was googling for that20:30
balloonsSun, 19 Jan 2014 23:00:00 GMT20:31
Letozaf_balloons, lol Sun, 19 Jan 2014 23:00:00 GMT was about to write it20:31
balloons:-) So basically everything looks correct then. The locale is telling us the week starts on Monday, but it doesn't20:32
Letozaf_balloons, I'm a bit confused as calendar app has the week displayed coreclty20:32
Letozaf_balloons, it starts on mon and ends on sun20:32
balloonsok, so let's peer into the qml the20:33
Letozaf_balloons, but the value of the property is wrong... :?20:33
balloonsLetozaf_, well I mean it's not what we need20:33
balloonsthe qml might make further changes to it, so it's starting on Monday like it should20:33
Letozaf_balloons, oh! yes maybe20:34
balloonslol.. not that I see20:34
* balloons was grasping at straws20:34
balloons^^ there's an odd saying for you20:34
Letozaf_balloons, :D yes20:34
Letozaf_balloons, love odd sayings20:34
balloonsI was hoping the qml would have an answer, but it doesn't20:35
balloonsso the locale returns Sunday as the first day, but it shows up properly as monday20:35
Letozaf_balloons, yes20:35
balloonsI can't figure out why autopilot isn't working for me on my desktop.. ugh20:39
Letozaf_balloons, weekStart property is not the same as dayStart the first has 1389567600 the latter 139017240020:39
Letozaf_balloons, weekStart is in PathViewBase20:39
Letozaf_balloons, Sun, 12 Jan 2014 23:00:00 GMT  ?20:40
Letozaf_balloons, another sunday instead of monday20:41
balloonsLetozaf_, I'm playing here: lhttps://code.launchpad.net/~nskaggs/ubuntu-calendar-app/debug-ap-tests/+merge/20269120:45
* Letozaf_ is looking at it20:47
Letozaf_balloons, the other day autopilot also did not work for me... after some updates it started working again :O20:50
balloonsit's only calendar.. I borked something somewhere.. there's a bad import but it doesn't make sense20:51
Letozaf_balloons, :(20:54
balloonsoO narrowed it down :-20:56
Letozaf_balloons, I've found something weired too20:57
Letozaf_balloons, in the TimeLineHeader there's a label LUN (monday) but the date is Sun, 12 Jan 2014 23:00:00 GMT20:58
Letozaf_balloons, so label and date differ20:58
Letozaf_balloons, same on the other HeaderDateComponent, label LUN and date Sun, 19 Jan 2014 23:00:00 GMT21:00
balloonswhoa, weird21:02
Letozaf_balloons, I am quite convinced something's wrong in the qml file, but cannot find where :(21:03
balloonsLetozaf_,  if you believe it to be a bug, then let's file one21:04
Letozaf_balloons, ok I will21:04
elfyballoons: if you're using trusty and have a minute to spare on a game - try horizontally resizing sudoku if it's installed21:10
elfythen try it on a small screen :p21:10
balloonsseems fine21:11
elfymmm - might be Xubuntu issue then - can't resize it <--> at all21:11
balloonsugh.. yea, I can resize everything just fine here21:11
balloonsmy trusty is updated to today21:12
elfymmm - that was worth mentioning then21:12
elfymine too21:12
Letozaf_balloons, I reported bug 127172621:22
ubot5bug 1271726 in Ubuntu Calendar App "In Week tab labels displayed in HeaderDateComponent differ from date with localization other than English locale" [Undecided,New] https://launchpad.net/bugs/127172621:22
balloonsLetozaf_, I think I might have an insight into why this is21:22
Letozaf_balloons, the labels display 20 and MON but the date is Sun 19 Jan21:23
balloonsLetozaf_, they are adding and subtracting days, but you see the datetime has a time value in it21:23
balloonsmight be the issue.. I wonder if a screenshot would be helpful?21:23
balloonsit's a bit confusing I'd guess to explain21:23
Letozaf_balloons, sure I will attach one now21:23
Letozaf_balloons, yes quite difficult to explain21:24
Letozaf_balloons, ok added three screenshots hope  the "problem" is clearer now21:38
balloonsLetozaf_, ohh that's perfect21:39
Letozaf_balloons, :D21:39
balloonsPretty clear to see the issue from the screenshots21:39
balloonsLetozaf_, very good find. And it's confusing, heh21:43
balloonsmight help explain some of these weird errors I'm seeing21:43
Letozaf_balloons, yes it's confusing21:43
Letozaf_balloons, hope this helps also for your weired errors :)21:44
balloonswell.. now as to good ole reminders app.. I'm guessing it's about time for you to say ciao21:44
balloonsLetozaf_, here's an example veebers did of mocking: https://code.launchpad.net/~veebers/stock-ticker-mobile-app/mock-server-for-testing/+merge/19497121:45
balloonsI might steal that for trying with reminders21:45
Letozaf_balloons, cool thanks I will take a look at it21:45
Letozaf_balloons, yes sounds like it will be useful for reminders-app too21:46
veebersballoons: that reminds me, have we had any luck communicating with the stock-ticker-app dev?21:47
Letozaf_balloons, going to bed now :P be back tomorrow21:47
balloonsLetozaf_, buonasera21:47
Letozaf_balloons, buonanotte :)21:48
balloonsveebers, :-) not since before xmas.. It's not a primary core app, so there's less focus on it21:48
veebersballoons: ok. It sucks that there is that MR still sitting there for it, but I don't really have time to do anything about it _right_ now. I'll try and chase it up in the near future21:49
balloonsveebers, I'll ping again. Still, the work you've done on it I think will be useful into solving the issues we have with reminders and weather21:49
veebersballoons: also, hi how are you :-)21:49
veebersis this regarding a mock server?21:49
balloonsso if you do have time, I'd suggest putting it into mocking the server for weather or reminders :-p21:49
balloonsveebers, yes21:49
balloonsweather is moving to TWC api, and there's a branch with some work done for it21:50
balloonsbut in general, we don't have a good solution for mocking yet21:50
balloonsI've been holding your MR as an example to look at when I needed to start21:50
veebersballoons: right, I took the example of the server mock from another app (can't remember the name right now) but there has been talk about making a generic mockable server that we can re-use21:50
balloonsthat day is more or less here21:50
veebersballoons: ah ok. I'm pretty sure it's something we intend to discuss during the sprint. But that's not today :-)21:51
balloonsveebers, elopio and I ran into the same issue with needing to setup an online account as part of a test21:51
balloonsso it's another piece in the mocking puzzle21:51
balloonsyes, it might take the sprint.. but likely I'll have some examples good or bad before then heh21:52
veebersballoons: ah, sweet21:55
elopioveebers, balloons: about sharing a base fake http server, the scope devs told me that the code we would share is so small that it's better to copy it. Most things are specific to the real server we are mocking.22:05
elopiohere's the one I like the most so far:22:05
elopiocomes with a nice fixture to start it during set up :D22:05
veeberselopio: sounds awesome22:05
veebersperhaps we need to promote it as an example other people can work off22:06
elopioveebers, balloons: maybe the three of us can come up with a perfect server example, and balloons can blog about it.22:08
elopiowhatever balloons says in his blog is holy word.22:09
balloonselopio, veebers we also have an app developer week with presentations :-)22:09
balloonselopio, lol.. yes I need to post about a few of these toys22:09
elopioballoons: hey, when's the developer week?22:10
elopioI would like to talk about a domain specific language for user acceptance tests.22:11
balloonselopio, oO22:11
balloonszzz.. I JUST now realized the week is the same time as our sprint in oakland22:12
=== salem_ is now known as _salem
balloonsLucaBiolcati, hello22:56
LucaBiolcatiballoons, where is the error?22:57
balloonsLucaBiolcati, oO.. I'll have a look22:58
balloonsLucaBiolcati, all fixed22:59
balloonsLucaBiolcati, you were missing the last column23:00

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!