Skip to content

Conversation

kou
Copy link
Member

@kou kou commented Apr 1, 2025

Rationale for this change

The current bundle Google 1.11.0 was released in 2021. It's too old.

What changes are included in this PR?

Update to the latest GoogleTest: 1.16.0

Are these changes tested?

Yes.

Are there any user-facing changes?

No.

Copy link

github-actions bot commented Apr 1, 2025

⚠️ GitHub issue #45986 has been automatically assigned in GitHub to PR creator.

@kou kou force-pushed the cpp-gtest branch 2 times, most recently from a7bec63 to c4aea3f Compare April 2, 2025 05:41
@kou
Copy link
Member Author

kou commented Apr 2, 2025

This is ready.

Copy link
Member

@raulcd raulcd left a comment

Choose a reason for hiding this comment

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

👍

@@ -210,7 +210,6 @@ jobs:
ARROW_WITH_SNAPPY: ON
ARROW_WITH_ZLIB: ON
ARROW_WITH_ZSTD: ON
GTest_SOURCE: BUNDLED
Copy link
Member

Choose a reason for hiding this comment

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

Note for self: next time we add something like this we probably want to add a comment on why we are adding it so we understand we can remove it later on. I didn't find a good enough reason on why it was added.
I had to go to a comment:
#14177 (comment)
and a commit to see where was this coming from:
1e33ad9

@github-actions github-actions bot added awaiting review Awaiting review awaiting merge Awaiting merge and removed awaiting committer review Awaiting committer review labels Apr 3, 2025
@raulcd raulcd merged commit eaeb64b into apache:main Apr 3, 2025
29 of 30 checks passed
@raulcd raulcd removed awaiting review Awaiting review awaiting merge Awaiting merge labels Apr 3, 2025
@kou kou deleted the cpp-gtest branch April 3, 2025 08:01
Copy link

After merging your PR, Conbench analyzed the 4 benchmarking runs that have been run so far on merge-commit eaeb64b.

There were no benchmark performance regressions. 🎉

The full Conbench report has more details. It also includes information about 17 possible false positives for unstable benchmarks that are known to sometimes produce them.

lriggs pushed a commit to lriggs/arrow that referenced this pull request Apr 15, 2025
### Rationale for this change

The current bundle Google 1.11.0 was released in 2021. It's too old.

### What changes are included in this PR?

Update to the latest GoogleTest: 1.16.0

### Are these changes tested?

Yes.

### Are there any user-facing changes?

No.
* GitHub Issue: apache#45986

Authored-by: Sutou Kouhei <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
zanmato1984 pushed a commit to zanmato1984/arrow that referenced this pull request Apr 15, 2025
### Rationale for this change

The current bundle Google 1.11.0 was released in 2021. It's too old.

### What changes are included in this PR?

Update to the latest GoogleTest: 1.16.0

### Are these changes tested?

Yes.

### Are there any user-facing changes?

No.
* GitHub Issue: apache#45986

Authored-by: Sutou Kouhei <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
zanmato1984 pushed a commit to zanmato1984/arrow that referenced this pull request Apr 15, 2025
### Rationale for this change

The current bundle Google 1.11.0 was released in 2021. It's too old.

### What changes are included in this PR?

Update to the latest GoogleTest: 1.16.0

### Are these changes tested?

Yes.

### Are there any user-facing changes?

No.
* GitHub Issue: apache#45986

Authored-by: Sutou Kouhei <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
assignUser pushed a commit that referenced this pull request Apr 22, 2025
### Rationale for this change

The current bundle Google 1.11.0 was released in 2021. It's too old.

### What changes are included in this PR?

Update to the latest GoogleTest: 1.16.0

### Are these changes tested?

Yes.

### Are there any user-facing changes?

No.
* GitHub Issue: #45986

Authored-by: Sutou Kouhei <[email protected]>
Signed-off-by: Raúl Cumplido <[email protected]>
Sign up for free to 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