test: fix timecop version to keep clock specs in tests #4521
+3
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue(s) this PR fixes:
None.
What this PR does / why we need it:
Fix the current situation where CI is failing entirely.
timecop
0.9.9 supportsProcess.clock_gettime
.This breaks specifications of
process_extenstion
of Fluentd andFluent::Clock
.Process.clock_gettime
support travisjeffery/timecop#419Fluent::Clock
usesCLOCK_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.
Docs Changes:
Not needed.
Release Note:
Not needed.