Skip to content

Conversation

@krvikash
Copy link
Contributor

@krvikash krvikash commented Dec 24, 2025

Description

Running SingleStoreQueryRunner locally on Mac (Silicon) hangs the startup and eventually fails because we were using singlestoredb-dev:0.2.51 (which is compatible with SingleStore version 8.9) with SingleStore version 7.8. Updating the compatible version fixes the startup.

This PR also reverts #12235 newer version of SingleStore(MemSql) fails to insert invalid date.

Reference:

Release notes

(X) This is not user-visible or is docs only, and no release notes are required.

@cla-bot cla-bot bot added the cla-signed label Dec 24, 2025
@github-actions github-actions bot added the singlestore SingleStore connector label Dec 24, 2025
@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch from 985dcdf to b53a1f1 Compare December 24, 2025 07:59
@github-actions github-actions bot added the docs label Dec 24, 2025
@krvikash krvikash marked this pull request as draft December 24, 2025 09:24
@krvikash
Copy link
Contributor Author

(The latest image is still failing locally on Mac. moving to draft for now.)

@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch 3 times, most recently from 21df709 to afcddf2 Compare December 25, 2025 13:30
@krvikash
Copy link
Contributor Author

(image above 0.2.62 only supports x86-64 architecture. So using
0.2.62 image for latest version.)

@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch 2 times, most recently from 2c1e205 to be7634d Compare December 25, 2025 19:48
@krvikash krvikash marked this pull request as ready for review December 25, 2025 19:52
@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch from be7634d to efeb400 Compare December 25, 2025 20:02
@krvikash
Copy link
Contributor Author

(ready for review)

@ebyhr
Copy link
Member

ebyhr commented Dec 26, 2025

Could you confirm CI failure?

java.sql.SQLException: (conn=325) Not enough disk space to create or attach database some_schema on leaf 127.0.0.1:3307. Estimate Available 9624 MB, Estimate Needed 13872 MB.

https://github.com/trinodb/trino/actions/runs/20510230185/job/58930448578?pr=27754

@krvikash
Copy link
Contributor Author

Could you confirm CI failure?

java.sql.SQLException: (conn=325) Not enough disk space to create or attach database some_schema on leaf 127.0.0.1:3307. Estimate Available 9624 MB, Estimate Needed 13872 MB.

https://github.com/trinodb/trino/actions/runs/20510230185/job/58930448578?pr=27754

Locally, it's not failing. The issue is similar to prestodb/presto#21900. It suggests to clean-up the disk space. But we are doing this already:

echo "Removing toolchains"
sudo rm -rf \
/usr/local/graalvm \
/usr/local/lib/android/ \
/usr/share/dotnet/ \
/opt/ghc/ \
/usr/local/share/boost/ \
"${AGENT_TOOLSDIRECTORY}"

@krvikash
Copy link
Contributor Author

image

@krvikash
Copy link
Contributor Author

(trying out with explicit cleanup)

@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch 4 times, most recently from cfe61ac to bb86bf8 Compare December 26, 2025 07:32
image above `0.2.62` only supports x86-64 architecture. So using
`0.2.62` image for latest version.
@krvikash krvikash force-pushed the krvikash/singlestore-server-upgrade branch from bb86bf8 to 787ca9e Compare December 26, 2025 07:35
@krvikash
Copy link
Contributor Author

krvikash commented Dec 26, 2025

java.sql.SQLException: (conn=325) Not enough disk space to create or attach database some_schema on leaf 127.0.0.1:3307. Estimate Available 9624 MB, Estimate Needed 13872 MB.

Reducing the resource usage resolves the issue. (https://www.singlestore.com/forum/t/available-disk-space-error/3802/9)

@krvikash krvikash requested review from ebyhr and findinpath December 29, 2025 05:42
}

@Test
@Override
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Could you please leave a code comment explaining why this test is overridden?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Development

Successfully merging this pull request may close these issues.

3 participants