Command Line Tests Failed, whe simulator SDK_VERSION is set to 6.0 about cedar HOT 8 CLOSED

My main.m is looked like this now:

#if CEDAR_KNOWS_SOMETHING_ABOUT_FAILING_ON_IOS6_SIMULATOR  
@implementation UIWindow (Private)

- (void)_createContext {

}

@end
#endif


int main(int argc, char *argv[])
{
   @autoreleasepool {

#if CEDAR_KNOWS_SOMETHING_ABOUT_FAILING_ON_IOS6_SIMULATOR
      CFMessagePortCreateLocal(NULL, (CFStringRef) @"PurpleWorkspacePort", NULL, NULL,NULL);

      // Default behaviour
      return UIApplicationMain(argc, argv, nil, @"CedarApplicationDelegate");

#endif

      // Also I've decied to discard lgic for jenkins-user
      NSString * user = [NSString stringWithCString:getenv("USER") encoding:NSUTF8StringEncoding];
      if ([user isEqualToString:@"jenkins-ci"]) {
         int exitStatus = runSpecsWithinUIApplication();
         exitWithStatusFromUIApplication(exitStatus);
         return 0;
      }

      // Default behaviour
      return UIApplicationMain(argc, argv, nil, @"CedarApplicationDelegate");
   }
}

And test run in RakeFile is now looking like here:

  system_or_exit "xcodebuild -workspace #{WORKSPACE_NAME}.xcworkspace -scheme #{SCHEME_NAME} -configuration #{CONFIGURATION} -sdk iphonesimulator6.0 build SYMROOT=#{BUILD_DIR} GCC_PREPROCESSOR_DEFINITIONS='$GCC_PREPROCESSOR_DEFINITIONS CEDAR_KNOWS_SOMETHING_ABOUT_FAILING_ON_IOS6_SIMULATOR=1'", output_file("uispecs")

from cedar.

Thanks for figuring this out, it's been a thorn in my side for some time. I've tried it and it works.

I've filed a story in the public Pivotal Tracker project to add the fix to the codebase:

https://www.pivotaltracker.com/story/show/42793177

Thanks again for your contributions!

from cedar.

Has there been any progress on fixing this issue?

from cedar.

What is the issue you are having? This has been closed for 7 months.

Also, if you look at the public CI build on travis-ci you will see that cedar is compiled and run with a variety of SDK and runtime versions, all passing: https://travis-ci.org/pivotal/cedar

from cedar.

I am seeing the same error message that cause the ticket it be created in the first place

And the workaround does not work either--that results in another message (which I do not have handy at the moment.)

Regards,

Bob

Sent from my iPhone

On Aug 29, 2013, at 11:58 AM, Andrew Kitchen [email protected] wrote:

What is the issue you are having? This has been closed for 7 months.

Also, if you look at the public CI build on travis-ci you will see that cedar is compiled and run with a variety of SDK and runtime versions, all passing: https://travis-ci.org/pivotal/cedar

—
Reply to this email directly or view it on GitHub.

from cedar.

Hi Bob,

How did you upgrade to the latest Cedar?  If you ran the install script, this will only update the library in the Xcode templates, so only newly created spec targets will have the fixes.





We're working on a way to allow users to easily upgrade existing targets, but for now your best bet is probably to create a new, throw-away cedar target and update the Cedar.framework and/or Cedar-iOS.framework and Rakefiles in your existing target from that.





Hope this helps,

—

Sam

On Thu, Aug 29, 2013 at 6:44 PM, Bob White [email protected]
wrote:

I am seeing the same error message that cause the ticket it be created in the first place
And the workaround does not work either--that results in another message (which I do not have handy at the moment.)
Regards,
Bob
Sent from my iPhone
On Aug 29, 2013, at 11:58 AM, Andrew Kitchen [email protected] wrote:

What is the issue you are having? This has been closed for 7 months.

Also, if you look at the public CI build on travis-ci you will see that cedar is compiled and run with a variety of SDK and runtime versions, all passing: https://travis-ci.org/pivotal/cedar

—

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub:
#58 (comment)

from cedar.

I am new to Cedar and just ran the install script via a task I added to my
local Rakefile:

namespace :cedar do
task :install do
system_or_exit "curl -L
https://raw.github.com/pivotal/cedar/master/install.sh | bash"
end
end

This was within the last 48 hours (for the first time) so I think Cedar
should be very fresh.

I got the example spec and one of my own running in Xcode, but when I try
to run from the command line 'bundle exec rake Specs' (Specs is the name of
my test target) I see:

...
    setenv YACC yacc
    /bin/sh -c "\"/Users/bwhite/Garuda/Medidata PRO/Medidata
PRO/build/Medidata
PRO.build/Debug-iphonesimulator/Specs.build/Script-E2A0FC5817CE84FF008457B5.sh\""
/Applications/Xcode.app/Contents/Developer/Tools/RunUnitTests:68: note:
RunUnitTests exited without running tests because TEST_AFTER_BUILD was set
to NO.
** BUILD SUCCEEDED **
Executing Medidata\ PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO
-RegisterForSystemEvents -SenTest All2013-08-29 20:21:42.663
ePRO[78475:f07] Unknown Device Type. Using UIUserInterfaceIdiomPhone based
on screen size
Terminating since there is no workspace.
Allanon:Garuda bwhite$ ls -al Medidata\
PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO
-rwxr-xr-x  1 bwhite  MDSOL\Domain Users  8330476 Aug 29 11:14 Medidata
PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO

(It might partly be my fault--I am trying also to update the
Cedar-generated Rakefile to deal with spaces in the BUILD_ROOT path. This
is for a legacy application I've been asked to wrap some testing around.)

But when searching for answers I found the same error and noticed there
wasn't any history attached to the issue here so I was unsure if it was
still an issue or not.

Right now I am simply testing tools for eventual inclusion in a Jenkins CI
environment.

If there's a more appropriate place to have this discussion, please let me
know.

Bob

from cedar.

Thanks for clarifying.

It's probably best discussed on [email protected]

As Andrew mentioned, this was fixed a while ago for most folks.

I'm curious as to what else could be triggering this.

If you could copy your last reply to this thread to the list together with your Xcode version and iOS simulator version we can follow up there.
—
Sam

On Thu, Aug 29, 2013 at 8:45 PM, Bob White [email protected]
wrote:

I am new to Cedar and just ran the install script via a task I added to my
local Rakefile:
namespace :cedar do
task :install do
system_or_exit "curl -L
https://raw.github.com/pivotal/cedar/master/install.sh | bash"
end
end
This was within the last 48 hours (for the first time) so I think Cedar
should be very fresh.
I got the example spec and one of my own running in Xcode, but when I try
to run from the command line 'bundle exec rake Specs' (Specs is the name of
my test target) I see:
...
setenv YACC yacc
/bin/sh -c ""/Users/bwhite/Garuda/Medidata PRO/Medidata
PRO/build/Medidata
PRO.build/Debug-iphonesimulator/Specs.build/Script-E2A0FC5817CE84FF008457B5.sh""
/Applications/Xcode.app/Contents/Developer/Tools/RunUnitTests:68: note:
RunUnitTests exited without running tests because TEST_AFTER_BUILD was set
to NO.
** BUILD SUCCEEDED **
Executing Medidata\ PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO
-RegisterForSystemEvents -SenTest All2013-08-29 20:21:42.663
ePRO[78475:f07] Unknown Device Type. Using UIUserInterfaceIdiomPhone based
on screen size
Terminating since there is no workspace.
Allanon:Garuda bwhite$ ls -al Medidata
PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO
-rwxr-xr-x 1 bwhite MDSOL\Domain Users 8330476 Aug 29 11:14 Medidata
PRO/build/Products/Debug-iphonesimulator/ePRO.app/ePRO
(It might partly be my fault--I am trying also to update the
Cedar-generated Rakefile to deal with spaces in the BUILD_ROOT path. This
is for a legacy application I've been asked to wrap some testing around.)
But when searching for answers I found the same error and noticed there
wasn't any history attached to the issue here so I was unsure if it was
still an issue or not.
Right now I am simply testing tools for eventual inclusion in a Jenkins CI
environment.
If there's a more appropriate place to have this discussion, please let me
know.
Bob
On Thu, Aug 29, 2013 at 7:16 PM, Sam Coward [email protected]:

Hi Bob,

How did you upgrade to the latest Cedar? If you ran the install script,
this will only update the library in the Xcode templates, so only newly
created spec targets will have the fixes.

We're working on a way to allow users to easily upgrade existing targets,
but for now your best bet is probably to create a new, throw-away cedar
target and update the Cedar.framework and/or Cedar-iOS.framework and
Rakefiles in your existing target from that.

Hope this helps,

—
Sam

On Thu, Aug 29, 2013 at 6:44 PM, Bob White [email protected]
wrote:

I am seeing the same error message that cause the ticket it be created
in the first place
And the workaround does not work either--that results in another message
(which I do not have handy at the moment.)
Regards,
Bob
Sent from my iPhone
On Aug 29, 2013, at 11:58 AM, Andrew Kitchen [email protected]
wrote:

What is the issue you are having? This has been closed for 7 months.

Also, if you look at the public CI build on travis-ci you will see that
cedar is compiled and run with a variety of SDK and runtime versions, all
passing: https://travis-ci.org/pivotal/cedar

—

Reply to this email directly or view it on GitHub.

Reply to this email directly or view it on GitHub:
#58 (comment)

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/58#issuecomment-23530675
.

Bob White | Senior Software Engineer | Medidata Solutions
Worldwidehttp://www.mdsol.com
79 Fifth Avenue, 8th Floor, New York, NY 10003
[email protected] | mobile: +1 315 430 2165 | main: +1 212 918 1800 | conf:
+1 719 234 7872, pc:109 557 4880
Follow Us: Twitter http://twitter.com/#!/Medidata |
LinkedInhttp://www.linkedin.com/company/medidata-solutions
You are hereby notified that any unauthorized distribution or copying of
this transmittal or its attachments is prohibited. The information in this
transmittal and any attachments are confidential and intended only for the
recipient(s) listed above. If you have received this transmittal in error,

please notify the sender.

Reply to this email directly or view it on GitHub:
#58 (comment)

from cedar.