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

[Tables] Fix tables livetest #14797

Merged
merged 12 commits into from
Sep 9, 2020
Merged

[Tables] Fix tables livetest #14797

merged 12 commits into from
Sep 9, 2020

Conversation

bsiegel
Copy link
Member

@bsiegel bsiegel commented Sep 3, 2020

Fixes: #14798

@bsiegel bsiegel self-assigned this Sep 3, 2020
@bsiegel bsiegel added Client This issue points to a problem in the data-plane of the library. Tables labels Sep 3, 2020
@bsiegel bsiegel added this to the [2020] September milestone Sep 3, 2020
sdk/tables/tests.yml Outdated Show resolved Hide resolved
// Act & Assert
if (mode == UpdateMode.MERGE && tableClient.getTableUrl().contains("cosmos.azure.com")) {
// This scenario is currently broken when using the CosmosDB Table API
StepVerifier.create(tableClient.updateEntityWithResponse(createdEntity, true, mode))
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we split this into another test case and disable it? I feel it'll get lost as a comment since there is no issue or TODO tracking this.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, once support is merged for multiple tests with the same name (#14801) I will separate these into two test classes, one for Cosmos and one for Storage, each with their own recordings.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tracking this work in #14930

serviceClient.createTable(tableName3)
).block(TIMEOUT);

serviceClient.createTable(tableName).block(TIMEOUT);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is there a reason for splitting this into three sequential blocks rather than running them concurrently?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I was having intermittent 429 issues with failures when using Mono.when with multiple streams against the CosmosDB API.

@bsiegel
Copy link
Member Author

bsiegel commented Sep 9, 2020

/azp run

@azure-pipelines
Copy link

You have several pipelines (over 10) configured to build pull requests in this repository. Specify which pipelines you would like to run by using /azp run [pipelines] command. You can specify multiple pipelines using a comma separated list.

@bsiegel
Copy link
Member Author

bsiegel commented Sep 9, 2020

/azp run java - tables - ci

@azure-pipelines
Copy link

Azure Pipelines successfully started running 1 pipeline(s).

@bsiegel bsiegel merged commit 992ee0b into Azure:master Sep 9, 2020
@bsiegel bsiegel deleted the tables-livetest branch September 9, 2020 01:02
openapi-sdkautomation bot pushed a commit to AzureSDKAutomation/azure-sdk-for-java that referenced this pull request Jun 21, 2021
[Hub Generated] Review request for Microsoft.HybridCompute to add version preview/2021-06-10-preview (Azure#14797)

* Adds base for updating Microsoft.HybridCompute from version preview/2021-05-17-preview to version 2021-06-10-preview

* Updates readme

* Updates API version in new specs and examples

* updated the swagger

* added the missing bracket

* removed type object

* removed PatchSettings ref

* used x-ms-client-flatten

* fixed an issue

* added osProfile to the machineUpdateProperties

* removed the extra space

* fixed by npm run prettier
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
blocking-release Blocks release Client This issue points to a problem in the data-plane of the library. Tables
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[Tables] Add Live test configuration
2 participants