Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

roachtest: node-postgres failed #113673

Closed
cockroach-teamcity opened this issue Nov 2, 2023 · 1 comment · Fixed by #113676
Closed

roachtest: node-postgres failed #113673

cockroach-teamcity opened this issue Nov 2, 2023 · 1 comment · Fixed by #113676
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Milestone

Comments

@cockroach-teamcity
Copy link
Member

cockroach-teamcity commented Nov 2, 2023

roachtest.node-postgres failed with artifacts on master @ cedd409f2115655efe2c529f6052f3056673b277:

	            	  | [...repeated from below...]
	            	Wraps: (2) all attempts failed for add nodesource key and deb repository
	            	Wraps: (3) attached stack trace
	            	  -- stack trace:
	            	  | main.(*clusterImpl).RunE
	            	  | 	main/pkg/cmd/roachtest/cluster.go:2218
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.repeatRunE
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:115
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNodeJSPostgres.func1
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/nodejs_postgres.go:70
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNodeJSPostgres.func2
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/nodejs_postgres.go:183
	            	  | main.(*testRunner).runTest.func2
	            	  | 	main/pkg/cmd/roachtest/test_runner.go:1090
	            	  | runtime.goexit
	            	  | 	src/runtime/asm_amd64.s:1650
	            	Wraps: (4) full command output in run_145251.057522362_n1_sudo-aptget-update-s.log
	            	Wraps: (5) Node 1. Command with error:
	            	  | ``````
	            	  | sudo apt-get update && \
	            	  | sudo apt-get install -y ca-certificates curl gnupg && \
	            	  | sudo mkdir -p /etc/apt/keyrings && \
	            	  | curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg && \
	            	  | echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
	            	  | ``````
	            	  | stdout:Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy InRelease
	            	  | Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy-updates InRelease
	            	  | Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy-backports InRelease
	            	  | Hit:4 http://security.ubuntu.com/ubuntu jammy-security InRelease
	            	  | Hit:5 https://deb.nodesource.com/node_18.x nodistro InRelease
	            	  | Reading package lists...
	            	  | Reading package lists...
	            	  | Building dependency tree...
	            	  | Reading state information...
	            	  | ca-certificates is already the newest version (20230311ubuntu0.22.04.1).
	            	  | curl is already the newest version (7.81.0-1ubuntu1.14).
	            	  | gnupg is already the newest version (2.2.27-3ubuntu2.1).
	            	  | The following package was automatically installed and is no longer required:
	            	  |   libnuma1
	            	  | Use 'sudo apt autoremove' to remove it.
	            	  | 0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
	            	  |
	            	  | stderr:gpg: cannot open '/dev/tty': No such device or address
	            	  | curl: (23) Failed writing body
	            	Wraps: (6) COMMAND_PROBLEM
	            	Wraps: (7) exit status 2
	            	Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *hintdetail.withDetail (6) errors.Cmd (7) *exec.ExitError
	Test:       	node-postgres
(require.go:1360).NoError: FailNow called
test artifacts and logs in: /artifacts/node-postgres/run_1

Parameters: ROACHTEST_arch=amd64 , ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-33103

@cockroach-teamcity cockroach-teamcity added branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions) labels Nov 2, 2023
@cockroach-teamcity cockroach-teamcity added this to the 24.1 milestone Nov 2, 2023
@rafiss rafiss removed the release-blocker Indicates a release-blocker. Use with branch-release-2x.x label to denote which branch is blocked. label Nov 2, 2023
@cockroach-teamcity
Copy link
Member Author

roachtest.node-postgres failed with artifacts on master @ 694861a16c8d72a52ac059ef82cf2763ca4406b0:

	            	  | [...repeated from below...]
	            	Wraps: (2) all attempts failed for add nodesource key and deb repository
	            	Wraps: (3) attached stack trace
	            	  -- stack trace:
	            	  | main.(*clusterImpl).RunE
	            	  | 	main/pkg/cmd/roachtest/cluster.go:2262
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.repeatRunE
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/canary.go:115
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNodeJSPostgres.func1
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/nodejs_postgres.go:70
	            	  | github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests.registerNodeJSPostgres.func2
	            	  | 	github.com/cockroachdb/cockroach/pkg/cmd/roachtest/tests/nodejs_postgres.go:183
	            	  | main.(*testRunner).runTest.func2
	            	  | 	main/pkg/cmd/roachtest/test_runner.go:1090
	            	  | runtime.goexit
	            	  | 	src/runtime/asm_amd64.s:1650
	            	Wraps: (4) full command output in run_154314.785923553_n1_sudo-aptget-update-s.log
	            	Wraps: (5) Node 1. Command with error:
	            	  | ``````
	            	  | sudo apt-get update && \
	            	  | sudo apt-get install -y ca-certificates curl gnupg && \
	            	  | sudo mkdir -p /etc/apt/keyrings && \
	            	  | curl -fsSL https://deb.nodesource.com/gpgkey/nodesource-repo.gpg.key | sudo gpg --dearmor -o /etc/apt/keyrings/nodesource.gpg && \
	            	  | echo "deb [signed-by=/etc/apt/keyrings/nodesource.gpg] https://deb.nodesource.com/node_18.x nodistro main" | sudo tee /etc/apt/sources.list.d/nodesource.list
	            	  | ``````
	            	  | stdout:Hit:1 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy InRelease
	            	  | Hit:2 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy-updates InRelease
	            	  | Hit:3 http://us-east1.gce.archive.ubuntu.com/ubuntu jammy-backports InRelease
	            	  | Hit:4 https://deb.nodesource.com/node_18.x nodistro InRelease
	            	  | Hit:5 http://security.ubuntu.com/ubuntu jammy-security InRelease
	            	  | Reading package lists...
	            	  | Reading package lists...
	            	  | Building dependency tree...
	            	  | Reading state information...
	            	  | ca-certificates is already the newest version (20230311ubuntu0.22.04.1).
	            	  | curl is already the newest version (7.81.0-1ubuntu1.14).
	            	  | gnupg is already the newest version (2.2.27-3ubuntu2.1).
	            	  | The following package was automatically installed and is no longer required:
	            	  |   libnuma1
	            	  | Use 'sudo apt autoremove' to remove it.
	            	  | 0 upgraded, 0 newly installed, 0 to remove and 78 not upgraded.
	            	  |
	            	  | stderr:gpg: cannot open '/dev/tty': No such device or address
	            	  | curl: (23) Failed writing body
	            	Wraps: (6) COMMAND_PROBLEM
	            	Wraps: (7) exit status 2
	            	Error types: (1) *withstack.withStack (2) *errutil.withPrefix (3) *withstack.withStack (4) *errutil.withPrefix (5) *hintdetail.withDetail (6) errors.Cmd (7) *exec.ExitError
	Test:       	node-postgres
(require.go:1360).NoError: FailNow called
test artifacts and logs in: /artifacts/node-postgres/run_1

Parameters: ROACHTEST_arch=amd64 , ROACHTEST_cloud=gce , ROACHTEST_cpu=4 , ROACHTEST_encrypted=false , ROACHTEST_metamorphicBuild=false , ROACHTEST_ssd=0

Help

See: roachtest README

See: How To Investigate (internal)

See: Grafana

Same failure on other branches

This test on roachdash | Improve this report!

craig bot pushed a commit that referenced this issue Nov 3, 2023
113643: roachtest: move validate-after-version-upgrade to new framework r=rafiss a=rafiss

The new framework provides a few more testing enhancements and is the only one that will be maintained.

fixes #110535
Release note: None

113676: roachtest: fix js install command (gpg) r=rafiss a=annrpom

We are seeing a `gpg: cannot open '/dev/tty': No such device or address` error from the new installation method we followed. Resolution seems to be nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: #113673
Fixes: #113662
Fixes: #113659
Fixes: #113675
Fixes: #113677
Fixes: #113762

Release note: None

113698: metamorphic: add MVCC{CheckFor,}AcquireLock operations r=nvanbenschoten a=itsbilal

This change adds two new operations to the MVCC metamorphic testing package that were added in #110323. We check for determinism in the storage package by adding these operations to the metamorphic tests as well.

Fixes #109650.

Epic: none

Release note: None

Co-authored-by: Rafi Shamim <[email protected]>
Co-authored-by: Annie Pompa <[email protected]>
Co-authored-by: Bilal Akhtar <[email protected]>
@craig craig bot closed this as completed in e3bac44 Nov 3, 2023
blathers-crl bot pushed a commit that referenced this issue Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address`
error from the new installation method we followed. Resolution seems to be
nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: #113673
Fixes: #113662
Fixes: #113659

Release note: None
blathers-crl bot pushed a commit that referenced this issue Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address`
error from the new installation method we followed. Resolution seems to be
nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: #113673
Fixes: #113662
Fixes: #113659

Release note: None
blathers-crl bot pushed a commit that referenced this issue Nov 3, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address`
error from the new installation method we followed. Resolution seems to be
nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: #113673
Fixes: #113662
Fixes: #113659

Release note: None
blathers-crl bot pushed a commit that referenced this issue Nov 7, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address`
error from the new installation method we followed. Resolution seems to be
nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: #113673
Fixes: #113662
Fixes: #113659

Release note: None
rafiss pushed a commit to rafiss/cockroach that referenced this issue Nov 7, 2023
We are seeing a `gpg: cannot open '/dev/tty': No such device or address`
error from the new installation method we followed. Resolution seems to be
nodejs/docker-node#922.

In case we are running into an issue with machines being reused, we
first check to see if we can install nodejs and npm before we add
a nodesource key and deb repository (to prevent gpg: dearmoring failed:
File exists) issues.

(Copied from a reply to the bug report in the issue linked above)
> For any script use you should anyway use --batch which disables the use
of the tty as a side-effect.

Fixes: cockroachdb#113673
Fixes: cockroachdb#113662
Fixes: cockroachdb#113659

Release note: None
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch-master Failures and bugs on the master branch. C-test-failure Broken test (automatically or manually discovered). O-roachtest O-robot Originated from a bot. T-sql-foundations SQL Foundations Team (formerly SQL Schema + SQL Sessions)
Projects
No open projects
Archived in project
Development

Successfully merging a pull request may close this issue.

2 participants