Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Event Hubs] Test failures - receiver.spec.ts #3472

Closed
ramya0820 opened this issue Jun 5, 2019 · 2 comments
Closed

[Event Hubs] Test failures - receiver.spec.ts #3472

ramya0820 opened this issue Jun 5, 2019 · 2 comments
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs

Comments

@ramya0820
Copy link
Member

Following tests in receiver.spec.ts are failing (under section with EventPosition specified as) -

  • 'from end of stream' should receive messages correctly
  • 'after a particular offset' should receive messages correctly
  • 'from a particular enqueued time' should receive messages correctly

The Node tests were failing as well in some of the runs, and this seemed like it has to do with entity setup.

Expected behavior: Both Node and browser tests to pass consistently.

Steps to reproduce: Checkout latest commit from #3445 if not already available on master.

@ramya0820 ramya0820 added Client This issue points to a problem in the data-plane of the library. Event Hubs labels Jun 5, 2019
@ramya0820 ramya0820 assigned ramya0820 and unassigned ramya0820 Jun 5, 2019
@ramya0820
Copy link
Member Author

Took a closer look at the tests, the test failures in Node are unrelated and fixed with changes proposed in #3484 (as verified on local).
These tests involve multiple receive() calls as well and are the reason why messages are getting received before the main receive() call gets executed.
Fix for this will likely be same as #3471, unless something more gets uncovered.

cc @ramya-rao-a @AlexGhiondea

@ramya-rao-a
Copy link
Contributor

@ramya0820 Closing this issue for the same reason as #3471 (comment).

The failing tests in receive.spec.ts have been refactored to avoid multiple receive calls on the batching receiver and thus avoiding the drain scenario

@github-actions github-actions bot locked and limited conversation to collaborators Apr 12, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Development

No branches or pull requests

2 participants