k3s/test/e2e/apimachinery
Walter Fender 02bd75764c Issue 63622 - Flaky e2e/aggr test.
Investigated issue 63622. The test usually passes. When it does it seems
to take almost 30 seconds for the sample-apiserver to start returning
2xx rather than 4xx to flunder requests. On the failing tests I looked
at it was taking almost 45 seconds for the sample-apiserver to become
healthy. I bumped the wait/timeout in the test for this case to 60
seconds. I also added a log statement to make it easier to track how
long it was taking for the sample-apiserver to come up. Once we have a
bit more history I will log a bug for the long start up time.
Fixed go format error.
2018-06-11 16:05:08 -07:00
..
BUILD Merge pull request #60671 from jennybuckley/gc-test-error-message 2018-06-04 22:11:12 -07:00
aggregator.go Issue 63622 - Flaky e2e/aggr test. 2018-06-11 16:05:08 -07:00
certs.go
chunking.go
crd_watch.go apiextensions: make CreateNewCustomResourceDefinition return created CRD 2018-05-23 21:41:55 +02:00
custom_resource_definition.go apiextensions: make CreateNewCustomResourceDefinition return created CRD 2018-05-23 21:41:55 +02:00
etcd_failure.go Use pause manifest image 2018-04-06 11:00:50 +05:30
framework.go
garbage_collector.go Merge pull request #63386 from roycaihw/gc-json-patch 2018-06-06 19:56:20 -07:00
generated_clientset.go make use of simple dynamic client in test 2018-04-27 13:38:58 +08:00
initializers.go
namespace.go Use pause manifest image 2018-04-06 11:00:50 +05:30
table_conversion.go
watch.go Promote watch e2e test to conformance 2018-05-30 00:13:57 -07:00
webhook.go Set explicit labels/selector for apps/v1 Deployment/RS. 2018-05-22 13:43:07 -07:00