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

Try to make tomcat async servlet exception test less flaky #4772

Merged
merged 1 commit into from
Dec 2, 2021

Conversation

laurit
Copy link
Contributor

@laurit laurit commented Dec 1, 2021

According to https://ge.opentelemetry.io/scans/tests?search.relativeStartTime=P7D&search.tags=CI&search.timeZoneId=Europe/Tallinn&tests.sortField=FLAKY&tests.unstableOnly=true test exception with async servlet on tomcat is the most flaky test we have. Here is an attempt to make it stable by forcing response to be sent before exception is thrown which could trigger tomcat resetting connection to the client.

Copy link
Member

@trask trask left a comment

Choose a reason for hiding this comment

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

👍🤞

(more weirdness with exceptions thrown from AsyncContext.start() 😅)

@trask trask merged commit bbb5717 into open-telemetry:main Dec 2, 2021
RashmiRam pushed a commit to RashmiRam/opentelemetry-auto-instr-java that referenced this pull request May 23, 2022
@laurit laurit deleted the tomcat-async-exception branch July 6, 2023 17:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants