-
-
Notifications
You must be signed in to change notification settings - Fork 10.2k
Closed
Labels
area/testCategorizes issue or PR as related to testingCategorizes issue or PR as related to testinggood first issuegood first issue Good for beginnersgood first issue Good for beginners
Description
- I have checked the discussions
- I have searched the issues of this repository and believe that this is not a duplicate.
- I have checked the FAQ of this repository and believe that this is not a duplicate.
Describe the bug
Some tests run a little slow.
To Reproduce
Steps to reproduce the behavior:
- run com.ctrip.framework.apollo.biz.service.AccessKeyServiceTest
log
[WARN] org.springframework.cloud.loadbalancer.config.LoadBalancerCacheAutoConfiguration$LoadBalancerCaffeineWarnLogger - Spring Cloud LoadBalancer is currently working with the default cache. While this cache implementation is useful for development and tests, it's recommended to use Caffeine cache in production.You can switch to using Caffeine cache, by adding it and org.springframework.cache.caffeine.CaffeineCacheManager to the classpath.
[WARN] com.netflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient - Request execution failed with message: I/O error on GET request for "http://localhost:8761/eureka/apps/": Connect to localhost:8761 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:8761 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
[WARN] com.netflix.discovery.DiscoveryClient - Using default backup registry implementation which does not do anything.
[WARN] com.netflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient - Request execution failed with message: I/O error on POST request for "http://localhost:8761/eureka/apps/UNKNOWN": Connect to localhost:8761 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect; nested exception is org.apache.http.conn.HttpHostConnectException: Connect to localhost:8761 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused: connect
[WARN] com.netflix.discovery.DiscoveryClient - DiscoveryClient_UNKNOWN/LAPTOP-PJ6N2E8S:0 - registration failed Cannot execute request on any known server
com.netflix.discovery.shared.transport.TransportException: Cannot execute request on any known server
at com.netflix.discovery.shared.transport.decorator.RetryableEurekaHttpClient.execute(RetryableEurekaHttpClient.java:112)
at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.register(EurekaHttpClientDecorator.java:56)
at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator$1.execute(EurekaHttpClientDecorator.java:59)
at com.netflix.discovery.shared.transport.decorator.SessionedEurekaHttpClient.execute(SessionedEurekaHttpClient.java:77)
at com.netflix.discovery.shared.transport.decorator.EurekaHttpClientDecorator.register(EurekaHttpClientDecorator.java:56)
at com.netflix.discovery.DiscoveryClient.register(DiscoveryClient.java:876)
at com.netflix.discovery.InstanceInfoReplicator.run(InstanceInfoReplicator.java:121)
at com.netflix.discovery.InstanceInfoReplicator$1.run(InstanceInfoReplicator.java:101)
at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
at java.base/java.lang.Thread.run(Thread.java:829)
[WARN] com.netflix.discovery.InstanceInfoReplicator - There was a problem with the instance info replicator
This won't cause test failure, but we can speed up the test by close it.
Expected behavior
Test should run as fast as possible.
Screenshots
None.
Additional Details & Logs
- Version 2.1.0-SNAPSHOT
- Error logs
- Configuration
- Platform and Operating System: Win11 21H1
one of solution
Some tests doesn't need to use registy, we can disable it by add
spring.cloud.discovery.enabled=false
in @SpringBootTest
properties or other place.
On my own machine, it can decrease test time consuming from 22s to 12s.
Metadata
Metadata
Assignees
Labels
area/testCategorizes issue or PR as related to testingCategorizes issue or PR as related to testinggood first issuegood first issue Good for beginnersgood first issue Good for beginners