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

updates integration tests and benchmarks to use log4j #224

Merged
merged 2 commits into from
Dec 14, 2023
Merged

Conversation

codefromthecrypt
Copy link
Member

Similar to Brave, we don't want a large amount of clutter. To reduce a lot of it, I moved anything that uses MockWebServer to an IT (because it spams logs). I didn't move normal tests to log4j because we have a log capturing test that would fail. If someone wants to take a pass later at that, they could.

<include>**/IT*.java</include>
</includes>
<!-- Try to prevent flakes in CI -->
<reuseForks>false</reuseForks>
Copy link
Member Author

Choose a reason for hiding this comment

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

moved config from our normal failsafe

@@ -384,10 +406,6 @@
<plugin>
<artifactId>maven-surefire-plugin</artifactId>
<version>${maven-surefire-plugin.version}</version>
<configuration>
<!-- Ensures root cause ends up in the console -->
<trimStackTrace>false</trimStackTrace>
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 was a carry-over from zipkin with armeria

Similar to Brave, we don't want a large amount of clutter. To reduce a
lot of it, I moved anything that uses MockWebServer to an IT (because it
spams logs). I didn't move normal tests to log4j because we have a log
capturing test that would fail. If someone wants to take a pass later at
that, they could.

Signed-off-by: Adrian Cole <[email protected]>
@codefromthecrypt
Copy link
Member Author

after this is in, I'll add invoker tests for the rabbitmq amqp-client which proves we can use recent versions and avoid CVE distraction while still maintaining compat (similar to okhttp). Finally, I'll do the same for spring and we're ready to roll ideally with no CVE scares.

@codefromthecrypt codefromthecrypt merged commit 8e86704 into master Dec 14, 2023
2 checks passed
@codefromthecrypt codefromthecrypt deleted the log4j branch December 14, 2023 07:16
@codefromthecrypt
Copy link
Member Author

Thanks for helping me consume so much Azure VM time @anuraaga!

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.

2 participants