ruby.git/test/test_syslog.rb, branch v3_2_11

Update some syslog tests to absurb the format change of FreeBSD syslog

2020-03-12T06:30:20+00:00

FreeBSD

```
$ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }'
rubyspec 78462 - - Hello
```

Linux

```
$ ruby -rsyslog -e 'Syslog.open("rubyspec", Syslog::LOG_PERROR) {|s| s.log(Syslog::LOG_ALERT, "Hello") }'
rubyspec: Hello
```

https://github.com/freebsd/freebsd/commit/591ef7c8076109cff3c41f9bb50da996a34121e9

test/test_syslog.rb (test_log): skipped on Android

2019-10-11T12:13:52+00:00

On Android 28, LOG_PERROR is defined, but not implemented yet.
This change skips Syslog#log explicitly.

Add frozen_string_literal: false for all files

2015-12-16T05:07:31+00:00

When you change this to true, you may need to add more tests.

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@53141 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

use assert_raise

2015-06-02T02:18:44+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@50727 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

test/test_syslog.rb (TestSyslog#test_log): In AIX, each output line of LOG_PERROR to stderr has an additional empty line appended, so skip that line.

2014-10-04T07:35:43+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@47786 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

* test/test_syslog.rb: remove executable.

2014-05-31T07:03:13+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@46275 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

test/test_syslog.rb: Close fds.

2014-05-29T14:59:24+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@46235 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

* test/test_syslog.rb: adjust indent.

2014-02-27T12:52:16+00:00

git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@45197 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

* test/test_syslog.rb (TestSyslog#test_log): Do not be too

2011-08-05T08:26:42+00:00

  specific about the log line format.  Fixes #5081.



git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@32859 b2dd03c8-39d4-4d8f-98ff-823fe69b080e

Skip syslog tests that rely on LOG_PERROR unless it's defined

2011-03-25T11:06:57+00:00

Instead of checking looking at the platform to determine if the tests
relying on LOG_PERROR should be run, look for the definition of the
constant as this will be robust against all platforms as long as the
underlying syslog.c code sets it up correctly.

This specifically addresses failures on Solaris 9.

Signed-off-by: Ben Walton 
Signed-off-by: URABE, Shyouhei 



git-svn-id: svn+ssh://ci.ruby-lang.org/ruby/trunk@31178 b2dd03c8-39d4-4d8f-98ff-823fe69b080e