Skip to content
Go

L4 module for Postgres: matchers #173

Sign in to view logs

L4 module for Postgres: matchers

L4 module for Postgres: matchers #173

Triggered via pull request June 2, 2024 16:50
@metafeathermetafeather
synchronize #188
metafeather:05-03-l4-module-for-postgres-matchers
Status Failure
Total duration 5m 50s
Artifacts –

go.yml

on: pull_request
Matrix: build-test-check
Fit to window
Zoom out
Zoom in

Annotations

12 errors and 6 warnings
build-test-check (ubuntu-latest, 1.21): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (ubuntu-latest, 1.21)
Process completed with exit code 1.
build-test-check (ubuntu-latest, 1.22): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (ubuntu-latest, 1.22)
Process completed with exit code 1.
build-test-check (macos-latest, 1.22): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (macos-latest, 1.22)
Process completed with exit code 1.
build-test-check (macos-latest, 1.21): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (macos-latest, 1.21)
Process completed with exit code 1.
build-test-check (windows-latest, 1.21): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (windows-latest, 1.21)
Process completed with exit code 1.
build-test-check (windows-latest, 1.22): modules/l4postgres/matcher_test.go#L50
cannot use &bytes.Buffer{} (value of type *bytes.Buffer) as []byte value in argument to layer4.WrapConnection
build-test-check (windows-latest, 1.22)
Process completed with exit code 1.
build-test-check (ubuntu-latest, 1.21)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-check (ubuntu-latest, 1.22)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-check (macos-latest, 1.22)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-check (macos-latest, 1.21)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-check (windows-latest, 1.21)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.
build-test-check (windows-latest, 1.22)
Node.js 16 actions are deprecated. Please update the following actions to use Node.js 20: engineerd/[email protected]. For more information see: https://github.blog/changelog/2023-09-22-github-actions-transitioning-from-node-16-to-node-20/.