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

Ability to specify initial Instruments launch timeout from subliminal-test #141

Open
jazzychad opened this issue Mar 20, 2014 · 1 comment
Labels

Comments

@jazzychad
Copy link

We are noticing that it always takes X runs of the subliminal runner to successfully wait for Instruments to launch in CI - so basically the first X-1 builds are wasted time while we wait for the Instruments timeout to become high enough.

It would be handy to be able to specify the initial (or some additional) Instruments launch timeout value (in seconds probably) from the subliminal-test arguments from command line.

@wearhere
Copy link
Contributor

Sounds fine to me. I'm surprised you see that it consistently takes instruments a certain amount of time to launch--it varies widely between runs both here on Travis and locally using Jenkins--but ¯_(ツ)_/¯. I'd probably implement this using an environment variable rather than another argument to subliminal-test--it has so many already and this is kinda advanced usage.

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

No branches or pull requests

2 participants