RexOps / RexOps/Rex

read buffer tests on FreeBSD are bailing out sporadically

Open
#1,327 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
Perl
Stars
737
Forks
214
PR merge metrics
No merged PRs in 30d

Description

Describe the bug

Every once in a while, read buffer tests on FreeBSD are bailing out sporadically, like in this CPAN Testers report.

See #954 also, which is similar, or it's still the same even.

These two test results seems to be generated on the same testing box (same deps, rex version, perl version, OS version, architecture, uname output, etc.):

How to reproduce it

Since it seems sporadic, I'm not exactly sure about reproduction and we would probably need help from FreeBSD users.

Steps to reproduce the behavior:

  1. run t/read_buffers.t tests (probably many times until it happens)

Shortest code example that demonstrates the bug:

$ prove -l t/read_buffers.t

or perhaps

$ perl t/read_buffers.t

Expected behavior

t/read_buffers.t test should reliably finish successfully on FreeBSD systems.

Circumstances

  • Rex version: 1.10.0 (probably older ones too)
  • Perl version: 5.30.2 (probably older ones too)
  • OS running rex: FreeBSD 13.0 (probably older ones too)
  • OS managed by rex: -

Debug log

Not a debug log, but test fails with:

Bailout called.  Further testing stopped:  Reading from buffer timed out
FAILED--Further testing stopped: Reading from buffer timed out
*** Error code 255

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start with t/read_buffers.t and run it repeatedly using prove -l t/read_buffers.t or perl t/read_buffers.t on FreeBSD. Compare the sporadic timeout with the linked CPAN Tester reports and issue #954; done means the test reliably finishes successfully on FreeBSD systems.

Written by the indexing model from the issue text.

Assessment

Tech stack
perl
Domain
operating-systems, testing-qa
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.