Flakey test exceeds timeout on CI / specs (macos, 2.7.1)

Open
#775 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
25/100
Issue type
Bug
Clarity
Needs clarification
Activity status
Stale
Tech stack
ruby
Domain
testing

Research direction

Start with the CI / specs (macos, 2.7.1) job and the mspec-run command shown in the linked run. Locate the example mentioning CVE-2020-10663 and determine why it exceeds the 30-second timeout on macOS. Done means the example completes reliably within the timeout and the macOS spec job passes.

Written by the indexing model from the issue text.

Description

There is a test which occasionally exceeds the 30 second timeout on CI / specs (macos, 2.7.1), causing the test suite to fail, even if the changes being tested haven't broken anything.

The following logs are from this run

$ ruby /Users/runner/runners/2.263.0/work/spec/mspec/bin/mspec-run --timeout 30
ruby 2.7.1p83 (2020-03-31 revision a0c7c23c9c) [x86_64-darwin19]

CVE-2020-10663 is resisted by only creating custom objects if passed create_additions: true or using JSON.load
Example took longer than the configured timeout of 30.0s
Dominant language
Ruby
Stars
623
Forks
403
Avg merge
10h 38m
Merged PRs (30d)
5

Getting set up

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.

More from ruby/spec

All issues in ruby/spec

Similar issues

More Ruby issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.