Builder libcheck-solaris10-amd64 Build #30
Results:
Failed shell_3
SourceStamp:
| Project | libcheck |
| Repository | http://svn.code.sf.net/p/check/code/trunk |
| Revision | 1229 |
| Got Revision | 1229 |
| 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 | 30 | Build |
| codebase | Build | |
| got_revision | 1229 | SVN |
| project | libcheck | Build |
| repository | http://svn.code.sf.net/p/check/code/trunk | Build |
| revision | 1229 | 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 | Wed Dec 23 18:09:49 2015 |
| End | Wed Dec 23 18:18:01 2015 |
| Elapsed | 8 mins, 11 secs |
All Changes:
:
Change #20822
Category libcheck Changed by brarcher Changed at Wed 23 Dec 2015 18:08:48 Repository http://svn.code.sf.net/p/check/code/trunk Project libcheck Revision 1229 Comments
checkmk: use double slash in regular expression For many awk implementations using both a single and double slash escapes in regex expressions in strings works correctly. However, it was observed on Solaris that a single slash results in the literal value being added to the string (e.g. \n was a newline) and only the double slash works as expected. As there should be no harm, updating the regex expressions to use double slashes.
Changed files
- AUTHORS
- checkmk/checkmk.in