yellow team mailing list archive

[Gary Poster <gary.poster@xxxxxxxxxxxxx>]

On 2012/12/20 01:02:21, gary.poster wrote:
> Good news and bad news.  The good news is that the deployment took
three minutes
> instead of 20 for me.  Rock!  The bad news is that the tests did not
pass for
> me.  I have to run now, but this is what I see so far.

> $ time JUJU_REPOSITORY=~/dev/repo/ ~/bin/jitsu test juju-gui --logdir
/tmp
> --timeout 40m --no-bootstrap
> 2012-12-19 19:30:10,417 jitsu.test:INFO Running unit test: deploy.test
> test_api_agent (__main__.DeployTest) ... ok
> test_branch_source (__main__.DeployTest) ... ERROR
> test_customized_api_port (__main__.DeployTest) ... ERROR
> test_staging (__main__.DeployTest) ... ERROR
> test_api_agent (__main__.DeployToTest) ...

> If I see any helpful log messages I'll pass them on later.  Anyway,
"Land with
> changes": please verify that the tests pass for you before landing.

> Thanks

> Gary

The unit tests all passed just fine, for what it is worth.

Unfortunately, the test logs that jitsu collected for the functional
tests don't appear to be informative.

The tests took 40 minutes and a few seconds, because the
DeployToTest.test_api_agent test hung and I used a maximum 40 minute
test length time with jitsu test.

2012-12-19 19:30:10,417 jitsu.test:INFO Running unit test: deploy.test
test_api_agent (__main__.DeployTest) ... ok
test_branch_source (__main__.DeployTest) ... ERROR
test_customized_api_port (__main__.DeployTest) ... ERROR
test_staging (__main__.DeployTest) ... ERROR
test_api_agent (__main__.DeployToTest) ... 2012-12-19 20:10:10,421
jitsu.test:WARNING Error running unit test deploy.test: 124

I have a vague suspicion that your branch of the charm doesn't like
installing on top of itself, but there could be many other explanations.

I really want to know what you do to debug these functional tests.  I
did not get pdbs to work locally (stdout/stdin are not passed through
for this to work, AFAICT), and the logs collected by jitsu test left a
lot to be desired.  I wanted to investigate the charm log, but we don't
get that from jitsu test.  Maybe we ought to incorporate that into our
own test infrastructure?  I have a weekly retrospective card to discuss
this, and see if you or anyone else have any good techniques, or ideas
about what we can do to improve jitsu test for debugging.

Thanks again

Gary

https://codereview.appspot.com/6977043/

-- 
https://code.launchpad.net/~frankban/charms/precise/juju-gui/bug-1088618-serve-releases/+merge/140745
Your team Juju GUI Hackers is requested to review the proposed merge of lp:~frankban/charms/precise/juju-gui/bug-1088618-serve-releases into lp:~juju-gui/charms/precise/juju-gui/trunk.