Update Nightly Test Command #16892
Merged
Update Nightly Test Command #16892
Conversation
This file contains 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
|
/azp run java - core - tests |
|
No pipelines are associated with this pull request. |
|
Azure Pipelines successfully started running 1 pipeline(s). |
…dk-httpclient to prevent build failures in Java 8
|
/azp run java - core - tests |
|
Azure Pipelines successfully started running 1 pipeline(s). |
openapi-sdkautomation bot
pushed a commit
to AzureSDKAutomation/azure-sdk-for-java
that referenced
this pull request
Nov 29, 2021
loadtestservice-typescript.md-update (Azure#16892)
openapi-sdkautomation bot
pushed a commit
to AzureSDKAutomation/azure-sdk-for-java
that referenced
this pull request
Jan 5, 2022
loadtestservice-typescript.md-update (Azure#16892)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
This PR fixes a discrepancy between the testing command used during PR validation and the daily test run. The daily test run used the
testlifecycle phase instead ofverifywhich PR validation was using. This resulted in a scenario where Jacoco modified the built library byte code to capture test coverage but never cleaned up the changes as that happens during the subsequent lifecycle phase. Not cleaning up the byte code modifications resulted in CI failures when the libraries in the build set had dependencies upon each other.