CherryPy logs

13 views
Skip to first unread message

demalexx

unread,
Jan 9, 2011, 2:16:48 AM1/9/11
to Django: sane testing
Hi,

On CI server I've got 500 internal server error, but I have no place
where I can see CherryPy or my Django app logs and see why it's
falling. How or where I can set logs on and see them?

Thank you.

Almad

unread,
Jan 16, 2011, 3:08:47 PM1/16/11
to django-sa...@googlegroups.com
Hi,

sorry for the late response, filter malfuncfion :-/

CP server should obey standard configuration, so this is more of a Django
configuration issue, harder to fix as Django is not using logging yet.

If You are using twill, since https://github.com/Almad/django-sane-
testing/commit/2e96fc3785f7ff67fd80350aa20891bc5c43e9bf , You should see the
traceback as a part of failing test message.

As a hack, I would probably write a middleware with process_exception. I have
not written one myself, as I am mostly having either reproducable errors or I
am able to figure it out from traceback.

One trick I have been using is also to use
self.selenium.capture_entire_page_screenshot(filename) or
self.selenium.capture_screenshot(filename), which is helpful (wanted some
wrappers to be part of DST, but had no time for that yet).

It also depends - are You running tests with DEBUG set to True or False?

Almad

demalexx

unread,
Jan 28, 2011, 9:44:13 AM1/28/11
to Django: sane testing
Thanks for your suggestions and answer, as usual :)

What I did - while running tests on CI server, I pause execution when
CherryPy is running and go to testing app manually using lynx
(127.0.0.1:9999/) - that way I've got detailed error description -
missing Python package (I needed to set DEBUG to True for that). It
was simple because app was falling on index page.

Then I make some screenshots using Selenium methods, it was rather
helpful to find bugs in other places.

Thanks for help again! :)

On Jan 17, 4:08 am, Almad <b...@almad.net> wrote:
> Hi,
>
> sorry for the late response, filter malfuncfion :-/
>
> CP server should obey standard configuration, so this is more of a Django
> configuration issue, harder to fix as Django is not using logging yet.
>
> If You are using twill, sincehttps://github.com/Almad/django-sane-
Reply all
Reply to author
Forward
0 new messages