Skip to content

tests: fix port overlap in ytsaurus tests#88134

Closed
azat wants to merge 1 commit intoClickHouse:masterfrom
azat:tests/ytsaurus
Closed

tests: fix port overlap in ytsaurus tests#88134
azat wants to merge 1 commit intoClickHouse:masterfrom
azat:tests/ytsaurus

Conversation

@azat
Copy link
Member

@azat azat commented Oct 6, 2025

@azat azat added the 🍃 green ci 🌿 Fixing flaky tests in CI label Oct 6, 2025
@clickhouse-gh
Copy link
Contributor

clickhouse-gh bot commented Oct 6, 2025

Workflow [PR], commit [8487b78]

@clickhouse-gh clickhouse-gh bot added the pr-not-for-changelog This PR should not be mentioned in the changelog label Oct 6, 2025
@MikhailBurdukov
Copy link
Contributor

@azat
Most likely this will not be sufficient, there are hardcoded port values in the tests:

yt = YTsaurusCLI(started_cluster, instance, "ytsaurus_backend1", 80)

If you don't mind, I can do a pr with fix

@antaljanosbenjamin antaljanosbenjamin self-assigned this Oct 6, 2025
@azat
Copy link
Member Author

azat commented Oct 6, 2025

@MikhailBurdukov you are welcome! (ping me there).

@azat azat closed this Oct 6, 2025
@azat
Copy link
Member Author

azat commented Oct 6, 2025

BTW please also take a look into this -

YT_HOST = "ytsaurus_backend1"
YT_PORT = 80
YT_URI = f"http://{YT_HOST}:{YT_PORT}"
YT_DEFAULT_TOKEN = "password"

And also you don't need to expose ports (and this is actually what all integration tests should do to avoid port overlaps, but I remember there are some issues with kafka) if you are doing requests via container host

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

Labels

🍃 green ci 🌿 Fixing flaky tests in CI pr-not-for-changelog This PR should not be mentioned in the changelog

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants