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: typeorm failed #113662

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

roachtest: typeorm failed #113662

cockroach-teamcity opened this issue Nov 2, 2023 · 1 comment · Fixed by #113676
Labels
branch-release-22.2 Used to mark GA and release blockers, technical advisories, and bugs for 22.2 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.typeorm failed with artifacts on release-22.2 @ 135acce473babb0109e796343581823b69146ebe:

test artifacts and logs in: /artifacts/typeorm/run_1
(typeorm.go:103).func1: all attempts failed for add nodesource key and deb repository: output in run_124055.610784381_n1_sudo-aptget-update-s: 
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 returned: COMMAND_PROBLEM: ssh verbose log retained in ssh_124055.621684055_n1_sudo-aptget-update-s.log: exit status 2

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)

Same failure on other branches

/cc @cockroachdb/sql-foundations

This test on roachdash | Improve this report!

Jira issue: CRDB-33097

@cockroach-teamcity cockroach-teamcity added branch-release-22.2 Used to mark GA and release blockers, technical advisories, and bugs for 22.2 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 22.2 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.typeorm failed with artifacts on release-22.2 @ 135acce473babb0109e796343581823b69146ebe:

test artifacts and logs in: /artifacts/typeorm/run_1
(typeorm.go:103).func1: all attempts failed for add nodesource key and deb repository: output in run_123340.636073022_n1_sudo-aptget-update-s: 
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 returned: COMMAND_PROBLEM: ssh verbose log retained in ssh_123340.646379727_n1_sudo-aptget-update-s.log: exit status 2

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)

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-release-22.2 Used to mark GA and release blockers, technical advisories, and bugs for 22.2 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