=== CyberJacob is now known as CyberJacob|Away === scuttlemonkey is now known as scuttle|afk [02:12] when writing charm tests are they run from the perspective of a deployed charm in a juju environment and ran from the /var/lib/juju/charms/path? [02:16] like when `make test` is run from the automated charm tester the charm is already in a deployed state? [02:17] or do i have to run through the actual deploy and relations commands first [02:17] im guessing this is what amulet does from what i can see in the juju docs [02:45] marcoceppi_, do i have the ability to query the api state server address and password from the jenv files during an automated test run? === CyberJacob|Away is now known as CyberJacob === MasterPiece1 is now known as MasterPiece === CyberJacob is now known as CyberJacob|Away === CyberJacob|Away is now known as CyberJacob === CyberJacob is now known as CyberJacob|Away === MasterPiece is now known as _Xamin_ === MasterPiece1 is now known as MasterPiece === ming is now known as Guest82927 === dosaboy_ is now known as dosaboy === uru_ is now known as urulama [13:57] anyone know if i have the ability to query the api state server address and password from the jenv files during an automated test run? [14:32] I dont think any of you know how to get a new thinpad kb in brussels rigt? [14:33] oops wrong channelsorry [14:37] imagine a charm with my IDE all configured https://www.stgraber.org/2014/02/09/lxc-1-0-gui-in-containers [14:38] where I can relate it to other charms in order to edit them [14:38] :) [14:38] this could be possible? [14:41] sebas5384, get pass that pending machine issue? [14:42] or were you able to file a bug? [14:42] I didn't comeback to that [14:42] after you destroy de environment all gets normal in the new version [14:43] i will get more information with the team and file a bug :) [14:43] stokachu: thanks for reminder me! [14:44] sebas5384, np :D msg me the bug when you get it created [14:44] stokachu: sure :D [14:44] the upgrade of juju using an existing juju env shouldnt break [14:44] Does someone have time to review this? https://bugs.launchpad.net/charms/+bug/1272083 [14:44] Bug #1272083: HPCC Charm initial check-in for review === danwest_ is now known as danwest [16:06] tvansteenburgh, my memory is a little foggy but was it you i was talking to about the charm testing a little while back? [16:08] stokachu: probably [16:09] tvansteenburgh, ok, i was wondering if during a charm test do i have access to the jenv file for getting the api state server and admin password? [16:09] or are those defined in an environment variable somewhere [16:12] stokachu: hm, i'm not sure [16:12] obviously it would work fine if you were running the test locally [16:12] yea, i noticed amulet will do some type of deployer setup for setting up the charm to be tested [16:12] and i *think* it would work on jenkins too [16:13] stokachu: yeah amulet basically makes a deployment file and hands it off the juju-deployer [16:14] tvansteenburgh, do i have the ability to run charm tests using jenkins without proposing it to charm store? [16:15] stokachu: no, but i could do it for you [16:15] stokachu: also, you can just run bundletester directly, as that was jenkins does [16:15] stokachu: this may be helpful -> http://blog.juju.solutions/cloud/juju/2014/10/02/charm-testing.html [16:16] tvansteenburgh, is charmguardian installed as part of bundletester? [16:16] stokachu: actually it's the other way around [16:17] but you can install bundletester by itself too [16:17] bundletester can be pip installed [16:17] charmguardian, you need to clone source and run make [16:17] ok cool, so if bundletester passes locally then theoretically it'll work in jenkins [16:17] stokachu: yep [16:18] tvansteenburgh, ok ill use this locally and when ready maybe have you kick off a charm test for me to make sure i can query the api server? [16:18] stokachu: sounds great. just curious, are you using python-jujuclient for the api calls? [16:18] tvansteenburgh, we have a python3 version of python-jujuclient that we use [16:19] https://github.com/Ubuntu-Solutions-Engineering/macumba [16:19] stokachu: ah, right on [16:19] stokachu: are you in Brussels this week? [16:19] tvansteenburgh, nah unfortunately [16:19] tvansteenburgh, im in austin in nov though [16:20] ah okay, just curious [16:20] i'm in Brussels, and it's time for beer now :) [16:20] tvansteenburgh, haha enjoy [16:20] thanks for the help this gets me most of the way there [16:20] stokachu: will do, catch ya later [16:20] great, glad to help! [16:20] cya [16:20] cya === stokachu is now known as stokachu__ === stokachu__ is now known as stokachu === roadmr is now known as roadmr_afk === CyberJacob|Away is now known as CyberJacob === roadmr_afk is now known as roadmr === CyberJacob is now known as CyberJacob|Away === underyx is now known as underyx|off