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

Don't enforce top-level repo name in BaseCostBasedPlanTest #16486

Conversation

findepi
Copy link
Member

@findepi findepi commented Mar 10, 2023

Engineers will typically check out the repo into a local folder named the same way: trino. This, however, doesn't work when an engineer needs to do a second checkout, or wants to make a backup of the repo for whatever purposes. The build and tests should not assume any particular name of the folder the repo is checked out into.

Engineers will typically check out the repo into a local folder named
the same way: `trino`. This, however, doesn't work when an engineer
needs to do a second checkout, or wants to make a backup of the repo for
whatever purposes. The build and tests should not assume any particular
name of the folder the repo is checked out into.
return workingDir.resolve("testing/trino-tests");
default:
throw new IllegalStateException("This class must be executed from trino-tests or Trino source directory");
if (isDirectory(workingDir.resolve(".git"))) {
Copy link
Member

Choose a reason for hiding this comment

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

I wonder if we should check for existence of .gitignore file instead since that is part of the checked out source.

Copy link
Member Author

Choose a reason for hiding this comment

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

you can have .gitignore at any level within the repo, but .git folder should be only one

@findepi findepi merged commit 1e38461 into trinodb:master Mar 11, 2023
@findepi findepi deleted the findepi/don-t-enforce-top-level-repo-name-in-basecostbasedplantest-400066 branch March 11, 2023 21:28
@github-actions github-actions bot added this to the 411 milestone Mar 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging this pull request may close these issues.

2 participants