{CI} Log each extension recording test time#24498
Draft
{CI} Log each extension recording test time#24498
Conversation
ghost
added
ghost
requested review from
jiasli,
jsntcy,
kairu-ms,
wangzelin007 and
yonzhan
Collaborator
|
CI |
Member
Author
|
/azp run |
|
Azure Pipelines successfully started running 2 pipeline(s). |
yonzhan
modified the milestones:
April 2023 (2023-04-25),
May 2023 (2023-05-23) - For Build (Breaking change release)
yonzhan
modified the milestones:
May 2023 (2023-05-23) - For Build (Breaking change release),
June 2023 (2023-07-04)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Before building a extension regression test pipeline, we need to know how long each extension takes to run recording tests.
This PR aims to get a result of extension recording test time using PR's CI pipeline.
This checklist is used to make sure that common guidelines for a pull request are followed.
The PR title and description has followed the guideline in Submitting Pull Requests.
I adhere to the Command Guidelines.
I adhere to the Error Handling Guidelines.