This is an automated email from the git hooks/post-receive script. It was generated because a ref change was pushed to the repository containing the project "UNNAMED PROJECT".

The branch, master has been updated via 9b0a51fb8761f448d6ab604eb7f39bf197c5b59d (commit) via 119bed52fa77294ad810dc9cc29dcdb933b89c3f (commit) via abd4b7d7057bf4f33e9720c12853348562720c38 (commit) via 4e64b8821d73b29edab2e0a945ba3c05587cfd3a (commit) via 8e9f30f3e12b59d2a432bd0306f08a9825d42f5e (commit) via e34932099218d7b8c4e00629242551edced2e2fb (commit) via cb320b8ddf91037872b0fe47a2b8f8d5ac26da4f (commit) via ac0b59d93a11687060f4a2328961d6d5bff3426a (commit) via 2bdab3d2911badc892f62bb34c83c20e4eb79b85 (commit) from f6ab3d8e9cc90a5bc028334ca96001a612a3e001 (commit)

Those revisions listed above that are new to this repository have not appeared on any other notification email; so we list those revisions in full, below.

- Log ----------------------------------------------------------------- http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=9b0a51fb8761f448...

commit 9b0a51fb8761f448d6ab604eb7f39bf197c5b59d Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 02:38:42 2017 +0100

osmoutil: end_proc: wait for term in a loop

Recent commit b59b677c9b13483aac72b15f4f797863d841d958 called proc.terminate() instead of killing right away, with a .1 second sleep. Reduce this sleep to a minuscule first wait_time, remaining tolerant for processes that take longer.

Actually all of our current processes are very fast to terminate. This patch was created while looking for a different problem, now that it's there we might as well keep it.

Change-Id: I98849e4550116c5666fdf6f5d4cbb576ffa3e14a

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=119bed52fa77294a...

commit 119bed52fa77294ad810dc9cc29dcdb933b89c3f Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Tue Feb 28 02:44:25 2017 +0100

osmoutil: add pick_test() to pick unittest tests by name

Change-Id: I92f90c334169f31920c63dd5c5ac8dac215065e6

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=abd4b7d7057bf4f3...

commit abd4b7d7057bf4f33e9720c12853348562720c38 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:03:44 2017 +0100

speed up python tests more than 10 fold by sleeping less

The VTYInteract tests gave a constant sleep(1) grace period for the process to startup. This caused the test to take minutes for no reason at all.

Add code to VTYInteract._connect_socket() to try and connect right away, retrying up to three seconds in .1 second intervals. This flies through most tests without any sleep() at all.

When TCP socket debugging is switched on, also print how many connection tries it took to connect the VTY socket.

Note that the openbsc python tests also add some sleep()s that also need to be removed to benefit from this.

Change-Id: Icc337f52a93d5fe31fc4ff235ccaf4e0fe75fa39

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=4e64b8821d73b29e...

commit 4e64b8821d73b29edab2e0a945ba3c05587cfd3a Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:31:02 2017 +0100

cosmetic: put socket connection code in separate function

Prepare for upcoming patch that adds connection retries to speed up tests.

Change-Id: I2dddf8794b4241898373178c8a1aa2e98b01095c

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=8e9f30f3e12b59d2...

commit 8e9f30f3e12b59d2a432bd0306f08a9825d42f5e Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:17:22 2017 +0100

tcp_debug: don't abort when socket can't be removed

It appears that during some error conditions, the socket will not be in the tcp socket debug tracking list, and on top of an exception this barfs as well. Let's not care about the tcp debug list and avoid confusing error messages.

Change-Id: I8daa317fed8fc7e720dccb70fd5f7fc74fde423f

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=e34932099218d7b8...

commit e34932099218d7b8c4e00629242551edced2e2fb Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:12:14 2017 +0100

cosmetic: early exit instead of if-cascade

It appears that during some error conditions, the socket will not be in the tcp socket debug tracking list, and on top of an exception this barfs as well. Let's not care about the tcp debug list and avoid confusing error messages.

Change-Id: Ib7b0e45fa1f5551da2fc81b71dcc227eee533f44

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=cb320b8ddf910378...

commit cb320b8ddf91037872b0fe47a2b8f8d5ac26da4f Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:11:13 2017 +0100

debug_tcp_sockets: clearly mark as global var

Change-Id: I56e26590ea380c7deab7ce132d688b37eb2d11a3

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=ac0b59d93a116870...

commit ac0b59d93a11687060f4a2328961d6d5bff3426a Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 01:02:45 2017 +0100

debug: also output nr of open file descriptors for 'tcp debug'

Change-Id: I8a583df549f3e2b79068fd8cd32b75473539410d

http://cgit.osmocom.org/python/osmo-python-tests/commit/?id=2bdab3d2911badc8...

commit 2bdab3d2911badc892f62bb34c83c20e4eb79b85 Author: Neels Hofmeyr nhofmeyr@sysmocom.de Date: Mon Feb 27 00:58:19 2017 +0100

tcp debugging: allow switching on TCP debug by env var

Print monitoring info about TCP sockets when the env var OSMOPY_DEBUG_TCP_SOCKETS is present and not "0".

Makes it easy to enable it on jenkins without blowing up output of normal runs "at home".

Change-Id: I46212d07a2c1be05672a37766457e6c98b68f90d

-----------------------------------------------------------------------

Summary of changes: osmopy/obscvty.py | 68 +++++++++++++++++++++++++++++++++++------------- osmopy/osmodumpdoc.py | 1 - osmopy/osmotestconfig.py | 1 - osmopy/osmotestvty.py | 1 - osmopy/osmoutil.py | 46 ++++++++++++++++++++++++++++---- 5 files changed, 91 insertions(+), 26 deletions(-)

hooks/post-receive