-
Notifications
You must be signed in to change notification settings - Fork 2.8k
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
MongoDB test cluster far too verbose #11844
Labels
Milestone
Comments
/cc @loicmathieu, @evanchooly |
I agree, however there is one problem with this: The tests that actually create a Mongo cluster... |
I'll take a quick (less than an hour look and see if we can remove the logs) |
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 3, 2020
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 3, 2020
Relates to: quarkusio#11844
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 3, 2020
geoand
added a commit
to geoand/quarkus
that referenced
this issue
Sep 3, 2020
Relates to: quarkusio#11844
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 4, 2020
gsmet
pushed a commit
to gsmet/quarkus
that referenced
this issue
Sep 4, 2020
Relates to: quarkusio#11844
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It's very hard to grab the output of the MongoDB extension tests given how the MongoDB test cluster is chatty.
I think we should get rid of flapdoodle and start a MongoDB cluster using the usual Maven plugin and be consistent with the rest of the test suite.
I don't know how chatty it will be so we might have to pass it options.
The text was updated successfully, but these errors were encountered: