Skip to content

go 1.27.0, go@1.26 1.26.7 (new formula) - #288803

Merged
BrewTestBot merged 12 commits into
mainfrom
go1.27
Aug 21, 2026
Merged

go 1.27.0, go@1.26 1.26.7 (new formula)#288803
BrewTestBot merged 12 commits into
mainfrom
go1.27

Conversation

@stefanb

@stefanb stefanb commented Jun 19, 2026 •
edited
Loading

Copy link
Copy Markdown
Member

Announcements:

Release notes:

Go 1.27 milestone: GitHub milestone details (release blockers, commits, PRs)

Go release dashboard: https://dev.golang.org/release

Downloads: https://go.dev/dl/

This PR also adds go@1.26 (1.26.7) as a new formula, keeping the previous major available for formulae not yet compatible with Go 1.27.

Related/similar previous major releases:

Builds:

Note on rc3 coverage: macOS 14-x86_64 (deps) was cancelled after ~36 h (2026-08-14 00:05 → 2026-08-15 12:06) rather than finishing, stopping partway through the alphabet at tfmigrate and emitting no failed steps summary. So tfproviderlint, tgpt, trivy, vuls, wireguard-go, xeol and xgo were never exercised on macOS x86_64, and their platform notes below reflect arm64/Linux only. (pomerium was reached and correctly skipped — it is arch: :arm64 only.)

This PR's own formulae

The non-(deps) jobs fail on a single, transient step:

  • go@1.26 (1.26.6): brew audit --formula go@1.26 --online --new → Stable: The source URL https://fossies.org/linux/misc/go1.26.6.src.tar.gz is not reachable (HTTP status code 410) — Fossies had not mirrored 1.26.6 yet when the run started; the URL now returns HTTP 200, so this only needs a re-run.

errcheck, golangci-lint and govulncheck (revision bumps included here) pass on all platforms. solod needs its revision bump pushed to this branch as well (see below).

What would unblock the most formulae

Root causes ranked by how many failing formulae each one accounts for, after checking each project's current go.mod/upstream state:

Blocker Fix Formulae
golang.org/x/net < v0.55.0 (http2.TrailerPrefix) bump x/net to >= v0.55.0, or grpc >= 1.83.0 which requires it 9 — apptainer bigquery-emulator dagger gascity kapacitor localai opentofu steampipe vulcain
cockroachdb/swiss not enabled for Go 1.27 one-line build-tag enablement upstream, as was done for 1.26 5 — ethereum ipget kubo plakar pomerium
go-json-experiment/json not synced to Go 1.27 encoding/json/v2 upstream sync, then dependants bump 4 — dagu sing-box trivy vuls
golang.org/x/sys from 2019-2021 crashes on darwin/amd64 upstream x/sys bump 4 — leaf pget reg terraform-lsp
golang.org/x/tools too old to read Go 1.27 export data upstream x/tools bump 2 — go-critic tfproviderlint
CI runner disk exhaustion none (infrastructure) 3 — grafana grafana-alloy mesheryctl

Already fixed on upstream's master and only waiting for a release: apptainer, dagger, opentofu, vulcain, teleport.

Problematic formulae

Test failure - Needs revision bump

Build failure due to bug in Go 1.27

Build failure internal compiler error: bad live variable

Build failure undefined: http2.TrailerPrefix in google.golang.org/grpc module

Upstream:

The deciding dependency is golang.org/x/net, not grpc. Every formula below pins golang.org/x/net v0.54.0; v0.55.0 is the first release that keeps http2.TrailerPrefix defined under Go 1.27. grpc still references it at internal/transport/handler_server.go:271 in v1.83.0 too — bumping grpc only helps because of what its go.mod requires:

grpc required x/net builds on Go 1.27
v1.79.3 v0.48.0 no
v1.82.1 v0.53.0 no (confirmed by gascity)
v1.83.0 v0.55.0 yes

So, fixable by any of:

  • bumping golang.org/x/net to >= v0.55.0 (smallest change; grep 'golang.org/x/net' go.mod tells you instantly whether a formula is affected),
  • bumping google.golang.org/grpc to >= 1.83.0 (pulls x/net v0.55.0 in), or
  • adding go build -tags=http2legacy.

Formulae issues:

Formula reports different checksum

Gitea unstable checksum:

Others

Upstream tag moved

Build failure undefined: json.SkipFunc / undefined: json.DiscardUnknownMembers

Caused by github.com/go-json-experiment/json module being incompatible with Go 1.27's new stdlib encoding/json/v2. Upstream:

go-json-experiment/json mirrors the stdlib encoding/json/v2 API; its last sync commit is from 2026-06-23, before the Go 1.27 rename, and no upstream issue is filed for this yet — filing one there is probably the highest-leverage action, since it unblocks all four formulae at once.

Formulae:

Build failure undefined: checkMapABI in github.com/pingcap/tidb

Build failure undefined: hashFn / getRuntimeHasher / fastrand64 in cockroachdb/swiss

cockroachdb/swiss gates its runtime-internal hooks on an explicit per-release build-tag list, so each new Go major needs a one-line enablement: runtime_go1.20.go is currently //go:build (go1.20 && !go1.27) || untested_go_version.

None of the five formulae use swiss directly — each gets it as an indirect dependency of cockroachdb/pebble/v2, so this cannot be fixed in the formulae or in their own upstreams; it has to come from swiss or pebble.

  • Build with Go 1.27 fails cockroachdb/swiss#51 - The repo is low-activity — its newest commit is still b0f6560 from 2025-12-24, which was exactly this enablement for Go 1.26 (#50). The same one-line change for Go 1.27 would unblock all five formulae below.
  • pebble#5676 (open) asks whether the dependency is still needed at all, given Go 1.24+ implements the builtin map with Swiss tables. Per the pebble maintainer it is: pebble pairs swiss.Map with a custom cgo allocator so the GC does not have to scan the large block-cache maps, which the builtin map cannot express. So the realistic fix is the build-tag bump, not dropping the dependency.

Checked locally against go1.27rc3 (macOS arm64): swiss's own test suite passes with -tags untested_go_version — plain, under -race, and with swiss_invariants — and ipget 0.13.2 then builds and runs. So the breakage is the version gate itself rather than a real Go 1.27 incompatibility, which suggests the one-line bump is safe.

Formulae (all with cockroachdb/swiss@v0.0.0-20251224182025-b0f6560f979b):

Build failure link: invalid reference to runtime.nanotime1

Go 1.27 removed/renamed runtime.nanotime1. Needs upstream tailscale.com/tstime/mono update.

Formulae:

Build failure flag provided but not defined: -no-canonical-prefixes (rules_go + Go 1.27)

Runtime panic / crash

macOS x86_64 crash in old golang.org/x/sys ioctl (SIGBUS / SIGSEGV) — new in rc3

Binaries built with Go 1.27 that pull in a pre-2022 golang.org/x/sys crash immediately on macOS x86_64 when calling IoctlGetTermios (isatty/terminal detection). The faulting PC equals the signal address, i.e. the libc trampoline call from syscall.syscall/syscall.syscalln (runtime/sys_darwin.go:27) jumps somewhere non-executable. macOS arm64 and Linux are unaffected.

This is consistent with Go 1.27's change to the darwin libc trampoline calling convention (9b4244e9 runtime: return the error code as a return value in syscallN_trampoline), and it is the same shape as the earlier golang/go#71302 (runtime, x/sys/unix: Connectx is broken on darwin/amd64), which needed a matching x/sys fix and was backported. No Go 1.27 issue is filed for this yet — worth reporting upstream, since it silently breaks previously working binaries at runtime rather than at build time.

Per-formula the fix is an upstream golang.org/x/sys bump to anything recent (current is v0.47.0); the four pins below are 4-7 years old. The x86_64 log contains exactly 8 such crashes (4 formulae × 2 --retry attempts), so these are the full set within the range that job covered before it was cancelled.

panic: crypto: RegisterHash of unknown hash function

in https://go.dev/src/crypto/crypto.go#:~:text=crypto%3A%20RegisterHash%20of%20unknown%20hash%20function

panic: strcase.UnicodeVersion "15.0.0" != unicode.Version "17.0.0"

Needs rebuild with updated strcase module matching Go 1.27's Unicode 17.0.0 tables, pending

Formulae:

panic: jsontext: invalid nil io.Reader

encoding/json.NewDecoder(nil) now panics. In Go <= 1.26 a nil io.Reader was accepted and only failed on first read; in Go 1.27 encoding/json is backed by jsontext, which panics in Reset. Any formula calling json.NewDecoder with a nil reader will hit this, so it is worth watching for beyond grpcurl.

  • grpcurl (1.9.3) test failure: panic: jsontext: invalid nil io.Reader — all macOS: grpcurl: pin go@1.26 #300105 
    encoding/json/jsontext.(*Decoder).Reset  encoding/json/jsontext/decode.go:137
encoding/json.NewDecoder({0x0?, 0x0?})   encoding/json/v2_stream.go:48
grpcurl.NewJSONRequestParserWithUnmarshaler  format.go:62
grpcurl.RequestParserAndFormatter            format.go:412
    grpcurl passes a nil reader when the command needs no request body (describe). v1.9.3 (2025-03-11) is still the newest release and upstream already has an open request for a new release; the fix is upstream skipping the decoder for nil input. Worth reporting to golang/go as well, as it is a silent runtime behaviour change

Go 1.27 internal error — package "X" without types was imported

Go 1.27 runtime analysis failure

  • go-size-analyzer (1.13.1) test failure: the length of module data section is to big: address 0x50f940, base 0x50f940, length 0xffffffffffaf6960 — Linux x86_64/arm64 only. Go 1.27 changed the module data layout the tool parses; no upstream issue filed for 1.27 yet (Zxilly/go-size-analyzer) feat: support Go 1.27 Zxilly/go-size-analyzer#594 go-size-analyzer 1.14.0 #300048
  • xgo (1.7.5) test failure: panic: runtime error: invalid memory address or nil pointer dereference — all macOS arm64 + Linux x86_64/arm64. Crash is in the gogen dependency, reached from dependency checking: 
    github.com/goplus/gogen@v1.23.5/package.go:486 (*Package).ForEachFile
github.com/goplus/xgo/tool.checkGopDeps  tool/load.go:338
github.com/goplus/xgo/tool.afterLoad     tool/load.go:322
    No upstream issue filed for Go 1.27 — worth reporting at goplus/xgo with this stack
    test for Go1.27 goplus/xgo#2851 needs release >v1.7.5

Various other build failures

  • argo build failure: panic in k8s.io/code-generator deepcopy-gen — passes in rc3
  • checkmake (0.3.2) build failure: golangci-lint goconst issues (string 'list-rules' has 3 occurrences, make it a constant, …) → make: *** [golangci-lint] Error 1 — all macOS. Not a Go 1.27 problem: upstream's newest release is v0.3.2 (2026-01-10) and its make target runs an unpinned golangci-lint, so newer linter defaults fail the build. Homebrew-side options are dropping the lint step from the build or getting upstream to pin the linter
  • ffmate (2.0.18) build failure: ERR_PNPM_IGNORED_BUILDS — passes in rc3
  • kubetail (0.18.0) build failure: [ERROR] Cannot verify the identity of the @pnpm/exe.darwin-x64 native binary: it is missing from pnpm-lock.yaml → make: *** [build-dashboard-ui] Error 1 — macOS 14 x86_64 only; unrelated to Go 1.27. Upstream switched to a pinned pnpm + frozen lockfile in #1169, and cli/v0.18.0 is the newest release, so the shipped pnpm-lock.yaml simply has no darwin-x64 entry — needs an upstream lockfile regenerated on/for x86_64 macOS
  • parca build failure: ERR_PNPM_LOCKFILE_CONFIG_MISMATCH — passes in rc3
  • syncthing (2.1.3) build failure: runtime go1.27rc3 not found in compat.yaml — all macOS. Trivial upstream fix: compat.yaml lists runtimes only up to go1.26 (whose entry is just # no changes from 1.25), so a - runtime: go1.27 block mirroring it is all that is needed
  • terracognita build failure: no space left on device — passes in rc3

CI runner out of disk (no space left on device)

Not Go 1.27 related; the runner's disk fills up after the large envoy/grafana builds on the same machine.

  • grafana (13.1.3) build failure: ENOSPC: no space left on device during webpack → Command failed: yarn nx run grafana:"build" — macOS 14 arm64 only grafana 13.2.0 #299419
  • grafana-alloy (1.18.1) build failure: compile: writing output: … no space left on device — macOS 26 arm64 only
  • mesheryctl (1.0.66) build failure: no space left on device — macOS 15/26 arm64 only. OK in mesheryctl 1.0.67 #300322

Test failure

Test failure — assertion mismatch (needs test fix)

GitHub API rate limit (CI environment issue)

External resource unavailable (CI environment issue)

  • amass (5.1.1) test failure: Failed to create a session with the Amass engine: createSession: status=500 Internal Server Error — all macOS
  • curlie (1.8.2) test failure: 503 Service Temporarily Unavailable from httpbin.org — macOS 14 x86_64 (new in rc3)
  • netdata: passes in rc3
  • restish (2.3.0) test failure: 503 Service Temporarily Unavailable from httpbin.org — macOS 14 x86_64 only; passed on all arm64 runners, and it is the same httpbin.org outage that hit curlie in the same job
  • squealer: passes in rc3
  • tgpt (2.13.0) test failure: Some error has occurred. Statuscode: 429 / FreeUsageLimitError — macOS 26 arm64 (new in rc3) {"type":"error","error":{"type":"ModelError","message":"Free promotion has ended for DeepSeek V4 Flash Free. You can continue using the model by subscribing to OpenCode Go - https://opencode.ai/go"}}
  • wormhole-william: passes in rc3
  • xeol (0.10.8) test failure: the eol database was built 1 year ago (max allowed age is 12 weeks) — macOS 14/15 arm64. The hosted EOL database itself has stopped being refreshed upstream, so no Go/formula change can make this pass; only a test change or an upstream DB refresh will

Failed to download resource (404/403)

  • Have you followed the guidelines for contributing?
  • Have you ensured that your commits follow the commit style guide?
  • Have you checked that there aren't other open pull requests for the same formula update/change?
  • Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>?
  • Is your test running fine brew test <formula>?
  • Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?
  • AI was used to generate or assist with generating this PR. Please specify below how you used AI to help you, and what steps you have taken to manually verify the changes.

AI (Claude Opus 5 via Claude Code) was used only to triage the CI logs of run 31753313820 and to maintain the failure list above: it downloaded the six (deps) job logs, extracted each failing step and its error, grouped them by root cause, and then checked each affected project's upstream go.mod, releases and issue tracker to record what is already fixed and what is still blocked. The formula changes in this PR were written and verified by me. Build/test results quoted above come from Homebrew's CI, except the cockroachdb/swiss / ipget check against go1.27rc3, which the AI ran locally on my machine at my request.

@stefanb stefanb added in progress Stale bot should stay away prerelease-testing Pull request from upstream, testing a pre-release with homebrew dependencies CI-skip-recursive-dependents Pass --skip-recursive-dependents to brew test-bot. CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. CI-build-dependents-from-source Pass --build-dependents-from-source to brew test-bot. CI-no-fail-fast-deps Continue dependent tests despite failing GitHub Actions matrix tests. long dependent tests Set a long timeout for dependent testing labels Jun 19, 2026
@github-actions github-actions Bot added automerge-skip `brew pr-automerge` will skip this pull request new formula PR adds a new formula to Homebrew/homebrew-core alias labels Jun 19, 2026
This was referenced Jun 20, 2026
Closed
Merged
Closed
Closed
Merged
Merged
Closed
Merged
Open
Merged
Closed
Closed
Merged
This was referenced Jun 28, 2026
Closed
Merged
Open
Merged
Merged
pull Bot pushed a commit to t8y2/homebrew-core that referenced this pull request Jun 29, 2026
@stefanb
gitea-runner: use git instead of archive
7da3ae5 
Ref:
* https://gitea.com/gitea/runner/releases/tag/v1.0.8
* Homebrew#288967
* Homebrew#288803

Closes Homebrew#288967
@github-actions github-actions Bot added the CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. label Aug 21, 2026
@github-actions

github-actions Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

⚠️ @stefanb Failed to enable automerge.

@BrewTestBot
BrewTestBot added this pull request to the merge queue Aug 21, 2026
Merged via the queue into main with commit d720de1 Aug 21, 2026
22 checks passed
@BrewTestBot
BrewTestBot deleted the go1.27 branch August 21, 2026 05:16
This was referenced Aug 21, 2026
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
Merged
@chenrui333 chenrui333 mentioned this pull request Aug 23, 2026
Merged
7 tasks
This was referenced Aug 23, 2026
Merged
Merged
Merged
This was referenced Sep 2, 2026
Merged
Merged
Merged
Merged
@cho-m cho-m mentioned this pull request Sep 8, 2026
Merged
7 of 8 tasks
@stefanb stefanb mentioned this pull request Sep 12, 2026
Merged
4 of 7 tasks
social4hyq pushed a commit to social4hyq/homebrew-core that referenced this pull request Sep 20, 2026
HarmonybrewBot HarmonybrewBot
!14844 merge bump-dolt-2.2.2 into main
8753c1b 
dolt 2.2.2

Created-by: HarmonybrewBot
Commit-by: HarmonybrewBot
Merged-by: HarmonybrewBot
Description: Created by `brew bump`

---

Created with `brew bump-formula-pr`.<details>
  <summary>release notes</summary>
  <pre># Merged PRs

## dolt

* [11332](dolthub/dolt#11332): /go/cmd/dolt/cli: only emit backspace characters in a tty
  The CLI's progress spinners (dolt push, pull, fetch, assist, and import/sql progress output) redraw themselves in place by writing backspace  control characters. This was done unconditionally, with no check for whether output was going to a terminal.
  When stdout/stderr is captured to a file or pipe — a script, a CI job, dolt push > push.log 2>&1 — those backspaces become literal bytes in the log instead of cursor movements. Rendering the log then "erases" the surrounding text. The worst case: an error is printed while the spinner is active, and the spinner's trailing backspaces overwrite the error text, so the captured log looks empty exactly when something went wrong.
  This PR fixes this so that TTY is detected and redraw is gated on it.
* [11327](dolthub/dolt#11327): Add support for functional indexes with multiple expressions
  Picks up support for functional indexes with multiple expressions from GMS (dolthub/go-mysql-server#3634) and adds additional tests for Dolt.
  Depends on: dolthub/go-mysql-server#3634
* [11326](dolthub/dolt#11326): unsafe adaptive value
* [11325](dolthub/dolt#11325): gitblobstore: fix premature flush and prune of pending write that was not referenced in current manifest
  CheckAndPut("manifest") flushed all queued pendingWrites into the commit, regardless of whether the manifest being written referenced them. That commits a table file into the git tree as an unreferenced entry, which a later manifest flush then legitimately prunes and evicts from the in-memory cache — while the file is still live (about to be added, or being re-read by addTableFiles' refCheckAllSources retry loop). The result is Blob not found. Stale pendingWrites from earlier failed pushes in the same process keep the condition sticky, which is why a restart clears it.
  This PR only flushes the pending writes the manifest actually references. Unreferenced writes stay pending until a manifest that references them is written, so they're committed and referenced atomically. After this change a live table file is always either pending and cached (not in the tree, so unprunable) or committed and referenced (never pruned) — an unreferenced tree entry can no longer coexist with being live.
* [11320](dolthub/dolt#11320): go: sql_server_driver: Fix a race on *SqlServer.Cmd access. Start the command before we spawn its wait goroutine.
* [11316](dolthub/dolt#11316): go: sqle/cluster: Improve dolt_cluster_ack_writes_timeout_secs circuit breaker behavior.
  Previously, the circuit breaker only had an open and a closed state. It would only go from open to closed when the replication thread fully quiesced. This PR adds a half-open state, where it lets a single commit probe for replication success within the configured timeout. If that wait succeeds, the circuit breaker closes.
  This lets high write throughput use cases reenable their configured replication waits even when writes arrive more requently than their typical replication delay.
* [11314](dolthub/dolt#11314): go: sqle/cluster: controller.go: Make DROP DATABASE replication participate in dolt_cluster_ack_writes_timeout_secs.
* [11313](dolthub/dolt#11313): go: Fix some data races surfaced by running go-sql-server-driver tests under -race.
* [11312](dolthub/dolt#11312): go/store/nbs: Fix a race between the journal persister and PruneTableFiles.
  When PruneTableFiles runs, it is willing to delete the journal file if there is no longer a reference to it in the manifest. This can race with bootstrapJournal making a new journal file. The journal file can be on disk, and seen by PruneTableFiles and thus selected for removal, before the journal has been added to the chunk store proper.
  This change makes the journal writer participate in the retained files machinery, same as the table file persister, so that the journal is correctly considered not-safe-for-delete-by-PruneTableFiles before it is ever created on disk and potentially selected for deletion by PruneTableFiles.
* [11305](dolthub/dolt#11305): fix stats functions to include schema
  We lookup stats with empty string for schema. Since this is not always the case, we sometimes miss stats.
* [11290](dolthub/dolt#11290): Bump golang.org/x/net v0.54.0 => v0.55.0 for Go 1.27 compatibility
  Go 1.27 change:
  * golang/go#60746
  * golang/go#67810
  Problem found in
  * Homebrew/homebrew-core#288803
  Build error:
  ```
  $ go1.27rc1 build -v ./cmd/dolt
  google.golang.org/grpc/internal/transport
  # google.golang.org/grpc/internal/transport
  ../../../../go/pkg/mod/google.golang.org/grpc@v1.79.3/internal/transport/handler_server.go:271:18: undefined: http2.TrailerPrefix
  ```
  `golang.org/x/net` upgrade
  ```
  $ go get golang.org/x/net@v0.55.0 && go mod tidy
  go: upgraded golang.org/x/net v0.54.0 => v0.55.0
  ```
  Build successful:
  ```
  $ go1.27rc1 build -v ./cmd/dolt
  ```

## go-mysql-server

* [3634](dolthub/go-mysql-server#3634): Add support for multiple expressions in functional indexes
* [3627](dolthub/go-mysql-server#3627): fix stats functions to include schema
  We include the schema in the stats key, but only sometimes fill in the field.
* [3626](dolthub/go-mysql-server#3626): Prevent index offset when comparing rows in `topRowsIter`
  Fixes dolthub/dolt#11300
  Appending the row order number to the end of a `sql.Row` during a Top-N Heap Sort in `topRowsIter` was causing an index offset when evaluating SortFields that were subqueries, thus resulting in incorrect result.
  This PR
  - modifies `topRowsHeap` to instead take a `rowWithOrder` struct that separates out the `sql.Row` from the order number while still taking the order number into account when sorting the heap.
  - refactoring `Sorter.LesserRow` logic  into a new `CompareRows` function to allow checking for row equality
  - moves top row(s) iterators to its own file as part of an effort to make our iterators more organized (#3620). This file also includes `topRowsHeap` since it is only ever used by `topRowIter` (see dolthub/go-mysql-server#3622 (comment) for next steps)
  - removes `ValueRowSorter`since it's actually never used anywhere and doesn't even fully implement `sort.Interface`
* [3617](dolthub/go-mysql-server#3617): special case on extended type for getting compare type


# Closed Issues

* [11265](dolthub/dolt#11265): Dolt INSERT … SELECT with CTE + JSON_TABLE disconnects
* [3622](dolthub/go-mysql-server#3622): Clean up: move sorters in `sql/expression/sort.go` out of `expression` package

# Performance

|       Read Tests        | MySQL  |  Dolt  | Multiple |
|:-----------------------:|:------:|:------:|:--------:|
|  covering\_index\_scan  | 17.32  |  2.3   |   0.13   |
|      groupby\_scan      | 134.9  | 142.39 |   1.06   |
|       index\_join       |  3.43  |  1.89  |   0.55   |
|    index\_join\_scan    |  4.18  |  1.32  |   0.32   |
|       index\_scan       | 350.33 | 215.44 |   0.61   |
|   oltp\_point\_select   |  0.19  |  0.25  |   1.32   |
|    oltp\_read\_only     |  3.62  |  4.91  |   1.36   |
| select\_random\_points  |  0.35  |  0.51  |   1.46   |
| select\_random\_ranges  |  0.39  |  0.64  |   1.64   |
|       table\_scan       | 350.33 | 200.47 |   0.57   |
|   types\_table\_scan    | 746.32 | 467.3  |   0.63   |
| reads\_mean\_multiplier |        |        |   0.88   |

|       Write Tests        | MySQL | Dolt  | Multiple |
|:------------------------:|:-----:|:-----:|:--------:|
|   oltp\_delete\_insert   |  7.7  | 6.21  |   0.81   |
|       oltp\_insert       | 4.03  | 3.13  |   0.78   |
|    oltp\_read\_write     | 8.74  | 11.24 |   1.29   |
|   oltp\_update\_index    | 4.33  |  3.3  |   0.76   |
| oltp\_update\_non\_index |  4.1  | 3.02  |   0.74   |
|    oltp\_write\_only     | 5.18  | 6.21  |   1.2    |
|  types\_delete\_insert   | 8.28  | 6.67  |   0.81   |
| writes\_mean\_multiplier |       |       |   0.91   |

|    TPC-C TPS Tests    | MySQL | Dolt  | Multiple |
|:---------------------:|:-----:|:-----:|:--------:|
|  tpcc-scale-factor-1  | 95.13 | 51.54 |   1.85   |
| tpcc\_tps\_multiplier |       |       |   1.85   |

| Overall Mean Multiple | 1.21 |
|:---------------------:|:----:|</pre>
  <p>View the full release notes at <a href="https://github.com/dolthub/dolt/releases/tag/v2.2.2">https://github.com/dolthub/dolt/releases/tag/v2.2.2</a>.</p>
</details>
<hr>

See merge request: Harmonybrew/homebrew-core!14844
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@carlocab carlocab carlocab approved these changes
@github-actions github-actions[bot] github-actions[bot] approved these changes

Assignees

No one assigned

Labels

alias CI-build-dependents-from-source Pass --build-dependents-from-source to brew test-bot. CI-no-fail-fast Continue CI tests despite failing GitHub Actions matrix builds. CI-no-fail-fast-deps Continue dependent tests despite failing GitHub Actions matrix tests. CI-published-bottle-commits The commits for the built bottles have been pushed to the PR branch. CI-skip-recursive-dependents Pass --skip-recursive-dependents to brew test-bot. long dependent tests Set a long timeout for dependent testing new formula PR adds a new formula to Homebrew/homebrew-core no long build conflict Do not allow merging other pull requests when files conflict with this one

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

5 participants

@stefanb @wayneashleyberry @sanbei101 @carlocab @BrewTestBot