Skip to content

v0.27.1
Compare
Choose a tag to compare
@na-- na-- released this 30 Jul 10:22
· 5411 commits to master since this release
v0.27.1
This tag was signed with the committer’s verified signature. The key has expired.
na-- Ned Andreev
GPG key ID: F22E11F404F3CB49
Expired
Learn about vigilant mode.
4ee1ca9

k6 v0.27.1 is a minor release with a few bugfixes and almost no functional changes compared to v0.27.0.

The biggest fix was resolving a panic (and some k6 login errors) when k6 was ran through git bash / Mintty on Windows (#1559).

k6 will now work in those terminals, however, if you're using git bash or Mintty as your terminal on Windows, you might not get the best user experience out of k6. Consider using a different terminal like Windows Terminal, PowerShell or Cmder. Alternatively, to work around the issues with the incompatible terminals, you can try running k6 through winpty, which should already be preinstalled in your git bash environment: winpty k6 run script.js.

If you're using the Windows Subsystem for Linux (WSL), you are probably going to get better experience by using the official Linux k6 binary or .deb package. For all other cases of running k6 on Windows, the normal k6 Windows binary / .msi package should work well.

Other minor fixes and changes:

  • The Go version that k6 is compiled with was updated to 1.14.6, to incorporate the latest Go fixes (#1563).
  • If the throw option is enabled, warnings for failed HTTP requests will no longer be logged to the console (#1199).
  • Metric sample packets sent to the cloud with k6 run --out cloud can now be sent in parallel via the new K6_CLOUD_METRIC_PUSH_CONCURRENCY option, with a default value of 1 (#1569).
  • The gracefulRampDown VU requirement calculations for the ramping-vus executor were greatly optimized for large test runs (#1567).
  • Fixed a rare bug where dropped_iterations wouldn't be emitted by the per-vu-iterations executor on time due to a race (#1357).
  • Metrics, including checks, from setup() and teardown(), were not correctly shown in local k6 runs (#949).
Assets 8
Loading