Remove one more iOS 7 compile-time conditional.
Add NS_FORMAT_FUNCTION declarations to SLComposeString and SLComposeStringv.

This means that we get warned if the arguments do not match the
format specifiers in the failure descriptions for SLAssert*.
Retry launching the tests three times.

Even twice is not sufficient, per https://travis-ci.org/inkling/Subliminal/jobs/16975689.
Slightly relax the uniformity requirement for Subliminal's test distribution.

The test has failed on Travis a couple of times, most recently
https://travis-ci.org/inkling/Subliminal/builds/16975672.
Merge pull request #111 from tipbit/SLComposeString-format-decl-rebased

Add NS_FORMAT_FUNCTION declarations to SLComposeString and SLComposeStringv.
Merge pull request #110 from inkling/jeff/fix_build

Make one more iOS 7 CI change and fix the build.
Increase the interval used to determine when instruments has hung.

In https://travis-ci.org/inkling/Subliminal/jobs/16977489,
instruments can be seen to begin to log output to the terminal
--but not yet to the log file--when it was then killed.
Again increase the delay before alert handlers return.

To ensure that alert delegates receive their callbacks before tests continue.

On certain platforms i.e. Travis, iOS 7 occasionally requires a slightly higher delay.
Add some logging around keyboard test failures.
Simplify the test of the uniformity of Subliminal's test distributions.

After another failure of this test on Travis, I took another look at the chi-square code
and I don't think it's ever been correct and/or we've ever been applying it correctly.
We've been claiming that there is at least a 5% chance (recently changed to 7.5%)
that the distribution is uniform, but a chi-square test, when applied to a uniform distribution,
usually supports the claim that there is *less than* a 5% chance that the distribution
*is not* uniform. That is, we've been making a very weak claim. And it turns out
that the significance values found by the chi-square code have been all over the place:
often above 7.5%, but sometimes below (which is when this fails).

I'm still fairly certain that our randomization code is correct, i.e. our distributions
are uniform, and that we should be able to apply a chi-square test to support
that claim. But I don't think that it's worth trying to patch up this code.
I've replaced the chi-square test with a simpler claim which ought to verify
the practical use and validity of our randomization.
`-[SLPopover dismiss]` blocks until the popover has been fully dismissed.

So that clients do not have to wait for the popover to become invisible.
Merge pull request #112 from inkling/jeff/fix_build

Another attempt to fix the build.
Increase the interval `+[SLPopover dismiss]` waits before returning.

To ensure that the popover is invisible, in response to another failure on Travis:
https://travis-ci.org/inkling/Subliminal/jobs/16987504.
Merge pull request #113 from inkling/jeff/fix_build

Increase the interval `+[SLPopover dismiss]` waits before returning.
Merge remote-tracking branch 'upstream/master'

Conflicts:
	Subliminal.xcodeproj/project.pbxproj