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

[SR-5591] Failures within DateFormatter tests #4269

Open
swift-ci opened this issue Jul 31, 2017 · 5 comments
Open

[SR-5591] Failures within DateFormatter tests #4269

swift-ci opened this issue Jul 31, 2017 · 5 comments

Comments

@swift-ci
Copy link
Contributor

Previous ID SR-5591
Radar None
Original Reporter ddunn (JIRA User)
Type Bug
Environment

MacOS
However the tests need updating on MacOS so the failures would then occur on Linux

Additional Detail from JIRA
Votes 0
Component/s Foundation
Labels Bug
Assignee mattrajca (JIRA)
Priority Medium

md5: 15e8dd51a957bed077f409e6ac58a219

Issue Description:

It seems the behavior of the .full property within the DateFormatter has changed on Darwin. Rather than returning 'GMT' for the timezone it now returns 'Greenwhich Mean Time' however on Linux 'GMT' is still being returned so this is causing failures in the tests on Darwin.

The tests need updating which will move these failures over to the Linux build and there they need fixing.

@belkadan
Copy link

cc @phausler

@phausler
Copy link
Member

The Darwin behavior is the expected format (that is what it does on macOS with the objc foundation). So we should update the linux code to emit the same values.

@spevans
Copy link
Collaborator

spevans commented Jul 31, 2017

Ive just been looking at this. I updated the tests to work correctly on macOS and disabled them on linux for now. I think there is an underlying issue with ICU as the Foundation / CoreFoundation code is doing the right thing on Linux, its just the ICU isnt outputting the correct response. Although it seems to work correctly with a different timezone (PST instead of GMT) !

@swift-ci
Copy link
Contributor Author

Comment by David Dunn (JIRA)

I've come to the same conclusion as you Simon Evans. I've also updated the MacOS tests, and currently looking at fixing the Linux tests which lead me to the incorrect version of ICU on Ubuntu (55.1 whereas 57.1 on MacOS).

We've been able to run the build script on Ubuntu 16.04 which picked up a newer version of ICU (57.1) using a change made in your PR Simon however this didn't fix the issue we were seeing in the tests. I've also been speaking to Tony Parker about this and he informed me that Apple actually ships its own additions to ICU as well and that these additions are used by Foundation in various places so it'd be that version of ICU he'd want shipping as a part of Swift. We haven't been able to get this particular version of ICU to work within the build script yet but I'll update with any progress we make.

@spevans
Copy link
Collaborator

spevans commented Jul 31, 2017

Ive done a fix for the tests in #1147

Ive actually tested ICU59.1 directly with a small C program and its still broken with timezone GMT but actually works with timezone PST. It does however work on macOS using the system default icucore library. So I think it is actually an ICU issue not a linux foundation/corefoundation one

@swift-ci swift-ci transferred this issue from apple/swift-issues Apr 25, 2022
@shahmishal shahmishal transferred this issue from apple/swift May 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants