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

[service-bus] Fix issue with live tests failing on session-based tests #10325

Conversation

richardpark-msft
Copy link
Member

@richardpark-msft richardpark-msft commented Jul 29, 2020

A service-side change made it so setting the partition id and session id to different values an error in some cases where, before, it would have been incorrect but harmless.

This fixes our test data so we don't run afoul of that rule. I've filed an issue (#10326) to deal with two problems that came out as a result of this.

…sessionId and partitionKey is now considered a failure.
@richardpark-msft
Copy link
Member Author

/azp run js - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@HarshaNalluru
Copy link
Member

Looks like there are still some failures.

@richardpark-msft
Copy link
Member Author

/azp run js - servicebus - tests

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@richardpark-msft
Copy link
Member Author

Looks like there are still some failures.

Yeah, there were a few more spots that were toggling the sessionId without also updating the partitionKey.

I also have a test failure that I introduced when I accidentally merged the BatchingReceiverLite changes without re-running the live tests (facepalm).

I believe I got them all now, just rerunning.

@richardpark-msft richardpark-msft merged commit 9947ed8 into Azure:master Jul 29, 2020
@richardpark-msft richardpark-msft deleted the richardpark-sb-build-failure-investigation branch July 29, 2020 21:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants