• Home
  • Features
  • Pricing
  • Docs
  • Announcements
  • Sign In

Logflare / logflare / 46b7833deedcac78af4adf461d273f43dc12a5f9-PR-3478
80%
main: 80%

Build:
Build:
LAST BUILD BRANCH: ne/backends
DEFAULT BRANCH: main
Ran 14 May 2026 08:17PM UTC
Jobs 1
Files 473
Run time 2min
Badge
Embed ▾
README BADGES
x

If you need to use a raster PNG badge, change the '.svg' to '.png' in the link

Markdown

Textile

RDoc

HTML

Rst

14 May 2026 08:00PM UTC coverage: 79.946% (-0.007%) from 79.953%
46b7833deedcac78af4adf461d273f43dc12a5f9-PR-3478

Pull #3478

github

djwhitt
test: stabilize syslog truncation properties and scheduler metrics

The two syslog property tests asserted byte_size(syslog_msg) <= max_bytes
for all max_bytes in 1..100_000, but SyslogAdaptor.Syslog always emits the
full RFC5424 headers — when max_message_bytes falls below the headers
length (~74 bytes for a factory log event), the frame is headers + empty
body, which exceeds max_bytes. This intermittently failed on main when
StreamData generated a small max_bytes (e.g. seed 769458 → max_bytes=6).

Measure the headers length per log event and assert against
max(max_bytes, headers_floor). For the ciphertext property, skip the
decryption assertions when max_bytes leaves no room for an encrypted
payload (the frame is just headers in that case).

Also document the contract on Syslog.format/2 so the headers-floor
behavior is visible to callers without reading the implementation.

The "scheduler metrics" test in telemetry_test.exs was flaking on slow
CI runners: it called Schedulers.async_dispatch_stats/1 (which spawns a
supervised task) and then assert_receive with the default 100ms timeout.
Spawn + 10ms sample + dispatch can exceed 100ms under load. Switch to
the synchronous Schedulers.collect_dispatch_stats/1 — same emission
logic, no race — matching the synchronous-call pattern other tests in
this file already use.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Pull Request #3478: test: stabilize syslog truncation properties and scheduler metrics

12478 of 15608 relevant lines covered (79.95%)

5230.79 hits per line

Coverage Regressions

Lines Coverage ∆ File
1
93.33
-6.67% lib/logflare/system_metrics/schedulers/schedulers.ex
Jobs
ID Job ID Ran Files Coverage
1 46b7833deedcac78af4adf461d273f43dc12a5f9-PR-3478.1 14 May 2026 08:17PM UTC 473
79.95
GitHub Action Run
Source Files on build 46b7833deedcac78af4adf461d273f43dc12a5f9-PR-3478
  • Tree
  • List 473
  • Changed 5
  • Source Changed 0
  • Coverage Changed 5
Coverage ∆ File Lines Relevant Covered Missed Hits/Line
  • Back to Repo
  • Pull Request #3478
  • PR Base - main (#5215A47D...)
STATUS · Troubleshooting · Open an Issue · Sales · Support · CAREERS · ENTERPRISE · START FREE · SCHEDULE DEMO
ANNOUNCEMENTS · TWITTER · TOS & SLA · Supported CI Services · What's a CI service? · Automated Testing

© 2026 Coveralls, Inc