-
Notifications
You must be signed in to change notification settings - Fork 268
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
Block-style Initializer and properties: Allow injection of primitive #135
Conversation
We've got four failing tests on the main branch here. . . makes it difficult to merge in other contributions. @rhgills - huge appreciation for identifying these issues. However, please follow the policy we agreed. |
Block-style Initializer and properties: Allow injection of primitive
@jasperblues My apologies. Everything was passing on my end, but I see we have three failing tests on master right now. One in (the re-added) TyphoonTestUtilsTests and two in TyphoonComponentDefinition+InstanceBuilderTests (which may be an issue with different sizes of NSUIntegerMax between 32 and 64 bit). What tests do you see as failing? I haven't changed either of these recently, did you mean to @eriksundin? |
TyphoonTestUtiils tests was failing just in the assertion: "Condition didn't happen before 2.0" now "Condition didn't happen before 0.1" . . fixed. . not sure what is happening in the other class. |
@rhgills I've added new tests in TyphoonComponentDefinition+InstanceBuilderTests, was not failing for me ... so yes could be related to environment. Let me check. |
I commented out the two tests (related to NSUIntegerMax) that were failing for me in d900878. |
Thanks @rhgills |
I was/am getting a test failure on TyphoonBlockComponentFactory_CollectionTests (test_dealloc_cleans_up_method_advising) ... You guys not getting that one? |
I wasn't before, but I began to have some failures today when I was making some changes to the AssemblyAdviser (that I haven't pushed yet). That test passes for me on the current HEAD. I believe the issue with that test in general is that we can't control when the assembly will be deallocated by ARC. It's interesting that you're getting a failure there and I'm not, I wouldn't think ARC would appear nondeterministic in that way... I've scrapped that entire test locally and replaced it with a unit test on the AssemblyAdviser. I'll go ahead and quickly remove that test from the server now. |
Done. |
Can you confirm master is back to passing? |
@rhgills Yes, passing for me. Working on fixing the tests you commented out. |
All passing here! |
👍 |
Issue #100