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

Stabilize most commonly failing tests #36956

Merged
merged 8 commits into from
Sep 27, 2023

Conversation

alzimmermsft
Copy link
Member

@alzimmermsft alzimmermsft commented Sep 26, 2023

Description

Fixes #36666

Attempts to stabilize the most commonly failing tests in the Core pipeline.

All SDK Contribution checklist:

  • The pull request does not introduce [breaking changes]
  • CHANGELOG is updated for new features, bug fixes or other significant changes.
  • I have read the contribution guidelines.

General Guidelines and Best Practices

  • Title of the pull request is clear and informative.
  • There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

  • Pull request includes test coverage for the included changes.

@alzimmermsft alzimmermsft self-assigned this Sep 26, 2023
@github-actions github-actions bot added the Azure.Core azure-core label Sep 26, 2023
@azure-sdk
Copy link
Collaborator

API change check

API changes are not detected in this pull request.

if (proxyRetry) {
// Exhausted retry attempt return an error.
return Mono.error(new HttpProxyHandler.HttpProxyConnectException(
"Failed to connect to proxy. Status: 407", responseAndHeaders.getT2()));
Copy link
Member

Choose a reason for hiding this comment

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

Curious why we can't use response.getHeaders() here?

Copy link
Member Author

Choose a reason for hiding this comment

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

This takes the Netty HttpHeaders object, not the azure-core HttpHeaders.

try {
classPath = Class.forName(className).getCanonicalName();
return Class.forName(className).getCanonicalName();
Copy link
Member

Choose a reason for hiding this comment

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

nit: maybe call overload with initialize flag set to false to minimize side-effects?

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'm a bit confused on this comment, this is a utility method to help the String-based constructor as this has to be the first statement in a constructor.

// 23 characters that will be ASCII
byte[] bytes = new byte[23];

// yyyy-
Copy link
Member

Choose a reason for hiding this comment

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

year 10000 will be a tough one 🤣

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'll be worried when I see that day 😄

@alzimmermsft alzimmermsft merged commit fd9c56b into Azure:main Sep 27, 2023
43 checks passed
@alzimmermsft alzimmermsft deleted the AzAll_StabilizeSomeTests branch September 27, 2023 20:13
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Azure.Core azure-core
Projects
None yet
Development

Successfully merging this pull request may close these issues.

java - core - ci flaky tests: attestation
3 participants