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

[stdlib] Remove invalid _sanityCheck #9815

Merged
merged 1 commit into from
May 21, 2017
Merged

Conversation

dabrahams
Copy link
Contributor

A Character should contain only a single grapheme, but we can't formally require it because of grapheme cluster literals and the shifting sands of Unicode. Fixes https://bugs.swift.org/browse/SR-4955

Note: the stray change in the comment is due to GitHub's editor changing all text from decomposed to precomposed.

A `Character` _should_ contain only a single grapheme, but we can't formally require it because of grapheme cluster literals and the shifting sands of Unicode.  Fixes https://bugs.swift.org/browse/SR-4955
@dabrahams
Copy link
Contributor Author

@swift-ci Please smoke test and merge

@swift-ci swift-ci merged commit f1d08d9 into master May 21, 2017
@dabrahams dabrahams deleted the character-invalid-sanity-check branch May 21, 2017 16:59
@palimondo
Copy link
Contributor

This indeed fixed SR-4955 on my machine.
I don't understand why was only I affected… My configuration should be normal AFAIK: build-script -R. Are there some processor specific optimizations involved somewhere? Only atypical thing is that I'm running on 8 years old Core 2 duo here…

@gottesmm
Copy link
Contributor

@palimondo The issue is that our normal perf test run builds without assertions. This was caught by a different bot that we have internally that builds the perf test with assertions. I could move it externally, I just have not gotten around to it.

@palimondo
Copy link
Contributor

@gottesman And the perf-test I get locally out of build-script -R is with assertions?

@gottesmm
Copy link
Contributor

@palimondo Did you do a clean build? If not, look in your build directory for CMakeCache.txt and see what SWIFT_STDLIB_ASSERTIONS is set to. Reconfigs sometimes can cause that value to get out of sync.

@palimondo
Copy link
Contributor

Um... clean build, when? I have never adjusted assertions AFAIK. I did clean build
(by deleting contests of build directory) when SR-4955 was failing for me. IIRC it looks like Dave was able to reproduce my error on a build with assertions and discovered the invalid _sanityCheck. What I don’t understand how/why I stumbled upon this and how it only manifested on my machine.

@palimondo
Copy link
Contributor

@gottesmm While I have your ear... I wrote you an email with request for guidance re: tests and modularization of Benchmark_Driver. Could you respond, plz?

@gottesmm
Copy link
Contributor

I saw your email. It was a long email, so the response took some thoughts. I kept on getting pulled into things over the weekend so I was unable to. I will finish responding later today.

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.

4 participants