Of course, I didn't test these instructions before sending them out...
Now, that I'm trying it out, I'm stuck on the first step:
make run-testapp fails with
Traceback (most recent call last):
File "bin/run-testapp", line 26, in <module>
canonical.launchpad.scripts.runlaunchpad.start_testapp()
File
"/home/francis/canonical/launchpad/devel/lib/canonical/launchpad/scripts/runlaunchpad.py",
line 392, in start_testapp
DatabaseLayer.tearDown()
File
"/home/francis/canonical/launchpad/devel/lib/canonical/testing/profiled.py",
line 29, in profiled_func
return func(cls, *args, **kw)
File
"/home/francis/canonical/launchpad/devel/lib/canonical/testing/layers.py",
line 757, in tearDown
cls.force_dirty_database()
File
"/home/francis/canonical/launchpad/devel/lib/canonical/testing/profiled.py",
line 29, in profiled_func
return func(cls, *args, **kw)
File
"/home/francis/canonical/launchpad/devel/lib/canonical/testing/layers.py",
line 866, in force_dirty_database
cls._db_fixture.force_dirty_database()
AttributeError: 'NoneType' object has no attribute 'force_dirty_database'
But that's a red herring, because it only means that the clean-ups
executed in the finally are run without the setup() function being called.
pdb shows that there is the following error that happens in start_launchpad:
OperationalError: 'fe_sendauth: no password supplied\n'
make run works correctly
So I don't know if make run-testapp is broken for everyone, or it's just
me that missed a configuration update because of the move to pgbouncer...
On 11-10-28 12:11 PM, Francis J. Lacoste wrote:
>
>
> On 11-10-28 06:04 AM, Robert Collins wrote:
>>>> I'd be happy to help look at this when I return. That could conceivably
>>>> be tomorrow but is more likely to be Monday. I'd look at the logs when I
>>>> ran the tests interactively as my first step. Maybe that would let you
>>>> tackle it?
>> What do you mean by that? {Sorry for noob question, but I'm allowed
>> one a week :P}
>
> My best guess to what he means is that he would use
>
> make run-testapp
>
> That runs launchpad with the same configuration used by AppServerLayer
> tests (available on :8085). You will also have access to the logs like
> when running the regular launchpad dev instance.
>
> You can then run the tests interactively by loading the test through the
> /+yuitest/ URL in your browser.
>
> So looking at the list of your failing test, I would use the following URL:
>
> https://launchpad.dev:8085/+yuitest/lp/testing/tests/test_yuixhr_fixture
>
> And watch the logs :-)
>
> You can even pdb things in this setup.
>
> I've found that this wasn't really documented on the dev wiki, so will
> take this opportunity to update it.
>
> P.S. Robert, every month, I find myself visiting the Urban Dictionary to
> find the meaning of one your expression. Thanks for the opportunity to
> expand my geek slang vocabulary!
>
>
>
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~launchpad-dev
> Post to : launchpad-dev@lists.launchpad.net
> Unsubscribe : https://launchpad.net/~launchpad-dev
> More help : https://help.launchpad.net/ListHelp
--
Francis J. Lacoste
francis.laco...@canonical.com
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Mailing list: https://launchpad.net/~launchpad-dev Post to : launchpad-dev@lists.launchpad.net Unsubscribe : https://launchpad.net/~launchpad-dev More help : https://help.launchpad.net/ListHelp
