TESTOPTS=-v shows running test and the result.
If something weird happen, it show error immediately.

As rake task executes many tests, so it may be better to
delay showing test details later.

NOTE: --progress-style=fault-only helps you to focus on
failure, but it is inconvenient when test case has stalled.

Signed-off-by: Kentaro Hayashi <[email protected]>
Co-authored-by: Kentaro Hayashi <[email protected]>

console gem v1.24 and v1.25 has some specification changes that
influence Fluentd.

Since they have nothing to do with vulnerability, we should keep
the version on v1.16 stable branch.

Signed-off-by: Daijiro Fukuda <[email protected]>

Backported from 74b2e3d. (#4502) 

Signed-off-by: Shingo Nakayama <[email protected]>
Signed-off-by: Daijiro Fukuda <[email protected]>
Co-authored-by: Shingo Nakayama <[email protected]>

Backported from 57f821b.

---

timecop 0.9.9 supports `Process.clock_gettime`.
This breaks specifications of `process_extenstion` of Fluentd and
`Fluent::Clock`.

`Fluent::Clock` uses `CLOCK_MONOTONIC_RAW` if possible and it does not
be affected.
However, `CLOCK_MONOTONIC_RAW` is not available on Windows, so the
impact on tests on Windows is very significant.

For now, we should avoid this effect by fixing the version.

Signed-off-by: Daijiro Fukuda <[email protected]>

Backported from 236d87d.

---

This is because `@log_level` is invalid for YAML.
Instead, we should interpret $log_level as `@log_level` on YAML parser.

Signed-off-by: Hiroshi Hatake <[email protected]>

Backport(v1.16): config: yaml_parser: Handle $log_level element for special case (#4482)

Backported from 3b27984.

---

`Tempfile#binmode` returns `File` object, not own `Tempfile`
object.
So, GC will cause its finalizer and the file can be closed during
the test.
This is the cause why these tests sometimes fail by
`IOError: closed stream`.

Signed-off-by: Daijiro Fukuda <[email protected]>

Backported from 891ce71.

---

If Oj is not installed, LoadError with the empty message is raised.
So, the current condition `/\boj\z/.match?(ex.message)` does not work
and the following meaningless warning is displayed.

    {datetime} [warn]: #x {id} LoadError

After this fix, the log message will be:

    {datetime} [info]: #x {id} Oj is not installed, and failing back to
    Yajl for json parser

Refactor "rescue" logic because this falling back feature is
currently only for "oj" (LoadError can not occur for "json" and
"yajl").

Signed-off-by: Daijiro Fukuda <[email protected]>
Co-authored-by: Takuro Ashie <[email protected]>

Backported from fe5843f

---

This option is explained as "add plugin directory".
However, since v1.16.0, the behavior has changed to overwrite the
default value unintentionally.
(PR: #4064, commit: 41678bf).

We should revert it to the original behavior.

Signed-off-by: Daijiro Fukuda <[email protected]>

Signed-off-by: Kentaro Hayashi <[email protected]>

Signed-off-by: Daijiro Fukuda <[email protected]>

Signed-off-by: Daijiro Fukuda <[email protected]>

Signed-off-by: Daijiro Fukuda <[email protected]>

Because it does not fix the bug itself.

Signed-off-by: Daijiro Fukuda <[email protected]>

For updating documentation or release task, running GitHub Actions
is waste of resource.

https://docs.github.com/en/actions/writing-workflows/workflow-syntax-for-github-actions#onpushpull_requestpull_request_targetpathspaths-ignore

Signed-off-by: Kentaro Hayashi <[email protected]>

v1.16.6