Hi Riccardo, thanks for your quick response! I saw those tests in /tests.. Is there a way to execute them on my local machine? Or are they considered to run in a travis CI only (at least I found a travis.sh file...)?
Regarding my setup: I'm working on an centos like system uwsgi has been installed via pip $ pip install uWSGI $ uwsgi --version 2.0.12 Basically my simple test app follows the example hosted here [1] Started it like this $ sudo uwsgi --http :9090 --wsgi-file _uwsgi_hello_world.py --buffer-size=32768 *** Starting uWSGI 2.0.12 (64bit) on [Mon Feb 22 13:50:54 2016] *** compiled with version: 4.8.3 20140911 (IBM 4.8.3-9) on 19 February 2016 16:34:43 os: Linux-3.10.0-229.7.2.el7_1.kvmibm1_1_1.16.s390x #1 SMP Mon Jan 25 16:11:01 EST 2016 nodename: zfwpc165 machine: s390x clock source: unix pcre jit disabled detected number of CPU cores: 1 current working directory: /opt/stack/devstack detected binary path: /usr/bin/uwsgi uWSGI running as root, you can use --uid/--gid/--chroot options *** WARNING: you are running uWSGI as root !!! (use the --uid flag) *** *** WARNING: you are running uWSGI without its master process manager *** your processes number limit is 31259 your memory page size is 4096 bytes detected max file descriptor number: 1024 lock engine: pthread robust mutexes thunder lock: disabled (you can enable it with --thunder-lock) uWSGI http bound on :9090 fd 4 spawned uWSGI http 1 (pid: 85157) uwsgi socket 0 bound to TCP address 127.0.0.1:44222 (port auto-assigned) fd 3 Python version: 2.7.5 (default, Jan 12 2016, 06:45:44) [GCC 4.8.3 20140911 (IBM 4.8.3-9)] *** Python threads support is disabled. You can enable it with --enable-threads *** Python main interpreter initialized at 0xb564be10 your server socket listen backlog is limited to 100 connections your mercy for graceful operations on workers is 60 seconds mapped 101440 bytes (99 KB) for 1 cores *** Operational MODE: single process *** WSGI app 0 (mountpoint='') ready in 0 seconds on interpreter 0xb564be10 pid: 85156 (default app) *** uWSGI is running in multiple interpreter mode *** spawned uWSGI worker 1 (and the only) (pid: 85156, cores: 1) now when trying to access it via curl, I get the following: $ curl localhost:9090 curl: (52) Empty reply from server Note: from sending the command until the result is displayed it takes around 5 seconds or so There's no additional output displayed for the request in the uwsgi log The same application works on a x86 machine... If you have a hint for me, it is highly welcome :) Thanks a lot! Andreas [1] http://uwsgi-docs.readthedocs.org/en/latest/WSGIquickstart.html -- ----- Andreas (IRC: scheuran) On Mo, 2016-02-22 at 11:30 +0100, Riccardo Magliocchetti wrote: > Hello Andreas, > > Il 22/02/2016 11:03, Andreas Scheuring ha scritto: > > Hi together, > > how can I execute the uwsgi test suite on my local system? > > There's some tests inside tests/ > > > Background: Uwsgi is is always sending back empty replies on my system > > (s390 architecture), so I thought the test suite would be a good > > starting point for figuring out if there are any platform specific > > issues. > > How have you compiled uwsgi? which version of uwsgi? what's your uwsgi > configuration? Do you have any log? > debian has uwsgi packages for s390x, any chance you can give them a try? > _______________________________________________ uWSGI mailing list [email protected] http://lists.unbit.it/cgi-bin/mailman/listinfo/uwsgi
