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.

Sign up for GitHub

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

Jump to bottom

[BUG] CheckpointBatchTest Failing on .NET Framework #7492

Closed
chidozieononiwu opened this issue Sep 5, 2019 · 4 comments
Closed

[BUG] CheckpointBatchTest Failing on .NET Framework #7492

chidozieononiwu opened this issue Sep 5, 2019 · 4 comments
Assignees
@jsquire
Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs

Comments

@chidozieononiwu
Copy link
Member

Describe the bug
CheckpointBatchTest Fails randomly on .NET Framework

Exception or Stack Trace

22:44:36.0911952: End Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointBatchTest
22:44:36.0911952: Begin Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointEventTest on .NETFramework,Version=v4.5.1
  X Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointBatchTest [10s 20ms]
  Error Message:
   Unexpected change in sequence number from 800 to 791
Expected: True
Actual:   False
  Stack Trace:
     at Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointBatchTest() in D:\a\1\AzureSDKEngSystem\Net\SourceDirectory\sdk\eventhub\Microsoft.Azure.EventHubs\tests\ServiceFabricProcessor\CheckpointingTests.cs:line 81
Results File: D:\a\1\AzureSDKEngSystem\Net\SourceDirectory\sdk\eventhub\Azure.Messaging.EventHubs\tests\TestResults\net461.trx

To Reproduce
Steps to reproduce the behavior: Queue PR Build

Expected behavior
Test fails randomly
@triage-new-issues triage-new-issues bot added the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 5, 2019
@chidozieononiwu chidozieononiwu added Client This issue points to a problem in the data-plane of the library. Event Hubs labels Sep 5, 2019
@triage-new-issues triage-new-issues bot removed the needs-triage Workflow: This is a new issue that needs to be triaged to the appropriate team. label Sep 5, 2019
@chidozieononiwu chidozieononiwu mentioned this issue Sep 5, 2019
Merged
@jsquire
Copy link
Member

jsquire commented Sep 13, 2019 •
edited
Loading

This test has been marked as flaky and will be skipped in builds going forward. Tracking using #7435

@jsquire jsquire self-assigned this Sep 13, 2019
@jsquire jsquire closed this as completed Sep 13, 2019
@pakrym pakrym reopened this Feb 4, 2020
@pakrym
Copy link
Contributor

pakrym commented Feb 4, 2020

Now failing on netcoreapp:

 X Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointBatchTest [5s 56ms]
  Error Message:
   Unexpected change in sequence number from 290 to 281
Expected: True
Actual:   False
  Stack Trace:
     at Microsoft.Azure.EventHubs.Tests.ServiceFabricProcessor.CheckpointingTests.CheckpointBatchTest() in D:\a\1\s\sdk\eventhub\Microsoft.Azure.EventHubs\tests\ServiceFabricProcessor\CheckpointingTests.cs:line 81

``

This was referenced Feb 4, 2020
Closed
Merged
@jsquire
Copy link
Member

jsquire commented Feb 4, 2020 •
edited
Loading

Looks like the skip was removed; marked again and updated the issue tracking Service Fabric Processor test issues. See #9799 and #7472

@jsquire
Copy link
Member

jsquire commented Feb 4, 2020

Closing this as #9799 has merged and the test should no longer be active.

@jsquire jsquire closed this as completed Feb 4, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Mar 29, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@jsquire jsquire

Labels
Client This issue points to a problem in the data-plane of the library. Event Hubs
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@jsquire @pakrym @chidozieononiwu