Skip to content

[CI] Expect real response durations in the request specs - #66

Merged
PetrHeinz merged 1 commit into
mainfrom
claude/request-spec-durations
Oct 2, 2026
Merged

PetrHeinz merged 1 commit into
mainfrom
claude/request-spec-durations

Conversation

@PetrHeinz

Copy link
Copy Markdown
Member

CI on main has been red since logtail-rack 0.2.8 was released. The latest build run on main (https://github.com/logtail/logtail-ruby-rails/actions/runs/36985106168) failed on all 65 jobs. Each job failed the same three examples:

  • spec/logtail-rails/http_events_spec.rb:38
  • spec/logtail-rails/http_events_spec.rb:81
  • spec/logtail-rails/rack_logger_spec.rb:38

logtail-rack 0.2.8 times responses with the monotonic clock. Timecop doesn't freeze that clock, so the response line now reads e.g. Completed 200 OK in 0.7ms instead of in 0.0ms. The last green run on main still resolved logtail-rack 0.2.7.

This PR only changes the tests: the three expectations now match any one-decimal duration (in \d+\.\d+ms), which also still matches 0.2.7's 0.0ms. The gem code is unchanged, so no release is needed.

The open logtail-rails PRs (#59–#65) each carry this same commit, so the patches are identical and they will merge cleanly after this one.

Locally on Rails 8.1 / Ruby 3.4.9 with logtail-rack 0.2.8: 36 examples, 0 failures.

🤖 Generated with Claude Code

logtail-rack 0.2.8 times responses with the monotonic clock, which Timecop
doesn't freeze, so "Completed 200 OK in 0.0ms" no longer holds. The last CI
run on main still resolved logtail-rack 0.2.7.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@PetrHeinz
PetrHeinz marked this pull request as ready for review October 2, 2026 08:51
@PetrHeinz PetrHeinz changed the title Expect real response durations in the request specs [CI] Expect real response durations in the request specs Oct 2, 2026
@PetrHeinz
PetrHeinz merged commit cf7f070 into main Oct 2, 2026
67 checks passed
@PetrHeinz
PetrHeinz deleted the claude/request-spec-durations branch October 2, 2026 08:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant