Disable log ingestion test on macOS #42163
Merged
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
…tly test on macOS
jeanbisutti
requested review from
srnagar,
jairmyree,
lmolkova and
a team
as code owners
jeanbisutti
requested review from
sarangan12,
joshfree,
pvaneck,
KevinBlasko,
KarishmaGhiya,
ToddKingMSFT and
gulopesd
|
API change check API changes are not detected in this pull request. |
trask
approved these changes
Oct 2, 2024
|
Also disable |
srnagar
approved these changes
Oct 2, 2024
mssfang
pushed a commit
to mssfang/azure-sdk-for-java
that referenced
this pull request
Oct 21, 2024
* Disable LogsIngestionAsyncClientTest.testUploadLogsInBatchesConcurrently test on macOS * Also disable testUploadLogsInBatches on macOS
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.
In #42134 and #42135, the
LogsIngestionAsyncClientTest.testUploadLogsInBatchesConcurrentlytest fails with themacoslatest_18_False_False_surefiretestfailsafeintegrationtestfailsafeverifybuild (see for example: https://dev.azure.com/azure-sdk/public/_build/results?buildId=4192172&view=logs&j=8b6ce078-9252-5859-2eab-25597345a671&t=2a829ff0-21e6-5645-6029-72db302ab93f). For both PRs, I have tried to restartmacoslatest_18_False_False_surefiretestfailsafeintegrationtestfailsafeverifyseveral times, without success.With a PR we could bypass the CI check, but it won't work to do a new release of the OTel Java exporter.