Releases: grpc/test-infra
Releases · grpc/test-infra
Release 1.4.2
What's Changed
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Full Changelog: v1.4.1...v1.4.2
Release 1.4.1
What's Changed
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
New Contributors
Full Changelog: v1.4.0...v1.4.1
Release 1.4.0
What's Changed
- Make collection of Prometheus data be controlled by an annotation. by @wanlin31 in #315
- Enable driver to be able to use image supplied from load test configuration. by @wanlin31 in #316
- Add PSM dashboard to OSS benchmark dashboard. by @wanlin31 in #317
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Full Changelog: v1.3.0...v1.4.0
Release 1.3.0
What's Changed
- Add all psm related examples, by @wanlin31 in #304
- Collect logs from all containers and add log to test properties, by @wanlin31 in #306
- Remove psm examples for ruby and csharp, by @wanlin31 in #310
- Update support for csharp core implementation, by @wanlin31 in #312
- Update driver version to 1.47.0, by @paulosjca in #314
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Full Changelog: v1.2.0...v1.3.0
Release 1.2.0
What's Changed
- Add pre-built image for grpc-dotnet, by @jtattermusch in #285
- Set default location for PSM images, by @paulosjca in #286
- Add complete configuration for prometheus installation, by @wanlin31 in #287
- Update driver version to v1.45.0, by @paulosjca in #288
- Add prometheus query to driver's run container, by @wanlin31 in #289
- Change driver version, by @wanlin31 in #291
- Update deployment guide, by @wanlin31 in #293
- Add grpc-dotnet support (contd.), by @jtattermusch in #294
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Full Changelog: v1.1.0...v1.2.0
Release 1.1.0
What's Changed
- Feature/envoy & xds server graceful exit by @wanlin31 in #268
- Pin driver version by @paulosjca in #277
- Integrate of PSM into test-infra by @wanlin31 in #275
- Add examples for PSM tests. by @wanlin31 in #278
- Add initial documentation on PSM benchmarks. by @paulosjca in #281
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Full Changelog: v1.0.0...v1.1.0
Release 1.0.0
Driver version: ccd8d577d063f97d02ce80a134c33cf51de530d1 (grpc/grpc#28805).
What's Changed
- Update kustomize version by @paulosjca in #271
- Rename run images flag in configuration generator by @paulosjca in #270
- Add deployment guide by @paulosjca in #272
- Update podbuilder for multiple run container by @wanlin31 in #273
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
- Driver must be pinned to grpc/grpc#28805, since that is not included in v1.44.0.
Full Changelog: v0.11.0...v1.0.0
Release 0.11.1
What's Changed
- Driver version updated from v1.43.2 (grpc/grpc#28706) to grpc/grpc#28805. This change fixes the driver error seen in tests that save data to BigQuery.
Known issues
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Release 0.11.0
What's Changed
Highlights: dashboard code and documentation, and breaking change in run containers configuration (from one per pod to a list).
- Support timeout when building images by @jtattermusch in #232
- Update PHP7 version for OSS benchmarks images by @paulosjca in #234
- Add loadtest name as property by @brandonpaiz in #236
- Update dotnet SDK and runtime in C# build by @jtattermusch in #237
- Update README by @paulosjca in #246
- Add dashboard code and configuration by @brandonpaiz in #244
- Update base docker images to golang:1.16 by @paulosjca in #262
- Delete unused submodule
grpc/grpc-proto
by @paulosjca in #265 - Delete unused submodule
googleapis/googleapis
by @paulosjca in #266 - Update the run containers to be a generic list of containers by @wanlin31 in #267
- Update README and other doc by @paulosjca in #269
Full Changelog: v0.10.0...v0.11.0
Known issues
- Important: Driver exits with an error when saving data to BigQuery (will be fixed in a patch release).
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
Release 0.10.0
Recent notable changes:
- Use the message attribute to store error message in xml reports. by @paulosjca in #219
- Add runner flag to delete successful load tests immediately. by @paulosjca in #225
- Store pod logs by @brandonpaiz in #227
- Assorted improvements to configs and docker images. by @jtattermusch in #228
- Use optimized build where applicable (it was missing in some places)
- Update Java Docker images to Java 11
- Improve cxx pre-build image
- Use
nproc
to get accurate processor count for JVM loadtests by @brandonpaiz in #231
Known issues include:
- Python OSS benchmarking client fails to yield initial status to driver (applies only to python_asyncio).
- Node.js OSS benchmarking driver shows no action after receiving final status from client.
- PHP7 worker build sometimes gets stuck forever (in a completely unexpected place in docker build)