Skip to content

[cxx-interop] Temporarily exclude CxxSetToCollection benchmark from the build #81145

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

Merged
merged 1 commit into from
Apr 29, 2025

Conversation

egorzhdan
Copy link
Contributor

This is needed to unblock nightly toolchains, which are currently failing to build with an assertion:

swift-frontend: /home/build-user/build/buildbot_linux/llvm-linux-x86_64/tools/clang/include/clang/AST/TypeNodes.inc:79: TypeInfo clang::ASTContext::getTypeInfoImpl(const Type *) const: Assertion `!T->isDependentType() && "should not see dependent types here"' failed.

rdar://150067288

@egorzhdan egorzhdan added the c++ interop Feature: Interoperability with C++ label Apr 28, 2025
@egorzhdan egorzhdan requested a review from j-hui April 28, 2025 18:41
@egorzhdan egorzhdan requested a review from eeckstein as a code owner April 28, 2025 18:41
Copy link
Contributor

@j-hui j-hui left a comment

Choose a reason for hiding this comment

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

There were a couple others failing too, including VectorSum and StringConversion. Those should probably be commented out too.

@egorzhdan egorzhdan force-pushed the egorzhdan/bench-disable branch from 7437b2e to 8edd8d2 Compare April 28, 2025 18:47
…he build

This is needed to unblock nightly toolchains, which are currently failing to build with an assertion:
```
swift-frontend: /home/build-user/build/buildbot_linux/llvm-linux-x86_64/tools/clang/include/clang/AST/TypeNodes.inc:79: TypeInfo clang::ASTContext::getTypeInfoImpl(const Type *) const: Assertion `!T->isDependentType() && "should not see dependent types here"' failed.
```

rdar://150067288
@egorzhdan egorzhdan force-pushed the egorzhdan/bench-disable branch from 8edd8d2 to 85d6be5 Compare April 28, 2025 18:48
@egorzhdan
Copy link
Contributor Author

@swift-ci please benchmark

@egorzhdan
Copy link
Contributor Author

@swift-ci please smoke test

@egorzhdan
Copy link
Contributor Author

@j-hui good point! I disabled the other two, let's see if anything else is failing.

Copy link
Contributor

@j-hui j-hui left a comment

Choose a reason for hiding this comment

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

This looks good to me, but I'm wondering why you're commenting out the contents of the benchmark rather than commenting out the cmake entry (as you were doing originally)?

@j-hui
Copy link
Contributor

j-hui commented Apr 28, 2025

@swift-ci please smoke test macos platform

1 similar comment
@j-hui
Copy link
Contributor

j-hui commented Apr 29, 2025

@swift-ci please smoke test macos platform

@MaxDesiatov
Copy link
Contributor

@swift-ci smoke test macos

@MaxDesiatov MaxDesiatov enabled auto-merge (squash) April 29, 2025 09:12
@MaxDesiatov
Copy link
Contributor

@swift-ci smoke test macos

@egorzhdan
Copy link
Contributor Author

This looks good to me, but I'm wondering why you're commenting out the contents of the benchmark rather than commenting out the cmake entry (as you were doing originally)?

@j-hui the benchmarks can be built as a Swift Package, in which case CMake flags won't be applied. This way we can be certain that the problematic code won't be built regardless of the build system used.

@MaxDesiatov MaxDesiatov merged commit 86c30d6 into main Apr 29, 2025
4 checks passed
@MaxDesiatov MaxDesiatov deleted the egorzhdan/bench-disable branch April 29, 2025 16:57
@MaxDesiatov
Copy link
Contributor

@egorzhdan does this need a cherry-pick for 6.2?

j-hui added a commit to j-hui/swift that referenced this pull request May 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
c++ interop Feature: Interoperability with C++
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants