Skip to content

Releases: grpc/test-infra

Release 0.9.0

30 Aug 16:53
d408f85
Compare
Choose a tag to compare
Release 0.9.0 Pre-release
Pre-release

Recent notable changes:

  • Make ready container write out the annotation as JSON (#199).
  • Save node info to a json file (#215).
  • Make test names in report TestGrid-friendly (#218).

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.
  • metadata.json and node_info.json files are generated but the data is not populated in BigQuery because corresponding changes made in grpc/grpc are not included in Release v1.39.1

Release 0.8.0

04 Aug 21:00
0a26683
Compare
Choose a tag to compare
Release 0.8.0 Pre-release
Pre-release

Recent notable changes:

  • Update to kubebuilder3. (#209).

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.

Release 0.7.3

03 Aug 01:39
8202c18
Compare
Choose a tag to compare
Release 0.7.3 Pre-release
Pre-release

Recent notable changes:

  • Separate deployment of cleanup agent from main process (#202).
  • Delete cleanup agent from codebase (#204).

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.

Release 0.7.2

21 Jul 23:12
66eb819
Compare
Choose a tag to compare
Release 0.7.2 Pre-release
Pre-release

Recent notable changes:

  • Ignore empty default pool label if pool is specified in the load test (#201).
  • Initial fixes for xml report generation (#198).
  • Fix php7 flakiness problem (#197).

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.

Release 0.7.1

05 Jul 23:38
4d95ed4
Compare
Choose a tag to compare
Release 0.7.1 Pre-release
Pre-release

Recent notable changes:

  • Fix executable path in Java load test example with prebuilt image (#190).
  • Update driver timeout (#192).
  • Feature/add php7_protobuf_c (#195).

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.

Release 0.7.0

24 Jun 01:01
581dbd5
Compare
Choose a tag to compare
Release 0.7.0 Pre-release
Pre-release

Recent notable changes:

  • Add timeout for workers. #182
  • Set default test suites name to empty string. #183

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.

Release 0.6.1

14 Jun 19:48
29ec42a
Compare
Choose a tag to compare
Release 0.6.1 Pre-release
Pre-release

Recent notable changes:

  • Fix envtest flakiness (#175)
  • Use real name instead of uuid (#173)
  • Feature/add driver timeout (#172)
  • Delete references to label "loadtest" from controller (#169)
  • Use "php7" language name in defaults and examples (#164)
  • Add LoadTest state information to kubectl get (#163)
  • Log details of kubernetes API errors in the runner (#160)
  • Generate JUnit XML reports in the runner (#157)
  • Feature/parallel building (#150)
  • Test runner tool (#149)
  • Improvements to prebuilt docker image builds (#145)

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 OSS benchmarking driver failed to connect to workers.
  • PHP7 tests fail to find default images (to be fixed in the next release).
  • Workers may keep running after test timeout (to be fixed in a follow-up to #172.

Release 0.5.2

06 May 07:40
bcae794
Compare
Choose a tag to compare
Release 0.5.2 Pre-release
Pre-release

Recent notable changes:

  • Schedules controller and cleanup agent on nodes with a "default-system-pool" label (#144).

Known issues include:

  • Python OSS benchmarking client fails to yield initial status to driver.
  • Node.js OSS benchmarking driver shows no action after receiving final status from client.
  • PHP OSS benchmarking driver failed to connect to workers.
  • Timeouts may be flaky (mitigated by #109).
  • Controller integration tests are flaky due to the use of envtest.

Release 0.5.1

05 May 07:17
e0bdb3e
Compare
Choose a tag to compare
Release 0.5.1 Pre-release
Pre-release

Recent notable changes:

  • Move controller and cleanup agent to a separate pool. #143
  • Removes resource quotas on the controller and cleanup agent. #141
  • Ready container timeouts now match load test timeouts. #133
  • System paths are trimmed from the binaries. #136
  • Prebuilt images were added for most languages.

Known issues include:

  • Python OSS benchmarking client fails to yield initial status to driver.
  • Node.js OSS benchmarking driver shows no action after receiving final status from client.
  • PHP OSS benchmarking driver failed to connect to workers.
  • Timeouts may be flaky (mitigated by #109).
  • Controller integration tests are flaky due to the use of envtest.

Release 0.5.0

09 Apr 01:46
3f81e61
Compare
Choose a tag to compare
Release 0.5.0 Pre-release
Pre-release

Recent notable changes:

  • Support and example for Node.js load test is added. #108
  • Support and example for PHP load test is added. #112
  • Add server port flag and explanation to example. #119
  • Resync pods after cache invalidation. #120

Known issues include:

  • Python OSS benchmarking client fails to yield initial status to driver.
  • Node.js OSS benchmarking driver shows no action after receiving final status from client.
  • PHP OSS benchmarking driver failed to connect to workers.
  • Timeouts may be flaky (mitigated by #109).
  • Controller integration tests are flaky due to the use of envtest.