[00:04] sigh, i guess I can't put off looking at simple streams bugs any longer [00:04] waigani: how you doing today? [00:05] hi davecheney, well after blowing up my vm, I'm now back on track. [00:05] so just starting to look at the tests now [00:06] davecheney: I noticed you start your branches with 106, 111 etc - what is that? [00:06] is there a convention I should follow for branch names? [00:07] waigani: we all started doing that years ago [00:07] for me it was because i couldn't remembver what I had comitted and what I hadn't [00:07] you can do whatever makes sense [00:08] waigani: for me the branch name is entirely to remind me [00:08] so they tend to be long [00:08] and descriptie [00:09] okay, including the bug no. makes sense [00:12] davecheney: you might want to add installing mercurial to your tl;dr [00:13] waigani: everyone has permission to update those deps [00:13] I think when i wrote it code.google.com was blocked bythe firewall [00:13] so I had to copy those deps in by hand [00:13] waigani: everyone has permission to update that install doc [00:13] okay, I'll add it in [00:17] hows it going guys [00:19] Valduare: good [00:19] and yourself [00:19] doing well [00:20] doing photoshoot this week at the wife’s dance studio - on irc in between :P [00:20] looks like few updates to my bug https://bugs.launchpad.net/juju-core/+bug/1300264 [00:20] <_mup_> Bug #1300264: manual provisioning requires target hostname to be directly resolvable

[00:21] Valduare: axw is will be in an hour or so [00:21] ok [00:35] if anyone has a moment to spare https://codereview.appspot.com/83370043 [00:38] perrito666: quick review, please fix the typos in the descriptoin [00:38] you can use [00:38] lbox propose -edit [00:38] davecheney: thank you [00:39] * perrito666 should not propose during night [00:43] davecheney: thank you, reproposed, if any typo is still there it might be poor English grammar on my behalf [00:44] https://bugs.launchpad.net/juju-core/+bug/1301085 [00:44] <_mup_> Bug #1301085: state/apiserver: login_test.go intermittent failure [00:44] this one is concerning [00:44] davecheney: thank you for the comments, will address them [00:50] mwhudson: how are you doing today ? [00:51] davecheney: i am mostly getting distracted [00:54] HURRY THE GUCK UP JUJU [00:54] SHIT [00:54] these god damn tests take hours! [00:55] davecheney: Hi. [00:57] jpds: speaking of frustration [00:57] davecheney: Quite. [01:03] sinzui: http://paste.ubuntu.com/7192347/ [01:03] shit, results are the same as yesteday [01:03] i don't understand [01:04] [LOG] 36.85478 DEBUG juju.environs.configstore Making /tmp/gocheck-1976235410884491574/0/home/ubuntu/.juju/environments [01:04] ... Panic: cannot share a state between two dummy environs; old "dummyenv"; new "dummyenv" (PC=0x3FFFB02F3E4F) [01:04] :0 [01:04] brilliant :( [01:13] hazmat: https://github.com/liris/websocket-client/issues/73 - im going to work with upstream to get python2/3 into one codebase so we can package a python3 version easily [01:14] davecheney: I think that means two tests are trying to Prepare a dummy env without calling dummy.Reset() first [01:14] stokachu, awesome! [01:14] davecheney: are you just running make check, or what? [01:16] hazmat: looks like i can ping andreas once thats done to have a python2 and python3 package [01:16] i didnt see it in debian [01:16] thumper: oops, sorry, I gave you bad advice about using listener.Addr() yesterday apparently [01:16] * thumper shrugs [01:16] it passed the test [01:16] :) [01:16] interestingly when I logged it out [01:17] it was ipv6 as a value [01:17] http://[::]:1234 [01:17] stokachu, tick tock on trusty, i'll merge in 2/3 support to jujuclient its a pretty tiny diff.. deployer might need a little more work [01:18] ok ill work on it this week, the maintainer is in japan though so time differences will be difficult [01:23] axw: nope [01:23] go test [01:25] davecheney: in just the configstore directory? [01:26] axw: nopt [01:26] nope [01:26] go test launchpad.net/juju-core/... [01:27] oh sorry that's from the log, not the test that's being run [01:27] axw: i have no idea what you're talking about [01:27] sorry [01:27] oh [01:27] davecheney: " [LOG] 36.85478 DEBUG juju.environs.configstore Making /tmp" [01:27] it's the package name [01:27] right [01:38] wallyworld_: https://launchpad.net/bugs/1299588 [01:38] <_mup_> Bug #1299588: LXC permission denied issue with 1.17.7

[01:52] davecheney: is there a test memory thing I can use for an io.ReaderSeeker? [01:52] davecheney: like bytes.Buffer [01:52] or somthing [01:52] or do I need to write a file [01:54] davecheney: thanks for your help, I rewrote a part of the script and looks definitely cleaner now :D [02:07] * thumper writes a file... [02:08] thumper: bytes.Reader? [02:33] axw: thumper: you guys used an aws environment lately? the shared credentials i've been using appear to have been revoked [02:33] I've not used shard creds [02:33] wallyworld_: I haven't, but I use my own account [02:34] mmmm ok. i'll dig up som other creds [02:34] after lunch. nom nom [02:45] thumper: bytes.Reader ? [02:45] nm [02:45] wallyworld_, CI failed failed the first attempt of joyent [02:45] I am running it again [02:54] so a test on ppc64el needs zip, but it is not installed by default. [02:55] waigani: add it to the Makefile [02:55] for the install-deps section [02:55] this is a server image [02:55] most people test with the desktop image [02:55] which has gnome fileroller [02:55] so I guess it has zip [02:55] davecheney: okay, will do [02:57] hmm, it's already there [03:05] sinzui: i'll look at the error [03:05] wallyworld_, I am just reporting a bug about the issue [03:06] wallyworld_, You can see the config for the env in cloud-city [03:06] ok. i wonder why it worked for me [03:06] i'll look at the bug [03:06] what's cloud-city? [03:08] sinzui: i see th error says quota exceeded - i had to hog smash wordpress and mysql onto the one machine cause the credentials i had only allow 2 machines [03:09] sinzui: so if your test deploys wordpress an my sql, use the --to option for the second charm [03:09] wallyworld_, Our test wont like exceptions. It needs 3 machines. [03:09] :-( [03:09] I will ask someone to give us proper resources [03:09] won't work for joyent unless we get more quota [03:09] ok [03:10] We have a similar problem with azure. CI failed during the release because the release + revision testing + cloud health checks can exceed the cpu limit [03:11] wallyworld_, At least I don't need to report a bug [03:12] sinzui: and at least it looks like stuff would have worked hopfully :-) [03:12] wallyworld_, yep. [03:15] hmm so if I install zip by hand it works. If I run make install, it doesn't get installed? [03:18] wallyworld_ thumper: so, I can delete 1.16 compat stuff right? [03:18] YES! [03:18] wheee [03:19] have fun, i'm jealous [03:19] :) [03:19] I'm just making changes in cmd/juju/ssh.go, figured I'll delete the compat stuff while I'm there [03:20] yep [03:42] wallyworld_, I hacked the test to make an exception for the joyent provider. http://ec2-54-84-137-170.compute-1.amazonaws.com:8080/job/joyent-deploy-devel/6/console [03:42] ^ same error even though --to 1 was used for mysql [03:42] any other ideas? [03:42] * wallyworld_ looks [03:43] sinzui: is there another orphaned machine running in that account? use the joyent daskboard to check [03:44] nothing in the dashboard [03:44] that happened to me and once i shut down the extra machine it worked [03:44] but wallyworld_ I never even saw the juju machine show up [03:44] sinzui: i can pm you the cred i used [03:44] there was a machine there earlier today. I deleted it [03:50] fuckity fuck fuck [03:50] thumper: ? [03:51] trying to write a test [03:51] :) [03:51] no, wait [03:51] however the behaviour is full of async [03:51] :( [03:51] wow. such fuck [03:51] multiple go rountines started [03:51] I kinda need to wait to know that the tailer has started listening for new lines before I have the test write a few more [03:51] not sure how [03:52] * thumper thinks... [03:53] sinzui: there's a showstopper bug in 1.17.7 which i'm fixing :-( [03:53] i just confirmed it [03:54] so 1.18 will need to be held off till i fix it, which will be today [03:54] wallyworld_, I found the instance. The old UI doesn't show it. The beta does [03:54] ah [03:54] well that kinda sucks [03:55] wallyworld_, I need to get the docs completed. I wont release tomorrow [03:55] yay, gives me time to fix [03:56] this run gets farther, but I wonder how far this will go with just 2G ram [03:58] should be enough to bring up wordpress/mysql you'd hope [03:58] wallyworld_, PASS. I am going to sleep. I will find someone tomorrow to address 1 machine to test and release with [03:58] \o/ [03:58] good night :-) [03:59] wallyworld_: what was the problem? [04:00] thumper: i don't want to tell you [04:00] it was my fault :-( [04:00] permisison error ivoking new api from container provisioner [04:00] works fine from env provisioner [04:00] ah [04:01] our logging/error reporting kinda sucks [04:01] we need to get this errgo stuff integrated and used [04:02] axw: we would expect destroy-env --force to remove the jenv file right? [04:07] join #go-nuts [04:07] oh hai! [04:08] wallyworld_: yes we would [04:08] thumper: i'll have to see if i can reproduce later, but on trunk i did a --force and the jenv file stuck around === vladk|offline is now known as vladk [04:21] wallyworld_: sorry, afk. the .jenv file should be removed if destroy-env succeeds [04:21] wallyworld_: regardless of --force [04:21] wallyworld_: but --force *should* always succeed [04:21] np. yeah, it seems like it wasn't. i'll have to try and reproduce [04:21] obviously that's an ideal though [04:22] * axw goes back afk [04:23] OH FFS [04:23] * thumper looks for someone to stab [04:23] .. [04:25] oops [04:25] * thumper sighs [04:25] ran 'go test' instead of 'go test -gocheck.f ...' [04:26] oh well, all tests passed [04:26] yay [04:26] now for step 27 [04:41] * thumper is done for now === vladk is now known as vladk|offline === vladk|offline is now known as vladk [06:31] axw: I'm just testing the bot for a second, I'll set your branch back to approved when I'm done === jam1 is now known as jam [06:32] jam: okey dokey [07:24] jam: do you know what that error was about? [07:24] axw: well, I killed it once [07:25] but we also seem to have a new intermittent failure in TestRunStop [07:25] https://bugs.launchpad.net/juju-core/+bug/1301198 [07:25] yay :( [07:25] <_mup_> Bug #1301198: jujud Provisioner TestRunStop no activity detected

=== psivaa is now known as psivaa-afk [07:26] and AddRemoveSet still causes problems from time to time... [07:26] not *quite* as often as it used to [07:30] jam: is the bot stalled? [07:30] wallyworld_: I was poking at it, it should be back up now [07:30] log file lasted updated 11 mins ago [07:31] doesn't *appear* to be working [07:31] mornin' all [07:31] morning rogpeppe3 === rogpeppe3 is now known as rogpeppe [07:31] jam: did you notice this? "listen unix @/tmp/juju-core-test.ARliJS/gocheck-6334824724549167320/18/var/lib/juju/agents/unit-wordpress-0/agent.socket: invalid argument" [07:31] jam: I wonder if the TMPDIR change has broken something [07:32] I had not seen that. [07:38] axw: one thing comes to mind, the /tmp/XXX dir starts with 700 permissions. [07:38] but doesn't everything have to be running as the tarmac user anyway? [07:38] yeah, I thought the same thing and had the same conclusion... [07:39] it won't/can't change user [07:44] jam: I think we may have exceeded the path length. [07:44] max path length [07:44] max path length is 108, that is exactly 108 - I'm guessing it needs to include the null byte [07:45] axw: odd. We also had a problem where we rm -rf /tmp [07:45] :) [07:45] which I'm fixing now [07:45] :o [07:46] axw: if something before we set TMPDIR ran and failed, it would still hit the rm -rf TMPDIR [07:46] ah heh :) [07:46] so I'm setting it in another var, and only removing that one. [07:46] axw: I didn't realize normal users could rm tmp [07:47] axw: but that is why the bot stopped working, because it couldn't get /tmp access. [07:47] does it not just remove all the files they own within and then fail? [07:47] yikes, ok [07:47] axw: well /tmp was gone [07:47] I had to mkdir it [07:48] axw: I don't think that is why the original failure occurred. [07:48] jam: tmp being gone, or the invalid argument/max path limit? [07:48] axw: you're probably right about the socket thing: https://bugs.launchpad.net/unity-scopes-api/+bug/1252588 [07:48] <_mup_> Bug #1252588: UNIX domain socket path name limit [07:48] mk [07:49] axw: so I can make my TMPDIR prefix a bit shorter, but we were only just lucky that it was working before. [07:50] indeed, if ever moved away from /var/lib/juju... [07:51] axw: like with the namespacing work? [07:51] /var/lib/juju-jameinel-local ? [07:51] namespace only affects the log dir [07:52] data-dir is in $HOME for machine-0 in the local provider [07:52] but that does not allow units [07:52] axw: so, I can reproduce directly by making TMPDIR really long and running that test. [07:52] I made them shorter, but it still seems like we're going to get bitten sometime. [07:53] yeah. I dunno how we're going to fix that one... perhaps the socket should be in /var/run or something [07:53] that's no good for tests, but we could override it for tests [07:55] dimitern: morning [07:56] morning vladk [08:11] morning vladk and dimitern [08:11] jam: morning [08:15] morning jam [08:23] axw: did you see the bug about rev 2524 ? [08:23] not yet [08:24] oh [08:24] axw: https://bugs.launchpad.net/juju-core/+bug/1300889 [08:24] <_mup_> Bug #1300889: azure and hp cannot deploy as of r2524

[08:24] eh [08:24] no shared-secret file [08:24] error getting file /var/lib/juju/shared-secret: No such file or directory [08:25] gah, because it doesn't exist during cloud-init [08:25] axw: at the least, your patch should probably have included a logger.Debugf() when we were writing the file. [08:26] axw: ah, because we write the Upstart during cloud init, but we don't run the rest of bootstrap stuff until we ssh into the machine. [08:26] yeah, that was a bit dumb. I'll fix it... [08:26] axw: so I think that means we just need to back out your patch until EnsureMongoServer is writing the file at a later time [08:26] because we *don't* want to write the contents of shared-secret to cloud-init [08:26] jam: yeah. I'll just take the --keyFile bit out of the upstart script for now? [08:27] axw: that's probably ok [08:27] axw: I'll note, changes during bootstrap is something that you should probably test live [08:28] jam: I did run with local, but have no idea why it worked now [08:28] axw: local is special [08:28] for a lot of things [08:28] machine-0 is your $HOST [08:28] so not brought up via cloud-init [08:29] mongo is still started before the machine agent though [08:29] axw: I'm pretty sure we also don't "ssh localhost" [08:29] axw: sure but the bootstrap steps probably happen at a different time. [08:29] jam: we don't ssh localhost, but we run the same script via bash [08:29] it's now very similar to cloud bootstrap [08:29] anyway [08:30] I will investigate, and test with azure [08:30] kk [08:31] I have the feeling it is broken on EC2 as well, but I haven't tested that [08:31] I don't see any reason why it would be special [08:32] wallyworld_: did you get your Joyent changes backported to the 1.18 branch? [08:32] jam: yep, and CI tests passed ok \o/ [08:32] wallyworld_: nice, so we get a 1.17.8 today ? [08:33] as soon as my bug fix gets backported but i need to get in landed in trunk first [08:33] wallyworld_: that's what you're landing now? [08:33] yep [08:33] p:~wallyworld/juju-core/container-provisioner-retrywatcher [08:33] k, [08:33] Bot is running it again [08:33] you had a test suite timeout [08:33] great [08:34] as soon as it lands, i'll backport, probably after dinner [08:34] the other failures were probably just my changes, so I'll keep an eye on it. [08:34] which is imminent === psivaa-afk is now known as psivaa [08:41] morning all [08:43] voidspace: mornin' [08:43] voidspace: hangout? [08:43] morning voidspace [08:44] rogpeppe: https://codereview.appspot.com/83500043 when you're free [08:44] axw: looking [08:51] rogpeppe: sure, in a minute or two [08:51] axw: reviewed [08:51] rogpeppe: coffee first :-) [08:51] thanks [08:52] rogpeppe: so, using State and it working is just lucky (racy)? [08:52] I never quite State vs. BackingState [08:52] I never quite understood [08:53] axw: how long did the tests take to run? [08:53] I never quite English [08:53] axw: it's really a failure of vision [08:53] axw: because you talk to a specific State to sync it, but in this case we've got several [08:53] axw: so you need to prod the right one into action [08:54] axw: for a while now, i've wanted to change the syncing scheme so it's global [08:54] rogpeppe: didn't take particularly long to run. it makes sense to change it, anyway [08:57] wallyworld_: your patch has landed. [08:57] jam: the one in 1.18? i submitted that just before dinner [08:57] almost finished eating :-) [08:58] i hadn't checked back [08:58] wallyworld_: no, the one in trunk, I guess you were faster than I :) [08:58] yeah, i am keen to get 1.18 fixed [08:58] so i can relax [08:58] wallyworld_: bot is currently processing axw's gocrypto change, probably will do yours next [08:59] * wallyworld_ taps fingers impatiently [09:00] rogpeppe: I'm in the hangout [09:01] morning all, is the joyent provider working in trunk? I am trying it and bootstrapping hangs on "Bootstrapping Juju machine agent" [09:01] voidspace: i suspect my net connection may be working even less than yesterday... [09:01] rogpeppe: that's impressive :-) [09:02] voidspace: and there's a BT van outside, so it's quite possible it'll go away completely soon [09:06] fwereade: what's the deal with utils.IsNotExist ? [09:06] frankban: there's a bug on trunk that affects all providers, I'm fixing it right now [09:07] rogpeppe, exactly what it looks like: if foo is a file, statting foo/bar does not give an error that satisfies IsNotExist :/ [09:07] os.IsNotExist, that is [09:09] axw: cool, FYI 1) ec2 works well and 2) bootstrapping joyent panics if key-file is not specified in the environments.yaml file [09:10] panic: interface conversion: interface is nil, not string on /provider/joyent/config.go:121 [09:10] frankban: ec2 worked? ok. I think there's a race condition. key-file is something specific to joyent... over to wallyworld_ :) [09:11] axw: yes, I was able to bootstrap that correctly earlier (saucy, revno 2535) [09:11] axw: ec2 I mean [09:12] i'm just losing internet connection while an engineer works on the line [09:12] back soon i hope [09:12] frankban: if you want to get unstuck quickly, then try merging lp:~axwalk/juju-core/lp1300889-disable-mongo-keyfile [09:12] (still uploading...) [09:16] wallyworld_: bot is running your 1.18 branch now [09:16] started 14 min ago [09:17] fwereade: because ENOTDIR != ENOEXIST ? [09:20] wallyworld_: bots done [09:21] axw: trying joyent with your branch [09:21] wallyworld_: looks like it was happy with your patch [09:22] 2253 Ian Booth 2014-04-02 [merge] [09:22] [r=wallyworld],[bug=1299588] Backport r2536 to fix container provisioner retry issue. [09:24] rogpeppe: I did end up going with "godeps before the bot runs", thanks for the suggestion. [09:24] I trust godeps enough now, I'm still not sure about a go get -u in there, though. [09:24] jam: i thought i'd already changed it to do that actually [09:25] rogpeppe: if you did, it didn't end up in the config I saw [09:25] rogpeppe: maybe you did but didn't push the config back into swift ? [09:26] jam: ah, yes, you're right, i didn't [09:26] jam: so i guess you (or someone) overwrote the config i'd done [09:26] jam: oh well [09:27] rogpeppe: I did, as I needed to update it, so I updated my local copy from swift [09:28] jam: i've got a program that enables you to do a juju set with the same data that juju get returns [09:28] frankban: joyent panic is bug #1300846, right? [09:28] <_mup_> Bug #1300846: Juju crashes bootstrapping joyent

[09:29] jam: yeah it seems to be that bug [09:30] voidspace: MgoInstance.Port returns the same port that is inside MgoInstance.Addr [09:30] rogpeppe: right [09:30] voidspace: so no need to parse [09:30] rogpeppe: cool, that's nicer [09:32] rogpeppe: so one of your suggestions (agent/agent.go:528) [09:33] rogpeppe: you suggest gating on SharedSecret == "" instead of StatePort == 0 [09:33] voidspace: i can hear you pretty well BTW [09:33] rogpeppe: how is that any better or different [09:33] axw: after merging your branch, bootstrapping joyent succeeded, thank you! [09:34] frankban: cool, no worries [09:35] rogpeppe: if you're talking I can't hear you :-) [09:35] voidspace: ok, i'll give up on the hangout :-) [09:35] rogpeppe: if StatePort == 0 but SharedSecret != "" we're just as screwed as StatePort != 0 but SharedSecret == "" [09:35] voidspace: so, i see SharedSecret as slightly more fundamental, but you're probably right that it doesn't matter much [09:35] rogpeppe: so they seem directly equivalent checks [09:35] voidspace: the other possibility i thought of was to store a *StateServingInfo instead [09:35] rogpeppe: I'm happy to make the change [09:36] rogpeppe: that would be less arbitrary [09:36] voidspace: then the test could be "if not nil" [09:36] rogpeppe: yep [09:36] voidspace: yeah, otherwise they're both pretty arbitrary [09:36]