Ticket #333 (defect)
Opened 3 years ago
Last modified 2 years ago
ability to run the test suite on an arbitrary port (not 8000)
Status: closed (fixed)
| Reported by: | john_g@cibolo.com | Assigned to: | dowski |
|---|---|---|---|
| Priority: | normal | Milestone: | 3.0 |
| Component: | CherryPy code | Keywords: | tests port 8000 |
| Cc: |
I would like the ability to run the test suite on an arbitrary port because new users can hit a conflict with networkaudio using port 8000 (KDE multimedia includes libaudio2, jack uses it, akode uses it)
Change History
10/03/05 12:44:17: Modified by anonymous
- owner changed from Robert Brewer <fumanchu@amor.org> to fumanchu.
10/03/05 13:00:26: Modified by fumanchu
- status changed from new to assigned.
- milestone set to 2.1-final.
10/06/05 02:32:34: Modified by fumanchu
- keywords changed from cherrypy-2.1.0-rc1/trunk test.py failed tests port 8000 "in use" to tests port 8000.
- milestone changed from 2.1-final to 2.2-final.
11/30/05 11:07:53: Modified by dowski
- owner changed from fumanchu to dowski.
- status changed from assigned to new.
11/30/05 11:08:02: Modified by dowski
- status changed from new to assigned.
03/28/06 12:22:24: Modified by rdelon
- milestone changed from 2.2-final to 3.0.
08/22/06 12:19:56: Modified by fumanchu
- status changed from assigned to closed.
- resolution set to fixed.
Final touch-up in [1266].
12/10/06 23:57:26: Modified by fumanchu
2.x help fixed in [1512].
Partially fixed in [718]. test.py now takes a --port=xxxx argument, which will set the port for both client and server for all tests. Running individual tests, you are still restricted to the WSGI server on port 8000; that fix can wait for 2.2. Finally, test_states also hard-codes port 8000 when run on its own.