-
Notifications
You must be signed in to change notification settings - Fork 183
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
Update index table when generate service level readme #4632
Conversation
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
26f6bb8
to
98d4359
Compare
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
While I see you're running this through the pipeline several times to validate that it works in an ad-hoc fashion, shouldn't you also have actual tests for this to be able to validate this again later when we come back to it for future changes? |
I found the outputs are different if we ran the pipeline multiple times. I want to understand what happened there. My local test is fine before I found this. I have validated the behavior in local. But we need to run at least twice in pipeline to make sure the output are all as expected. |
The following pipelines have been queued for testing: |
cfe00d9
to
0d9e779
Compare
The following pipelines have been queued for testing: |
Shouldn't you also probably have a test script in addition to the ad-hoc testing you're doing? That way when someone comes back to this later, they'll have the tests you write to help them know they didn't break anything. |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
1 similar comment
The following pipelines have been queued for testing: |
72c5f5f
to
0013ccb
Compare
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
eng/common/scripts/Service-Level-Readme-Automation-Functions.ps1
Outdated
Show resolved
Hide resolved
eng/common/scripts/Service-Level-Readme-Automation-Functions.ps1
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
One comment about the helpers script but otherwise looks good.
The following pipelines have been queued for testing: |
123601a
to
e6cd5f8
Compare
The following pipelines have been queued for testing: |
The following pipelines have been queued for testing: |
Hello @azure-sdk! Because this pull request has the p.s. you can customize the way I help with merging this pull request, such as holding this pull request until a specific person approves. Simply @mention me (
|
Python
azure-developer-loadtesting
package did not show up in preview page. After checkup, I found our index table is lack of ability of update.Use the PR to fix the issue: #4646.
Also fixed the issue: #4002
Testing pipeline: https://dev.azure.com/azure-sdk/internal/_build/results?buildId=1971665&view=results
Service readme update: MicrosoftDocs/azure-docs-sdk-python@fa4a19f
Python
load-testing
preview service readme update: MicrosoftDocs/azure-docs-sdk-python@fa4a19f#diff-e72fa81fcf60a88d964ba37bab8f4118f8dff8b3db96758b98e20031796681e1