Added very simple stress test which scales fleets up/down and basic stress test harness #571
Conversation
jkowalski
force-pushed
the
stress-test
branch
2 times, most recently
from
d9b18bf to
8b61339
Compare
|
Build Failed 😱 Build Id: 7e5cece7-4464-4707-9348-83a8c990ea0f To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
|
Build Failed 😱 Build Id: 90493a93-f89a-4281-9322-00d9561dd459 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
|
Build Failed 😱 Build Id: f0a40d04-966f-4de5-905e-e13f3470907b To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
jkowalski
force-pushed
the
stress-test
branch
2 times, most recently
from
a310f83 to
f3ed5f7
Compare
|
Build Failed 😱 Build Id: 246e5906-270c-401e-bde7-c2eecd038390 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
|
Build Succeeded 👏 Build Id: 3cc6a6ee-f956-4b58-8026-311c02985bb6 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
jkowalski
force-pushed
the
stress-test
branch
from
f3ed5f7 to
e54a76a
Compare
|
Build Failed 😱 Build Id: 640b879c-5782-4eb2-b0ee-12c18366b1dc To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
jkowalski
force-pushed
the
stress-test
branch
from
e54a76a to
c544e07
Compare
|
Build Failed 😱 Build Id: 281b4232-3ca8-424b-a5ba-11f3b9e460f6 To get permission to view the Cloud Build view, join the agones-discuss Google Group. |
jkowalski
force-pushed
the
stress-test
branch
from
c544e07 to
c19ec03
Compare
…and basic stress test harness. The same test is used during regular e2e tests, except it runs just a few iterations on smaller fleets. To run stress test simply invoke `make stress-test-e2e` optionally passing `STRESS_TEST_LEVEL`, which controls the fleet sizes to be used (1..100, defaults to 20). Depending on stress test level, you may need a cluster with lots of capacity. By convention 'make stress-test-e2e' runs all test cases whose names include 'StressTest' and ignores everything else.
jkowalski
force-pushed
the
stress-test
branch
from
c19ec03 to
22313b8
Compare
|
Build Succeeded 👏 Build Id: 0534a626-6559-40e9-a658-e472038f3fbf The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
|
Build Succeeded 👏 Build Id: 9157a5c0-bd11-4075-b110-60d199394f53 The following development artifacts have been built, and will exist for the next 30 days:
A preview of the website (the last 30 builds are retained): To install this version:
|
markmandel
added
area/build-tools
The same test is used during regular e2e tests, except it runs just a few iterations on smaller fleets.
To run stress test simply invoke
make stress-test-e2eoptionally passingSTRESS_TEST_LEVEL, which controls the fleet sizes to be used (1..100, defaults to 20). Depending on stress test level, you may need a cluster with lots of capacity.By convention 'make stress-test-e2e' runs all test cases whose names include 'StressTest' and ignores everything else.