Builder libcheck-solaris10-amd64 Build #13
Results:
Build successful
SourceStamp:
Project | libcheck |
Repository | http://svn.code.sf.net/p/check/code/trunk |
Revision | 1199 |
Got Revision | 1199 |
Changes | 1 change |
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 | 13 | Build |
codebase | Build | |
got_revision | 1199 | SVN |
project | libcheck | Build |
repository | http://svn.code.sf.net/p/check/code/trunk | Build |
revision | 1199 | 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 Mar 12 14:01:17 2015 |
End | Thu Mar 12 14:09:13 2015 |
Elapsed | 7 mins, 56 secs |
All Changes:
:
Change #9159
Category None Changed by brarcher Changed at Thu 12 Mar 2015 14:00:14 Repository http://svn.code.sf.net/p/check/code/trunk Project libcheck Revision 1199 Comments
add extra space around comparison operators for assert messages The following argument was made in the report of bug #102 to include extra space around the comparison operator in assert messages: When ck_assert_int_gt(1 + 2, 3 + 4) fails, it outputs a string like this: Assertion '1 + 2>3 + 4' failed: 1 + 2==3, 3 + 4==7 This doesn’t look nice, since most programmers write spaces around comparison operators. Therefore, the assertion message should do the same. Assertion '1 + 2 > 3 + 4' failed: 1 + 2 == 3, 3 + 4 == 7 For condensed code, it would look like this: Assertion '1+2 > 3+4' failed: 1+2 == 3, 3+4 == 7 I think the versions with the spaces look nicer than those without.
Changed files
- src/check.h.in
- tests/check_check_master.c