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

DevServices: logs too verbose #16203

Closed
FroMage opened this issue Apr 2, 2021 · 1 comment
Closed

DevServices: logs too verbose #16203

FroMage opened this issue Apr 2, 2021 · 1 comment
Assignees
Labels
area/devmode kind/bug Something isn't working

Comments

@FroMage
Copy link
Member

FroMage commented Apr 2, 2021

I just started an app with DevServices and I got this logorrhea:

2021-04-02 09:39:53,979 INFO  [org.tes.doc.DockerClientProviderStrategy] (build-4) Loaded org.testcontainers.dockerclient.EnvironmentAndSystemPropertyClientProviderStrategy from ~/.testcontainers.properties, will try it first
2021-04-02 09:39:54,479 INFO  [org.tes.doc.DockerClientProviderStrategy] (build-4) Found Docker environment with Environment variables, system properties and defaults. Resolved dockerHost=unix:///var/run/docker.sock
2021-04-02 09:39:54,480 INFO  [org.tes.DockerClientFactory] (build-4) Docker host IP address is localhost
2021-04-02 09:39:54,518 INFO  [org.tes.DockerClientFactory] (build-4) Connected to docker: 
  Server Version: 19.03.13
  API Version: 1.40
  Operating System: Ubuntu 20.10
  Total Memory: 32013 MB
2021-04-02 09:39:54,521 INFO  [org.tes.uti.ImageNameSubstitutor] (build-4) Image name substitution will be performed by: DefaultImageNameSubstitutor (composite of 'ConfigurationFileImageNameSubstitutor' and 'PrefixingImageNameSubstitutor')
2021-04-02 09:39:55,650 INFO  [org.tes.DockerClientFactory] (build-4) Ryuk started - will monitor and terminate Testcontainers containers on JVM exit
2021-04-02 09:39:55,651 INFO  [org.tes.DockerClientFactory] (build-4) Checking the system...
2021-04-02 09:39:55,651 INFO  [org.tes.DockerClientFactory] (build-4) ✔︎ Docker server version should be at least 1.6.0
2021-04-02 09:39:55,824 INFO  [org.tes.DockerClientFactory] (build-4) ✔︎ Docker environment should have more than 2GB free disk space
2021-04-02 09:39:55,970 INFO  [🐳 .6.12]] (build-4) Creating container for image: postgres:9.6.12
2021-04-02 09:39:56,153 INFO  [🐳 .6.12]] (build-4) Starting container with ID: 3e77926f877410807a40fb18872211ae659f76c602aac51aa30891cb7c8950bf
2021-04-02 09:39:56,599 INFO  [🐳 .6.12]] (build-4) Container postgres:9.6.12 is starting: 3e77926f877410807a40fb18872211ae659f76c602aac51aa30891cb7c8950bf
2021-04-02 09:40:01,655 INFO  [🐳 .6.12]] (build-4) Container postgres:9.6.12 started in PT5.830455S

I'm pretty sure that this should be enough:

2021-04-02 09:39:56,599 INFO  [🐳 .6.12]] (build-4) Starting DevServices [postgres:9.6.12] using docker [localhost]: 3e77926f877410807a40fb18872211ae659f76c602aac51aa30891cb7c8950bf

The rest is useless, no?

@FroMage FroMage added kind/bug Something isn't working area/devmode labels Apr 2, 2021
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Sep 3, 2021
This changes the mass of Dev Services logging to a single status line
per starting container. This allows the user to see that progress is
happening, without flooding the console.

If the operation fails all captured output is dumped.

Fixes quarkusio#16203
@stuartwdouglas
Copy link
Member

I have come up with a fix where the log messages are displayed on the status bar at the bottom, so the user still sees progress, then disappear once the container is up.

If startup fails the messages are dumped.

stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Sep 7, 2021
This changes the mass of Dev Services logging to a single status line
per starting container. This allows the user to see that progress is
happening, without flooding the console.

If the operation fails all captured output is dumped.

Fixes quarkusio#16203
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Sep 7, 2021
This changes the mass of Dev Services logging to a single status line
per starting container. This allows the user to see that progress is
happening, without flooding the console.

If the operation fails all captured output is dumped.

Fixes quarkusio#16203
stuartwdouglas added a commit to stuartwdouglas/quarkus that referenced this issue Sep 7, 2021
This changes the mass of Dev Services logging to a single status line
per starting container. This allows the user to see that progress is
happening, without flooding the console.

If the operation fails all captured output is dumped.

Fixes quarkusio#16203
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/devmode kind/bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants