libosmocore - [no description]

	Commit message (Collapse)	Author	Age	Files	Lines
*	Use value string check from osmo-ci	Max	2017-08-25	1	-2/+3
\| \| \| \|	Change-Id: I513835be2d931d0a931cdfc996f361a451bc1a15
*	contrib: Enable -Werror by default	Pau Espin Pedrol	2017-06-23	1	-2/+2
\| \| \| \|	Change-Id: I1752cad1e34cb6e5f36edf3f538d803eff29d18c
*	jenkins.sh: Disable sanitize for FreeBSD	Pau Espin Pedrol	2017-06-23	1	-1/+7
\| \| \| \| \| \| \| \| \| \| \| \| \| \| \| \|	Our current build server uses clang-3.4.1 and FreeBSD10.3, and AddressSanitizer support is not good yet on those versions, triggering some link issues when it is enabled. I tested using newer clang 3.7.1 in the same FreeBSD version but another compiler error related to __builtin_cpu_supports is triggered. Conclusion: Explicitly disable AddressSanitizer until we move to FreeBSD11 with clang 3.8. Before this commit, AddressSanitizer was implicitly disabled due to a shell compatibility issue which is fixed in next commit in the series, thus we need to explicitly disable it here. Change-Id: I0db497045a2ebf7877232b28ae1fcf1fd89fb3f3
*	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
*	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.