Files

T

Ta-Ching ChenandGitHub 1ad7ac2dcf Adopt existing orphan kubernetes resources when executor starts up (#1443 )

Previously, once the executor is deleted for reasons (like upgrade or cluster scale-in),
the new executor deletes all existing resources created by the old executor and creates
new one. This mechanism becomes a problem when there are requests connecting to the
existing pods. Also in the worst case, the cluster may not have enough resources to create
new pods and cause service downtime.

This PR let each executor type adopts existing resources before starting the executor
API services, and so the alive connections won't experience failure. However, the requests
send to the function that doesn't have alive function pods will still fail due to the
executor is in bootstrapping.

2019-11-27 23:08:45 +08:00

benchmark

Update staticcheck version and fix all warnings (#1381 )

2019-11-05 18:09:12 +08:00

cluster

Add Terraform configuration and upgrade helm version (#1194 )

2019-05-31 15:44:42 +08:00

tests

Revert "Try to fix flaky canary test (#1441 )" (#1442 )

2019-11-27 16:19:33 +08:00

upgrade

Switch from fluentd to fluentbit for log forwarding (#1086 )

2019-03-18 15:42:37 +08:00

build.sh

Pre-built docker go module dependency cache image (#1318 )

2019-09-18 05:07:53 +08:00

init_tools.sh

Allow using URL as archive source when creating functions (#1360 )

2019-10-28 22:37:13 +08:00

README.md

Update go dependencies (#1240 )

2019-08-23 16:17:12 +08:00

run_test.sh

Test framework improvement (#1128 )

2019-05-23 22:52:39 +08:00

test_utils.sh

Add huge response body test (#1437 )

2019-11-26 12:50:41 +08:00

test.sh

Fix CI unable to start test due to the same travis build ID (#1246 )

2019-07-25 15:54:12 +08:00

utils.sh

Adopt existing orphan kubernetes resources when executor starts up (#1443 )

2019-11-27 23:08:45 +08:00

README.md

Test Framework

Prerequisite tools

GNU parallel >= 20161222

If you want to run test on Mac, you also need to install GNU tools for command compatibility. With Homebrew, you can get them by:

   brew install coreutils findutils gnu-sed

Run a single test

cd $REPO/test

# run 'tests/test_node_hello_http.sh'
./tests/test_node_hello_http.sh

# if you want to preserve the resources that created by test for debug
export TEST_NOCLEANUP=yes
./tests/test_node_hello_http.sh

# run 'tests/test_environments/test_go_env.sh' with custom images
export GO_RUNTIME_IMAGE=my.docker.repo/go-env:test
./tests/test_environments/test_go_env.sh

Run tests in parallel

NOTE: Some tests will consume lots of resources and cause the test fail.

Example: Run tests with 4 concurrent jobs.

cd $REPO/test

export JOBS=4
./run_test.sh \
    tests/test_backend_poolmgr.sh \
    tests/test_node_hello_http.sh \
    tests/test_pass.sh \
    tests/test_specs/test_spec.sh

# The test output will be available in logs/
cat logs/test_backend_poolmgr.sh.log

# The summary report will be saved to logs/_recap
cat logs/_recap