Builder libcheck-solaris10-amd64 Build #16
Results:
Build successful
SourceStamp:
Project | libcheck |
Repository | http://svn.code.sf.net/p/check/code/trunk |
Revision | 1203 |
Got Revision | 1203 |
Changes | 2 changes |
BuildSlave:
unstable10xReason:
scheduler
Steps and Logfiles:
Build Properties:
Name | Value | Source |
---|---|---|
branch | None | Build |
builddir | /export/home/buildbot/slave/libcheck-solaris10-amd64 | slave |
buildername | libcheck-solaris10-amd64 | Builder |
buildnumber | 16 | Build |
codebase | Build | |
got_revision | 1203 | SVN |
project | libcheck | Build |
repository | http://svn.code.sf.net/p/check/code/trunk | Build |
revision | 1203 | Build |
scheduler | schedule-libcheck-solaris10-amd64 | Scheduler |
slavename | unstable10x | BuildSlave |
workdir | /export/home/buildbot/slave/libcheck-solaris10-amd64 | slave (deprecated) |
Forced Build Properties:
Name | Label | Value |
---|
Responsible Users:
- brarcher
Timing:
Start | Thu May 7 05:24:05 2015 |
End | Thu May 7 05:32:30 2015 |
Elapsed | 8 mins, 24 secs |
All Changes:
:
Change #10400
Category libcheck Changed by brarcher Changed at Thu 07 May 2015 05:23:03 Repository http://svn.code.sf.net/p/check/code/trunk Project libcheck Revision 1202 Comments
Change behavior of calls for fork() on non-fork() platforms It was requested by users of Windows (e.g. non-fork() supporting platforms) that calls to set CK_FORK mode be ignored if fork() is not supported. This is to avoid the need to detect the current platform and conditionally compile unit test code.
Changed files
- NEWS
- src/check.c
- src/check.h.in
- src/check_run.c
- tests/check_nofork.c
- tests/test_check_nofork.sh
Change #10401
Category libcheck Changed by brarcher Changed at Thu 07 May 2015 05:23:03 Repository http://svn.code.sf.net/p/check/code/trunk Project libcheck Revision 1203 Comments
Catch SIGINT and SIGTERM and kill running tests Tests are forked and placed into their own process group. If the test runner process receives a terminal signal it exits but the test continue running. This could result in test processes running indefinitely if they do not exit themselves. This changes catches SIGINT and SIGTERM signals and kills the test processes. Note that other signals, such as SIGSEGV and SIGFPE will still result in test processes being leaked. This code is based on that in patch #52.
Changed files
- AUTHORS
- NEWS
- src/check_run.c