SenTestCase在Xcode 3.2和XCBuildLogCommandInvocationSection错误 [英] SenTestCase in Xcode 3.2 and XCBuildLogCommandInvocationSection Errors

查看:129
本文介绍了SenTestCase在Xcode 3.2和XCBuildLogCommandInvocationSection错误的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

我有一套SenTestCase,导致XCode 3.2.4中的问题。当尝试编译(使用非常基本的STFail(@);)时,会出现以下编译器错误:

I have a set of SenTestCase that are causing issues in XCode 3.2.4. When attempting to compile (with a very basic STFail(@"");) the following compiler errors occur:


处理命令输出: -

[XCBuildLogCommandInvocationSectionRecorder endMarker]:

发送到实例的无法识别的选择器

An internal error occurred when handling command output: -
[XCBuildLogCommandInvocationSectionRecorder endMarker]:
unrecognized selector sent to instance

处理时发生内部错误命令输出: -

[XCBuildLogCommandInvocationSection setTestsPassedString:]:

无法识别的选择器发送到实例

An internal error occurred when handling command output: -
[XCBuildLogCommandInvocationSection setTestsPassedString:]:
unrecognized selector sent to instance

我已经包含了来自'/ Developer / Library / Frameworks'的SenTestkingKit.framework,并且只是由目标> Targets> Add> New Target> Cocoa Touch> Unit Test Bundle创建的。有任何想法吗?谢谢!

I've included the SenTestkingKit.framework from '/Developer/Library/Frameworks' and just created by target by 'Targets > Add > New Target > Cocoa Touch > Unit Test Bundle'. Any ideas? Thanks!

推荐答案

这似乎是一个回归,报告代码的某些部分不遵守时区问题。

It seems to be a regression with some part of the reporting code not respecting timezone issues. The output is tagged as ending before it began, so gets very confused and chokes.

在Google上某处找到的一种解决方法是更改​​运行脚本

One work-around, that I found somewhere on Google, is to change the Run Script stage of the target.

更改

"${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests" 

"${SYSTEM_DEVELOPER_DIR}/Tools/RunUnitTests" 1> /tmp/RunUnitTests.out 

它解决问题,而不是解决它,但工作。

It’s working round the issue, rather than solving it, but does work.

这篇关于SenTestCase在Xcode 3.2和XCBuildLogCommandInvocationSection错误的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆