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

Block-style Initializer and properties: Allow injection of primitive #135

Merged
merged 1 commit into from
Dec 15, 2013

Conversation

eriksundin
Copy link
Contributor

Issue #100

@jasperblues
Copy link
Member

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.

jasperblues added a commit that referenced this pull request Dec 15, 2013
Block-style Initializer and properties: Allow injection of primitive
@jasperblues jasperblues merged commit f1a22c6 into appsquickly:master Dec 15, 2013
@eriksundin eriksundin deleted the inject-primitives branch December 15, 2013 01:59
@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

@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?

@jasperblues
Copy link
Member

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.

@eriksundin
Copy link
Contributor Author

@rhgills I've added new tests in TyphoonComponentDefinition+InstanceBuilderTests, was not failing for me ... so yes could be related to environment. Let me check.

@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

I commented out the two tests (related to NSUIntegerMax) that were failing for me in d900878.

@eriksundin
Copy link
Contributor Author

Thanks @rhgills

@eriksundin
Copy link
Contributor Author

I was/am getting a test failure on TyphoonBlockComponentFactory_CollectionTests (test_dealloc_cleans_up_method_advising) ... You guys not getting that one?

@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

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.

@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

Done.

@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

@jasperblues @eriksundin

Can you confirm master is back to passing?

@eriksundin
Copy link
Contributor Author

@rhgills Yes, passing for me. Working on fixing the tests you commented out.

@eriksundin
Copy link
Contributor Author

@rhgills I just pushed 02a7bcc with fixes. Can you check/confirm the tests pass on your machine?

@rhgills
Copy link
Contributor

rhgills commented Dec 15, 2013

All passing here!

@eriksundin
Copy link
Contributor Author

👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants