libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	jenkins: also test build in separate dir	Neels Hofmeyr	2017-03-31	1	-0/+12
\| \| \| \| \| \| \| \| \| \| \| \| \|	To make sure that new patches don't break a build done in another dir than srcdir, make jenkins verify that it still works. Even though 'make distcheck' also tests a build from a separate dir, this does not verify that BUILT_SOURCES are generated properly. If these already exist in the source tree from a previous 'make' issued in the source tree, the BUILT_SOURCES are not regenerated during 'make distcheck'. Hence a separate test run is necessary to ensure stability of new patches. Change-Id: I4b31538c155941fd241bcd33b0d39f2f8491ac1e
*	jenkins: add value_string termination check	Neels Hofmeyr	2017-03-16	1	-0/+2
\| \| \| \|	Change-Id: I7fe3678b524d602fc6aa14bc0ed06308df809a3e
*	contrib: add script to find unterminated value_string arrays	Neels Hofmeyr	2017-03-16	1	-0/+33
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Unterminated value_string arrays are dangerous since get_value_string() and get_string_value() need to know where the struct ends. If the terminator is missing, they might run through and return arbitrary memory locations. Employ some regexes to find such unterminated value string arrays and return nonzero if any are found. This can be used in our jenkins build jobs to avoid committing unterminated value_string arrays. In fact I've found one in current libosmocore: gsm0808_bssap_names in gsm/gsm0808.c, fixed in a separate patch. Change-Id: I2bc93ab4781487e7685cfb63091a489cd126b1a8
*	contrib: add fsm-to-dot.py to draw osmo_fsm dotty graphs	Neels Hofmeyr	2016-12-09	1	-0/+710
\| \| \| \| \| \| \| \|	Add a first version of a python script that tries to analyze .c source files to draw graphs of osmo_fsm implementations. So far it uses quick-and-dirty regexes. Change-Id: I155f57a608d600f59aedfd27ef66eb9772c124e7
*	configure: add --enable-sanitize, use in jenkins.sh	Neels Hofmeyr	2016-10-12	1	-2/+3
\| \| \| \| \| \| \| \| \| \| \| \| \|	--enable-sanitize adds address sanitizer CFLAGS/CPPFLAGS to the entire build. Also pass UBSAN_OPTIONS to the test suite run (only has effect during runtime). Add this flag to jenkins.sh's configure step. To ensure that we get the sanitize results, add 'make check' to jenkins to catch sanitize failures; Keep 'make distcheck' without ASAN; it has its own configure which omits --enable-sanitize. This way we test both with and without ASAN. Change-Id: Idf7f46fa048608c2951f2473cb528f6c8dc2681d
*	jenkins.sh: drop unecessary PATH, now in slave config	Neels Hofmeyr	2016-10-12	1	-1/+0
\| \| \| \|	Change-Id: Ifaff3e5e13c920eb716a5609bfec2f96e10f17b0
*	jenkins.sh: output all test logs when 'make check' failed	Neels Hofmeyr	2016-09-30	1	-1/+3
\| \| \| \| \| \| \|	Assume that cat-testlogs.sh from osmo-ci is installed in $HOME/osmo-ci/scripts, and call from jenkins.sh upon 'make check' failure. Change-Id: I18a08e7ade1a53783d5a4171fe825f61b49457be
*	jenkins: Enable tracing and error handling in bash	Holger Hans Peter Freyther	2016-04-13	1	-0/+2
\| \| \| \| \|	Like jenkins we want to see what is actually being executed and fail if a subcommand has failed.
*	jenkins: Add build script used by jenkins on our public CI	Holger Hans Peter Freyther	2016-04-13	1	-0/+6
	The actual script (removed unused and commented out handling) as invoked by jenkins. This can be used to locally try to reproduce the build.