view doc/debugging.txt @ 6488:99d365eebefd

Rearrage order of python versions. Hopefully travisci runs versions in my specified order. Run non-dev current versions first. Latest ResourceWarning failures only show up in 3.8 and 3.9, so let them run during the first batch of 4 jobs. Then backfill with earlier versions and nightly versions. Note travis has 3.9-dev even though it's tracking a released version.
author John Rouillard <rouilj@ieee.org>
date Mon, 06 Sep 2021 15:00:40 -0400
parents a635a60ffb84
children
line wrap: on
line source

Debugging Aids
--------------

Try turning on logging of DEBUG level messages. This may be done a number
of ways, depending on what it is you're testing:

1. If you're testing the database unit tests, then set the environment
   variable ``LOGGING_LEVEL=DEBUG``. This may be done like so:

    LOGGING_LEVEL=DEBUG python -m pytest test/

   This variable replaces the older HYPERDBDEBUG environment var.

2. If you're testing a particular tracker, then set the logging level in
   your tracker's ``config.ini``.

SENDMAILDEBUG
=============

Set to a filename and roundup will write each email message
that it sends to that file instead to the internet. 
This environment variable is independent of the python -O flag.


Roundup Issue Tracker: http://roundup-tracker.org/