ReactiveX / ReactiveX/rxjs

Intermittent test case failure

Open
#6,630 5 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

help wanted
Dominant language
TypeScript
Stars
31.7k
Forks
3k
PR merge metrics
No merged PRs in 30d

Description

Bug Report

Current Behavior
A clear and concise description of the behavior.

One of test is failing intermittently on CI like below:

1) Observable
       should handle sync errors within a test scheduler:
     AssertionError: 
Expected 
	{"frame":0,"notification":{"kind":"E","error":{"name":"RangeError","message":"Maximum call stack size exceeded"}}}
	
to deep equal 

      at TestScheduler.observableMatcher [as assertDeepEqual] (dist/spec/helpers/observableMatcher.js:42:14)
          -> /home/runner/work/rxjs/rxjs/spec/helpers/observableMatcher.ts:45:10
      at /home/runner/work/rxjs/rxjs/dist/src/internal/testing/TestScheduler.js:183:23
          -> /home/runner/work/rxjs/rxjs/src/internal/testing/TestScheduler.ts:216:14
      at Array.filter (<anonymous>)
      at TestScheduler.flush (dist/src/internal/testing/TestScheduler.js:181:43)

Expected behavior
A clear and concise description of what you expected to happen (or code).

Reproduction

** Please provide repro code does not involves framework, or other setups to address this bug is specific to rxjs core **

var your => (code) => here;

Environment

  • Runtime: [e.g. Node v${x}, Chrome v${x}]
  • RxJS version:
  • (If bug is related) Loader, build configuration: [e.g webpack, angular-cli version, config]

Possible Solution

Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

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 the Observable test named "should handle sync errors within a test scheduler" and inspect spec/helpers/observableMatcher.ts alongside src/internal/testing/TestScheduler.ts. Reproduce the intermittent CI failure and determine why the expected result becomes a RangeError; done means the test passes reliably without the stack overflow.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.