Known Issue with Unit Tests in Xcode 3.2
Known Issue with Unit Tests in Xcode 3.2
- Subject: Known Issue with Unit Tests in Xcode 3.2
- From: Chris Espinosa <email@hidden>
- Date: Sat, 19 Sep 2009 10:07:43 -0700
Folks,
I'm surprised this hasn't come up here yet, but as we've responded
to questions in the Dev Forums, Stack Overflow, and Twitter, I want to
post here as well for the record.
Very late in Xcode 3.2 we inadvertently introduced a bug in
processing the results from Unit Tests for display in the Build
Results pane in which Xcode fails to parse the beginning of a test,
then when the end of that test comes, it fails to match up with the
beginning. This causes a hang and often an eventual crash.
The root cause is a missing character in a regular expression,
which causes unit tests whose time stamp Zulu offsets contain the
digit 5 to fail to parse. This means that through November 1, 2009,
users in Central Daylight Time are susceptible to this bug. The
simplest workaround is to change your Time Zone. Other workarounds
(involving changing the Unit Test scripts to suppress or rewrite the
Zulu offset of the time stamp) are circulating in the developer
community, and we are working on a more durable fix.
Note that this also may affect developers in Oman, the United Arab
Emirates, Georgia, Armenia, Azerbaijan, and parts of central Russia,
as well as the Seychelles and Mauritius that observe Summer Time, and
possibly India, Pakistan, Afghanistan, Tajikistan, Kyrgyzstan,
Uzbekistan, Turkmenistan, and central Russia that do not observe
Summer time. We have no bug reports from these regions but from
analysis of the bug we expect users in +0500 and +0550 Zulu to be
affected.
We apologize for the inconvenience and are working to rectify it.
Chris
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Xcode-users mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden