/srv/irclogs.ubuntu.com/2014/02/18/#juju-gui.txt

=== gary_poster is now known as gary_poster|away
rick_h_frankban: I'm trying to run the functional tests and getting errors on "for pe in os.environ['PATH'].split(os.pathsep):" which seems odd? Seen that before?12:18
frankbanrick_h_: functional tests for the GUI? no, never seen it12:28
rick_h_frankban: yea, they all failed in the FF selenium stuff on PATH keyerror. Trying again12:30
frankbanrick_h_: uhm... so in the environment the tests are run on the path is not defined, weird12:31
rick_h_wondered if I had something missing, will keep poking at it12:31
rick_h_brb daycare run12:32
rick_h_benji: jujucharms.com is updated so moved the check the etags over. Can you check the etags while I get the charm updated and hopefully we can close the book on the move/upgrade today. 12:33
benjirick_h_: sure12:34
benjirick_h_: 100% consistent etags and they are in the right format (which is different than they were before)12:38
rick_h_benji: rock on, thanks for the check12:53
benjinp12:54
=== gary_poster|away is now known as gary_poster
* gary_poster adds quiet yay in benji's direction :-)13:10
gQuigscan I not restart juju-gui with normal service tools?   Does it need to have an upstart job to manage it?13:17
rick_h_gQuigs: the gui is run via an apache install. So you have to restart apache. The gui is just some JS that talks to Juju. Reloading the browser reloads the Gui13:18
rick_h_gQuigs: what are you trying to do?13:18
benjiheh13:19
gQuigsrick_h_: just curious how it starts up and is managed; sometimes it was coming up, but not ever finishing connecting to the environment13:20
rick_h_gQuigs: so yea, when you load the browser it tries to talk to the juju environment. That's purely the browser trying to setup a websocket connection to the charm and from the charm to the juju api endpoint in the environment. 13:22
frankbangQuigs: on the charm/server side, the upstart job is named guiserver, so "service guiserver restart". logs can be found in /var/log/upstart/guiserver.log13:26
gary_posterWe've never seen an issue there though, have we?  Knowing more about the symptom he describes would be valuable13:27
rick_h_no issues I've heard. My first reaction is local network issues during wss setup?13:28
gQuigsrick_h_: frankban, thanks both.. this helps a lot13:28
frankbangary_poster: agreed. gQuigs ^^^: what browser are you using? does it happen after e.g. cleaning the cache/running in incognito mode?13:28
rick_h_gQuigs: sure thing, let us know if you hit more issues we can watch for. We've not heard of any issues, but of course want to make sure we catch anything early13:29
gary_posterwe have heard of occasional issues on MaaS.  those have seemed to be related to networking.  Getting a test MaaS cluster might be a nice idea eventually.13:31
gQuigsfrankban: was using Firefox stable on Ubuntu 13.10.  I'll see if I can repdoduce reliably or if it was a one ff13:31
frankbancool thanks gQuigs 13:31
rick_h_frankban: are you on trusty or saucy?13:32
frankbanrick_h_: saucy13:32
frankbanrick_h_: I have a trusty vm13:32
* gary_poster steps out. biab13:52
rick_h_frankban: if you get a sec can you run the tests on charm trunk on both to see if you can dupe my issue on the trusty side? I'm getting it on both laptop/desktop.13:56
rick_h_I'm working on running hte tests manually so I can try to debug vs wrapped in juju-test, but a sanity check on your env would be appreciated. 13:56
frankbanrick_h_: sure, so "make ftest" on the charm in both saucy and trusty, right?13:58
rick_h_frankban: yes please13:59
rick_h_the hope is that saucy passes and trusty fails and gives me a hint that it's trusty package related13:59
frankbanrick_h_: started tests on saucy13:59
rick_h_vs some mystery thing in my install that causes it to not work13:59
gQuigsrick_h_: frankban the issue appears once the juju-gui VM has been restarted..  it just hangs at connecting to environment (has happened 3/5ish reboots)14:04
rick_h_gQuigs: VM restarted?14:05
rick_h_gQuigs: what are you deploying to?14:05
gQuigsrick_h_: openstack14:07
rick_h_gQuigs: so you're restarting the machines then? and on restart it fails to connect at all? Does it come up eventually?14:07
gQuigsrick_h_: io've givenb it 5 mins14:08
rick_h_gQuigs: ok, so next time it fails, see if you can ssh to the machine and see if the guiserver is running via the upstart script frankban mentioned. I wonder if that's not coming back up for some reason. "service guiserver restart"14:09
rick_h_gQuigs: also appreciate if you can open firebug or the javascript console and post any error output from there when it's not connecting14:09
frankbangQuigs: also, does the bootstrap node ip address change between restarts?14:10
frankbangQuigs: between machine reboots14:11
gQuigsfrankban: no, no IPs change14:12
gQuigs1rick_h_: Firefox can't establish a connection to the server at wss://10.55.60.229/ws. all-yui.js:2814:14
gQuigs109:14:06.710 The connection to wss://10.55.60.229/ws was interrupted while the page was loading. all-yui.js:2814:14
rick_h_gQuigs1: ok, so that is the IP of the gui unit?14:14
gQuigsyes14:14
rick_h_ok, yea so if you can juju ssh to that and check if guiserver is running "ps aux | grep guiserver"14:15
rick_h_gQuigs: and if not, try to restart it to see if that solves the issue 14:15
rick_h_"service guiserver restart"14:15
gQuigs1hmm...  nothing running with guiserver in the name, but:14:18
gQuigs1$ sudo service guiserver restart14:18
gQuigs1guiserver stop/waiting14:18
gQuigs1guiserver start/running, process 184414:18
gQuigs1ubuntu@juju-openstack-machine-1:~$ ps aux | grep 184414:18
gQuigs1root      1844  2.3  4.5 152996 23032 ?        Ss   14:16   0:00 /usr/bin/python /usr/local/bin/runserver.py --logging=info --guiroot=/var/lib/juju-gui/juju-gui/build-prod --sslpath=/etc/ssl/juju-gui --charmworldurl=https://manage.jujucharms.com/ --apiurl=wss://10.55.60.220:17070 --apiversion=go14:18
rick_h_gQuigs1: ah sorry yea. 14:19
frankbangQuigs1: is 10.55.60.220 the ip of the bootstrap node?14:20
rick_h_hmm, so that's running. and you can't connect to it. The ip of the machine is the same. 14:20
rick_h_gQuigs1: anything of interest in the /var/log/upstart/guiserver.log? Especially since reboot time?14:21
gQuigs1frankban: yup, and that did not get restarted14:21
frankbangQuigs1: just to exclude any client issues, does it work with chrome in incognito mode?14:22
gQuigs1frankban: interesting.. it worked after I disabled all of my firefox add-ons14:25
gQuigs1frankban: no it must have been a cache thing that required a reboot to clear... weird14:26
gQuigs1(private browsing mode didn't do enough...)14:26
gQuigs1thanks rick_h_ and frankban!14:26
frankbangQuigs1, rick_h_ : uhm... so our websocket client impl is affected in some way by ff cache...14:27
frankbanrick_h_: we should be able to dupe that stopping and restarting a GUI lxc in a local env14:28
rick_h_frankban: something on the network? 14:28
frankbangQuigs1: welcome14:28
rick_h_frankban: yea, should be simple to test out, I'll add a card to investigate14:28
frankbanrick_h_: thanks14:28
jcastroanyone know a good big data bundle offhand?14:29
rick_h_jcastro: there's one sec14:29
jcastroor better yet, know a trick to have the GUI show me all the bundles in the store?14:29
rick_h_jcastro: under dev right now14:29
rick_h_(the second part)14:29
jcastroack14:30
rick_h_jcastro: http://comingsoon.jujucharms.com/sidebar/search/bundle/~gary/demo/2/instantBigDataNoSQL/?text=instantBigDataNoSQL14:30
rick_h_jcastro: is one that maarten was asking about at CT14:30
jcastroperfect14:30
frankbanrick_h_: charm ftests passed on saucy. I'll set up the charm on trusty in a minute14:35
rick_h_frankban: thanks14:35
* gary_poster back14:43
bacmarcoceppi, jcastro, benji: the promulgation marking for bundles in charmworld is broken and i'd like to nail down the rules with you.14:46
jcastrosure14:47
marcoceppibac: sounds good14:47
bacfor a charm, it is marked as promulgated if the series==distroseries in the branch data.14:47
bacyesterday marcoceppi suggested any bundle owned by ~charmers should be considered promulgated14:47
bacis that true?14:47
marcoceppiimo, yes, but I'm biased as that's what I suggested14:49
bacmarcoceppi: well, nows a good time to rethink it!  :)14:50
baci mean, if you need to14:50
bacwhat says jcastro?14:50
jcastro(thinking)14:51
rick_h_the reason we went away from ~charmers for charms was so that others could own the charm (like ~juju-gui)14:51
rick_h_so do we expect the same for bundles?14:51
jcastroyes, eventually14:51
marcoceppiright, but I dont' imagine bundles would get as much attn14:51
marcoceppior not14:51
rick_h_then let's not go through that again14:51
jcastrolike, if I was MySQL and I wanted to own the bundles for MySQL14:51
bacrick_h_: i do not fully understand the series == distroseries test for charms14:51
jcastromarcoceppi, I would argue that bundles will and should get all the attention14:52
marcoceppijcastro: right, but they're probably more important and arguably more static than charms are14:52
jcastrotrue14:52
rick_h_bac: it's LP workings. I just know originally we had the rule that chrams owned by ~charmers were promulgated, but some LP mechanics allowed that to work for others to own the promulgated one14:52
jcastroI think having them owned by ~charmers is fine14:52
* rick_h_ never got all the series level stuff in LP14:52
marcoceppiI'd argue that I can't see a circumstance in the near future where a team would want to own a bundle14:53
rick_h_marcoceppi: so no sales team or open stack team or something?14:53
bacor ~jujugui14:53
marcoceppirick_h_: they can author bundles all they want, but if they want to put them in the store it needs to be vetted by charmers14:53
rick_h_I'm all for simple if we can do it, just want to avoid migrating again if we can. At least for a w2hile14:53
jcastroyeah ~charmers will be fine14:53
rick_h_marcoceppi: hmm, that's not going to be true in 6mo14:53
rick_h_well 8+14:54
marcoceppirick_h_: oh?14:54
jcastroif we ever have a problem with bundle ownership it will be a good problem to have14:54
rick_h_but we can deal with it then14:54
marcoceppirick_h_: what happens in 8mos?14:54
jcastroRick is rewriting the store in Erlang14:54
jcastroj/k14:54
rick_h_woot!14:54
marcoceppihaha14:54
bacok so any bundle owned by ~charmers will be promulgated.  the charmers will need to understand not to push any up that aren't of that quality14:55
marcoceppibac: correct, which is current policy14:55
rick_h_cool, thanks14:55
rick_h_bac: 14:55
bacrick_h_:14:55
bacdid you have more?14:56
rick_h_bac: no, sorry. Meant to be "cool thanks bac" 14:56
bacmarcoceppi: well, it is theoretically current policy.  no code yet to make it happen.  :)14:56
rick_h_but I keyboard fail14:56
rick_h_<enter> and <space> are next to each other on this kenisis 14:57
marcoceppibac: well, we have that policy for charms, so the same would apply to bundles, and given how small the ~charmers are it's pretty well enforced14:57
bacrt14:57
marcoceppicool14:57
rick_h_frankban: ok, got tests passing in trusty by manually bootstrapping, making sure precise is the default series, and manually running JUJU_ENV="ec2" ./tests/20-functional.test14:58
rick_h_frankban: so closer yay14:58
frankbanrick_h_: oh, so the problem could be juju-test not propagating PATH?15:02
rick_h_frankban: right15:02
rick_h_frankban: in trusty15:02
rick_h_I'm setting up a saucy lxc to see if it works for me there15:02
frankbanrick_h_: where are you taking juju-test from?15:03
rick_h_frankban: good question15:03
frankbanrick_h_: mine is from bzr+ssh://bazaar.launchpad.net/+branch/juju-plugins/15:04
rick_h_frankban: is it part of charmtools or something?15:05
frankbanrick_h_: not sure, I just checked out the juju-plugins branch and made a symlink like  /home/frankban/bin/juju-test -> /home/frankban/devel/juju-plugins/sandbox/plugins/juju_test.py15:06
rick_h_so yea, I've got it from the juju stable ppa version of charm-tools for trusty15:06
rick_h_http://bazaar.launchpad.net/~charmers/charm-tools/1.2/view/head:/setup.py15:06
frankbanrick_h_: mine has no version :-/15:08
rick_h_1.2.8-0ubuntu1~ubuntu14.04.1~ppa1 here15:08
rick_h_juju-plugins hmm15:09
rick_h_that's a diff repo entirely15:09
rick_h_marcoceppi: ^ juju test from juju-plugins vs charmtools? discuss?15:09
marcoceppirick_h_: only charm-tools, juju-plugins is depreciated and if I knew how to delete a project on LP I would15:10
marcoceppifrankban: ^15:10
rick_h_marcoceppi: k15:10
rick_h_marcoceppi: so we've got juju test tests that fail because PATH isn't in os.environ on the newer stuff?15:10
rick_h_marcoceppi: sound familiar at all?15:10
frankbanrick_h_: ok, so I'll re-run the tests on saucy using charmtools15:11
rick_h_probably not if the tests didn't hit os.environ I'd guess. 15:11
marcoceppirick_h_: there's a whitelist of envs that are set during the test run15:11
rick_h_frankban: k, sounds like we'll need a card to update the tests or setup to work in the newer stuff15:11
rick_h_marcoceppi: orly, cool Sounds like we might need to add one then15:11
rick_h_or discuss why PATH is a bad one not allowed15:11
rick_h_things are making a lot more sense now :)15:12
marcoceppirick_h_: yeah, I'll expose an environment variable/flag for additional params15:12
marcoceppirick_h_: not that it's a bad one, just one that didn't have a use case15:12
marcoceppiidk who put juju/charm-tools up but that's pretty out of date15:12
rick_h_marcoceppi: rgr, ok. That explains why it's not set. Seemed a really strange thing to have no PATH but having juju test kill it explains it15:12
marcoceppirick_h_: the idea behind that was to provide as sterile as an environment as possible when running the tests as to not have one users env cause a test to pass/fail15:13
marcoceppicharmtools/test.py has the ENV_WHITELIST which is just hardcoded atm15:14
rick_h_frankban: ok, so I think we can kill off the debugging now15:14
rick_h_frankban: I've added a card to update the tests and possibly charm-tools15:14
marcoceppirick_h_: actually, PATH is in the whitelist15:14
marcoceppiso, not sure what is breaking then15:14
frankbanuhm...15:14
rick_h_marcoceppi: hmm, in our tests it throws a keyerror on os.environ['PATH']15:15
marcoceppirick_h_: full trace?15:15
rick_h_bah, give me a few min to restart a test run (takes a few min in ec2 land)15:15
marcoceppirick_h_: ack, thanks!15:15
marcoceppirick_h_: OH, wait, I don't think that patch as landed yet15:16
rick_h_marcoceppi: ah, phew. 15:17
marcoceppirick_h_: I can cut a release for you now if you'd like15:17
rick_h_marcoceppi: yea, I'm pulling from the stable ppa15:17
marcoceppiah, yeah, that's only in trunk atm15:17
rick_h_so I'm on 1.2.8 I think I had up there15:17
rick_h_ok cool15:17
rick_h_marcoceppi: yea, a release with that fix would be useful. 15:17
marcoceppiyup, this would be a 1.2.9 release, will do a check for anything else that needs to land and a release15:18
rick_h_marcoceppi: been chasing tests all morning 15:18
rick_h_marcoceppi: thanks, appreciate it15:18
marcoceppiah, sorry about that!15:18
rick_h_marcoceppi: no hurry, now that I know what's up I can work around it for the moment. 15:19
frankbanhazmat: for when you are back and have time: could you please take a look at https://code.launchpad.net/~frankban/juju-deployer/unit-errors/+merge/206967 ? it's my proposed fix to bug 1279075 and bug 1252301 (the deployer part). Thanks!15:39
_mup_Bug #1279075: Deployer should not stop when a unit has an error <juju-deployer:In Progress by frankban> <https://launchpad.net/bugs/1279075>15:39
_mup_Bug #1252301: guiserver reports second bundle as failing after the first fails <juju-deployer:In Progress by frankban> <juju-gui (Juju Charms Collection):In Progress by frankban> <https://launchpad.net/bugs/1252301>15:39
rick_h_hazmat: we've got this on board for thurs release so appreciate look in next day ish if you can. 15:40
rick_h_hazmat: to beat freature freeze and release with new gui/charmworld this week.15:40
bachazmat: and while you're in the deployer mindset, if you could look at my branch too that would be great.15:42
bachttps://bugs.launchpad.net/juju-gui/+bug/127769615:42
_mup_Bug #1277696: Bundles with revision-less charm URLs should deploy <juju-gui:In Progress> <https://launchpad.net/bugs/1277696>15:42
hazmatfrankban, bac, rick_h_ ack.. it will have to be tomorrow morning i've got a customer deadline i'm racing against today15:53
rick_h_hazmat: understood thanks15:54
frankbanthanks15:54
bacty15:54
rick_h_jujugui call in 615:54
* rick_h_ needs to set a 10min alarm15:55
rick_h_jujugui call in 116:00
rick_h_Makyo: standup ping16:01
bacbenji: beep16:01
Makyo2fa sorry :T16:02
Makyobenji, https://github.com/juju/juju-gui/pull/13016:05
benjithanks16:06
benjiMakyo: review done; looks good.16:29
Makyobenji, thanks16:29
jcastrorick_h_, for your blog post16:30
jcastrodon't do mediawiki16:30
jcastrotoo boring16:30
jcastrodo something epic like the big data one16:30
jcastroor the mongodb cluster16:30
rick_h_jcastro: k16:37
rick_h_jcastro: for the 'explain' was that a side note?16:37
jcastroyeah16:38
benjimarcoceppi: I have a charmtools branch up for review which adds a warning for bundles that include charms with revisionless URLs: https://code.launchpad.net/~benji/charm-tools/add-versionless-charm-in-bundle-warning/+merge/20698616:38
jcastroso like if I rerun quickstart it relaunches the browser?16:38
gary_posteryes (it rocks)16:38
rick_h_jcastro: so when you run quickstart it looks "do you have an environment? If you do, does juju status show a gui? If it does, where is that gui at?"16:38
rick_h_jcastro: +1, why i said in the blog post, it's the fastest way to get back into your env days later16:38
rick_h_jcastro: so one more reason for you to <3 and use it16:39
marcoceppibenji: I figured you guys would put this in the online proof instead of the offline, but works for me. I'll review shortly16:39
benjicool16:39
rick_h_jcastro: aside from that, is the blog post ok for what they're wanting? I couldn't tell if they want one, two, etc?16:42
hatchrick_h_ you have a blog?16:57
rick_h_hatch: yea, though don't hit it all that often16:59
hatchcool what's the url? I wana see this blog post :)16:59
rick_h_hatch: oh, this is a doc not submitted yet17:00
hatchohh ok17:00
rick_h_hatch: https://docs.google.com/a/canonical.com/document/d/1ma0U1ZxILTh5s3NoHiuwKiclRSxJLIY-Q2MEMzBO7Dk/edit17:00
hatchcool I'll check it out17:00
hatchI used quickstart yesterday from scratch it was pretty awesome using that terminal gui thing17:01
hatchis that a python lib?17:01
hatchto make the gui that is17:01
hatchascii gui :)17:01
rick_h_ncurses17:02
rick_h_urwid is the python lib to help make it usable17:02
hatchcool I didn't know about that17:03
* rick_h_ shakes head at the idea of someone that never installed debian/ubuntu using the text installer17:03
rick_h_jcastro: is winning, cli deprecation goes on and on17:03
hatchrick_h_ Well my first version of Ubuntu was Warty so I'm pretty sure I used the text installer :)17:05
rick_h_hatch: ah ok then it was curses based cli 17:06
rick_h_do a server install sometime and get to see it17:06
rick_h_but anyway, yea quickstart curses for getting going is coolness17:06
hatchkind of caught me off guard because I remembered the cli q/a version :)17:07
hatchI was like....woah what's this? haha17:07
rick_h_man that same tests fails every other run in CI. 17:07
rick_h_Makyo: that test failure is spurious. heads up :/17:08
MakyoBoo, okay.17:08
hatchrick_h_ it's in a different test this time :/17:13
rick_h_hatch: it's been that one for the last 4 or 5 times it's failed I've seen it17:13
hatchohh I saw it in a few others 17:13
rick_h_hatch: it's always that IE10 setHTML error17:13
hatchit's odd how it says there are so many failures but there is just the one17:14
hatchand yes it's always the setHTML error but I've seen the same error in different tests17:14
rick_h_hatch: hmm, went back through last 4 failures and it's always that test and always that error17:16
hatchreally? I thought that it showed up in others...maybe I was mistaken 17:16
hatchwell at least then maybe we can track down the issue17:17
rick_h_hatch: yea17:17
hatchoo this looks cool http://www.indiegogo.com/projects/fin-wearable-ring-make-your-palm-as-numeric-keypad-and-gesture-interface17:19
* rick_h_ runs out for lunch today, biab17:35
MakyoUgh, finally.18:08
benjirick_h_: I have some questions about this bundle search task; do you have a minute?18:54
rick_h_benji: sure thing19:11
benjirick_h_: I'll make a hangout19:11
rick_h_thanks19:12
bacbenji: would you be able to review charmworld promulgation fix?  https://codereview.appspot.com/6555004319:20
benjibac: sure, one sec19:22
benjibac: looks good19:32
baccool19:33
bacbenji: i also killed that annoying message from enqueue, telling you all of the branches it was skipping.  hope you don't miss it.20:24
benjithere goes my Saturday night20:24
* rick_h_ sends cookies to bac 20:24
bacwe even had a test to ensure the output was sufficiently annoying20:25
bacbenji: do you need a review?20:26
benjibac: nope (unless your name is marcoceppi <hint> <hint>)20:27
marcoceppibenji: yes, swamped, will have it reviewed today20:27
benjibac: once you're ready for a new task I have one for the bundle searching things20:27
bacbenji: i am.  what you talking about?20:28
bacbenji: i was thinking about quickly doing the normalizing to lowercase one20:29
benjibac: well I'm trying to figure out the make-bundles-appear-in-search-results-when-one-of-their-charms-is-searched-for, so you can help me with that or...20:29
bacbenji: did you get a clearer idea of what to do?20:29
bacbenji: but i'm glad to talk about it20:30
* bac beverage run20:30
benjithat's cool, another quick one (and one of the top-two in priority) is makeing "bundle(s)" return all the bundels (and "charm(s)" return all the charms if you are in a giving mood)20:30
benjiyeah, I know what, I'm trying to figure out how now20:30
rick_h_benji: one note, the next deploy we need to bring up a new charmworld unit to replace the bad one running in prodstack20:31
rick_h_benji: at that time, we could bring up a new unit and wait for the index to update (the 30min) and then switch over20:32
rick_h_benji: it draws out the deploy, but reduces that downtime issue without an index20:32
benjiah, good thinking20:32
Makyojujugui tiny review and QA! https://github.com/juju/juju-gui/pull/13420:34
MakyoThough... hmm.20:34
rick_h_Makyo: looking ... or not20:34
Makyorick_h_,  take a look and see if that passes.  It can be incremental.20:34
* Makyo makes follow up card.20:34
bacbenji: quick call?20:35
rick_h_Makyo: seems ok here. What's missing?20:36
Makyorick_h_, the fix works around the fact that relations in the vis and relations in the bundle have the same dom id.20:37
MakyoAdded a card to ensure unique dom ids.20:37
rick_h_oh!20:37
bacbenji-cito: https://plus.google.com/hangouts/_/calendar/Z2FyeS5wb3N0ZXJAY2Fub25pY2FsLmNvbQ.t3m5giuddiv9epub48d9skdaso20:37
rick_h_gotcha, cool20:37
MakyoBut this will be a good increment.20:37
rick_h_Makyo: is this something we can add a test for? or some sanity check for future reference? Or if the dom ids were unique we'd not hit this issue so that's the root cause/fix20:38
Makyorick_h_, the latter, yeah. I'll make that my next card, and that part will be testable.20:41
rick_h_Makyo: cool thanks. :+1:'d the current branch20:42
bacrick_h_: can you join benji and me in the hangout above?20:43
rick_h_bac: joining20:43
bacso benji i will start on the bundly one20:48
benjibac: ok, I guess I'll do the lower-case-all-the-things one20:49
bacbenji: and i added your face to the pumpkin colored card20:49
benjiheh20:49
baci guess we can kill it now?  we have cards for the required items20:50
rick_h_bac: +1 it was there to evaluate what we could/should do. 20:52
rick_h_I'm out. Have a good night all. 20:53
benjiyeah20:56
Makyojujugui this stupid IE10 CI thing is really biting me.  Anyone have any hints?21:13
lazyPowerMakyo: What is this IE10 CI thing? I've got some experience with automated browser testing thanks to my last job21:34
rick_h_Makyo: grrr, not yet. It was something hatch could not reproduce locally so his branch went on21:36
rick_h_Makyo: and now it's annoying everyone 21:36
MakyolazyPower, "Error: Object doesn't support property or method 'setHTML'", but unable to repro locally.21:36
rick_h_Makyo: the key thing for retrying is to remove the comment in the pull request that's Status: merge request accepted21:36
MakyoOh, okay.21:36
rick_h_Makyo: that causes the lander to not try to load it again21:36
rick_h_so just delete that comment and it'll retry21:36
MakyoAha!21:37
rick_h_putting a card up for cleaning up this, must be some way to test21:37
MakyoThere we go.21:39
marcoceppirick_h_: do you have a few seconds for a hangout with regards to promulgated charms and me about to make a mess of that?21:39
rick_h_Makyo: there's some notes in the CI doc for the future21:39
rick_h_marcoceppi: sure, sec21:39
Makyorick_h_, cool, thanks.  Will rtfm next time :)21:40
rick_h_marcoceppi: hangout?21:41
rick_h_Makyo: all good, I cheat by writing it so I know the tricks21:43
marcoceppirick_h_: https://plus.google.com/hangouts/_/7acpja2hqsviddhvokd1jo82pc?hl=en21:43
rick_h_marcoceppi: sec, fighing the 'not allowed' get your google account right mess21:44
rick_h_Makyo: yay22:18
rick_h_I watched it so of course not it passed22:18
MakyoWoo!22:21
MakyoAlright, dogs walked, quick errand, then I'll get the dom ids.22:21
marcoceppirick_h_: you still around?23:09
rick_h_marcoceppi: kinda23:11
rick_h_marcoceppi: what's up?23:11
marcoceppirick_h_: ah, don't mean to be a bother, re-promulgated heat to ~openstack-charmers but the API is still reporting ~charmers as the approved version. Wasn't sure how long to wait (been about 45 mins since re-promulgation)23:12
marcoceppihttp://manage.jujucharms.com/api/3/search?name=heat&type=approved&series=precise23:12
rick_h_marcoceppi: did you unpromulgate the other?23:12
marcoceppigood question23:13
rick_h_marcoceppi: hmm, don't see the new one at all atm http://manage.jujucharms.com/api/3/search?name=heat23:13
rick_h_marcoceppi: so give it a bit more23:13
marcoceppirick_h_: will do23:13
marcoceppiwasnt sure if the API was updated at every injest or not23:14
rick_h_marcoceppi: what's the full path? ~openstack-charmers/precise/heat? http://manage.jujucharms.com/api/3/charm/~openstack-charmers/precise/heat ?23:14
marcoceppisince it was a re-promulgation, I didn't first unpromlugate (since all promulgate does is set the canonical branch for the source package in the distro)23:14
marcoceppies23:14
rick_h_k23:14
marcoceppiyes*23:14
marcoceppihttps://code.launchpad.net/~openstack-charmers/charms/precise/heat/trunk23:15
rick_h_ruh roh...damn23:15
rick_h_marcoceppi: http://manage.jujucharms.com/heartbeat23:15
marcoceppiit shows as mapped to lp:charms/heat23:15
marcoceppirick_h_: I don't know what that means, it says PASS to me23:15
rick_h_marcoceppi: looks like ingest has run off the rails23:15
rick_h_Ingest queue sizesPassqueued charms: 18537, queued baskets: 1740.23:15
marcoceppiOH CRAP23:15
marcoceppithat's a lot to ingest23:15
rick_h_heh, pass is "the queue is loading"23:16
rick_h_not that "it's not shrinking and getting caught up like it should"23:16
rick_h_marcoceppi: will have to look into the queue issue tomorrow. Sorry, will ping when we get it updated/straighted out23:16
marcoceppirick_h_: np, thanks!23:17
rick_h_marcoceppi: no vangaurd and such in webops atm. Sorry for the issue23:17
rick_h_but that explains it not loading23:17
marcoceppiyeah, that makes a lot more sense23:17
* marcoceppi has become accustomed to the 15 min turn around23:17
rick_h_yea, when it works it's kind of nice :)23:17
=== TheRealMue is now known as TheMue

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