Skip to content

Fix release cron workflow - #224

Closed
serdarozerr wants to merge 34 commits into
mainfrom
fix-release-cron
Closed

serdarozerr wants to merge 34 commits into
mainfrom
fix-release-cron

Conversation

@serdarozerr

Copy link
Copy Markdown
Contributor

Release cron workflow was failing because of new tagged benchmarker unit tests.

Add a subprocess-based benchmark harness under benchmark/ that measures
wall-clock put/get performance of the storage-cli binary without requiring
a CF deployment, BOSH director, or CC database.

Each operation is timed independently including process startup and SDK
behaviour. SHA-256 integrity is verified outside the timer after each get.
Two profiles are supported: quick (4 sizes, 3 samples) and full (5 sizes,
5 samples). Results are reported.

The package is excluded from the main build via //go:build benchmark and
tested with Ginkgo using injectable mock runners, no credentials required.
- Failure calculatio for both get and put refactored
- aliyun tool instalation guarded
- benchmark tests are protected with build tag
teardowd-infrastrcuture.sh tries to delete lambda function that might create probles during parallel runs. Deletion logic moved into run-integration-aws-iam.sh script because it manages the lifecyle(create and deletes afterwards) of lamda function. Also resiliency is improved
 for deleting.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Development

Successfully merging this pull request may close these issues.

1 participant