Skip to content

ARROW-16601: [C++][FlightRPC] Don't enforcing static link with static GoogleTest for arrow_flight_testing - #13180

Merged
kou merged 1 commit into
apache:masterfrom
kou:cpp-flight-gtest-linkage
May 18, 2022
Merged

ARROW-16601: [C++][FlightRPC] Don't enforcing static link with static GoogleTest for arrow_flight_testing#13180
kou merged 1 commit into
apache:masterfrom
kou:cpp-flight-gtest-linkage

Conversation

@kou

@koukou commented May 17, 2022

Copy link
Copy Markdown
Member

We can remove this because #13169/ARROW-16588 solved the link problem.

… GoogleTest for arrow_flight_testing
We can remove this because apache#13169/ARROW-16588 solved the link problem.
@github-actions

Copy link
Copy Markdown

@github-actions

Copy link
Copy Markdown

⚠️ Ticket has not been started in JIRA, please click 'Start Progress'.

@koukou changed the title ARROW-16601: [C++][FlightRPC] Don't encofcing static link with static GoogleTest for arrow_flight_testingARROW-16601: [C++][FlightRPC] Don't enforcing static link with static GoogleTest for arrow_flight_testingMay 18, 2022
@kou
kou merged commit 6faee47 into apache:masterMay 18, 2022
@kou
kou deleted the cpp-flight-gtest-linkage branch May 18, 2022 03:20
kou added a commit to kou/arrow that referenced this pull request May 18, 2022
We use local "git merge" to merge a pull request in
dev/merge_arrow_pr.py.
If we use "git merge" to merge a pull request, GitHub's Web UI shows
"Closed" mark not "Merged" mark in a pull request page. This sometimes
confuses new contributors. "Why was my pull request closed without
merging?" See
apache#12004 (comment) for
example.
If we use GitHub API
https://docs.github.com/en/rest/pulls/pulls#merge-a-pull-request to
merge a pull request, GitHub's Web UI shows "Merged" mark not "Closed"
mark. See apache#13180 for example. I
used GitHub API to merge the pull request.
And we don't need to create a local branch on local repository to
merge a pull request. But we must specify ARROW_GITHUB_API_TOKEN to
run dev/merge_arrow_pr.py.
kou added a commit that referenced this pull request May 31, 2022
We use local "git merge" to merge a pull request in
dev/merge_arrow_pr.py.
If we use "git merge" to merge a pull request, GitHub's Web UI shows
"Closed" mark not "Merged" mark in a pull request page. This sometimes
confuses new contributors. "Why was my pull request closed without
merging?" See
#12004 (comment) for
example.
If we use GitHub API
https://docs.github.com/en/rest/pulls/pulls#merge-a-pull-request to
merge a pull request, GitHub's Web UI shows "Merged" mark not "Closed"
mark. See #13180 for example. I
used GitHub API to merge the pull request.
And we don't need to create a local branch on local repository to
merge a pull request. But we must specify ARROW_GITHUB_API_TOKEN to
run dev/merge_arrow_pr.py.
Authored-by: Sutou Kouhei <kou@clear-code.com>
Signed-off-by: Sutou Kouhei <kou@clear-code.com>
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@kou@cyb70289