Skip to content

[android] XFAIL opt-remark-generator.swift in ARMv7 #33500

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

Conversation

drodriguez
Copy link
Contributor

Android ARMv7 doesn't seem to simplify the remarks from
Optional to just SubKlass, while other platforms do.

I did not find any clues in #33171 what it might be happening, so XFAIL
the test to avoid a failing build.

Android ARMv7 doesn't seem to simplify the remarks from
Optional<SubKlass> to just SubKlass, while other platforms do.

I did not find any clues in swiftlang#33171 what it might be happening, so XFAIL
the test to avoid a failing build.
@drodriguez drodriguez requested a review from gottesmm August 16, 2020 23:18
@drodriguez
Copy link
Contributor Author

@swift-ci please test

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - a0333a4

@drodriguez
Copy link
Contributor Author

@swift-ci please test macos platform

@swift-ci
Copy link
Contributor

Build failed
Swift Test OS X Platform
Git Sha - a0333a4

@drodriguez
Copy link
Contributor Author

@swift-ci please test macos platform

@drodriguez drodriguez merged commit bd1e23c into swiftlang:master Aug 17, 2020
@drodriguez drodriguez deleted the android-armv7-xfail-opt-remark-generator branch August 17, 2020 21:07
Copy link
Contributor

@gottesmm gottesmm left a comment

Choose a reason for hiding this comment

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

LGTM.

@gottesmm
Copy link
Contributor

@drodriguez if we aren't simplifying this, it is sort of weird. Maybe file an SR?

drodriguez added a commit to drodriguez/swift that referenced this pull request Nov 3, 2020
These tests were disabled in swiftlang#33500 (a0333a4) and swiftlang#30390
(6ac04c6) because the optimizer did not seem to be working in
Android ARMv7.

At some moment between October 21st and October 30th something unbroke
the tests. I have looked into the changes in the SILOptimizer directory,
but I cannot pinpoint it to any of them in particular. It might be also
changes introduced in LLVM.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants