Update airbase to version 124#11900
Conversation
|
#11856 is required first. |
7bbb297 to
7fe24d8
Compare
|
@nineinchnick build is red. can you also resolve #11294 TODOs ? |
This version updated maven-surefire-plugin to 3.0.0-M6, which should reduce maximum memory usage in tests.
7fe24d8 to
e16a7af
Compare
|
This should be easy to reproduce locally. I'll investigate since the surefire update was supposed to help with max mem usage.
which is easily reproducible locally, but also locally on master. There might be something about how I run the tests, my env or the test might be flaky, but this doesn't show up in CI on master. Anyway, it'll take me a while to sort these things out. |
|
I also just ran into this again locally in |
|
We're hitting this issue https://issues.apache.org/jira/browse/SUREFIRE-2068 that's not present in M5, looks like this would be an upgrade blocker. |
It seems we should downgrade surefire in airbase. So sad. |
I agree but I'll check what exactly triggers this and if there workarounds. |
| { | ||
| public TestingPageSourceProvider() | ||
| { | ||
| System.out.println(); |
There was a problem hiding this comment.
:)
anyway, crashing whenever we have System.out isn't practcal....
There was a problem hiding this comment.
I know we probably won't do this update, but I wanted to check if that'll work and are there going to be any gainst in job times.
I don't want to start bikeshedding, but are there any best practices about tests using logging or printing directly?
There was a problem hiding this comment.
i usually prefer logging to direct sout
There was a problem hiding this comment.
Note that Surefire itself doesn't like sout since it uses that for passing control messages and crashes depending on when a sout is done.
Newer versions have this fixed though it seems but required some config - https://stackoverflow.com/a/61936537/4594699
There was a problem hiding this comment.
Newer versions have this fixed though it seems but required some config - https://stackoverflow.com/a/61936537/4594699
for posterity
- this references https://issues.apache.org/jira/browse/SUREFIRE-1614
- and suggests to use
<plugin> <artifactId>maven-surefire-plugin</artifactId> <version>3.0.0-M5</version> <configuration> <!-- Activate the use of TCP to transmit events to the plugin --> <forkNode implementation="org.apache.maven.plugin.surefire.extensions.SurefireForkNodeFactory"/> </configuration> </plugin>
There was a problem hiding this comment.
There's a comment in the Surefire Jira issue that it is supposed to be fixed on master, so I guess we can wait for the next release. I'll close this PR until then.
There was a problem hiding this comment.
follow-up: downgrade surefire in airbase: airlift/airbase#313
Description
This version updated maven-surefire-plugin to 3.0.0-M6,
which should reduce maximum memory usage in tests.
other
test execution
n/a
Related issues, pull requests, and links
Documentation
(x) No documentation is needed.
( ) Sufficient documentation is included in this PR.
( ) Documentation PR is available with #prnumber.
( ) Documentation issue #issuenumber is filed, and can be handled later.
Release notes
(x) No release notes entries required.
( ) Release notes entries required with the following suggested text: