Failures on OSX

[sublimetext]

Failures on OSX

[randy3k]

My guess is https://github.com/randy3k/UnitTesting/blob/1f97a12a8dc0a1a920a4e644a5be0769e4c8e010/sbin/install_sublime_text.sh#L53 opens and closes sublime text. If it closes fast enough, the Preference file won't be created and the close_windows_when_empty settings will be correctly applied. But it may not be the case.

We just need to just that last session to the front.

[randy3k]

hope cae5c2a and 0.10.6 will fix it.

BTW, thanks for bringing it up.

[randy3k]

Let me know if the latest release fix the random error. It should actually be discovered earlier, however we don't have enough users to allow such.

[gerardroche]

How can I go about testing it. There doesn't seem to be an easy way to select to use the latest master branch of UnitTesting. It would be nice to be able rerun failing builds with the latest version UnitTesting. We can set environment variables in Travis e.g. you can set UNIT_TESTING_MASTER=true and then rerun the build. If UnitTesting could use an environment variable like this it will make it easier to toggle the latest version on for testing.

[randy3k]

I have just tagged a release, it should use the latest version now. To use a different tag, check this https://github.com/randy3k/AutoWrap/blob/master/.travis.yml

I will improve the docs once I have time...

[gerardroche]

Yes it's fixed. I reran the failing builds using UnitTesting master and they all pass now. Thanks.

The UNITTESTING_TAG environment variable is exactly what I was looking for. With that you can set the tag or branch of UnitTesting to use without needing to modify the build itself. You can add the environment variable in the Travis Ci setting panel. Rerunning a build after setting it will use the latest UnitTesting. Very useful, because it saves having to needlessly edit the build itself.

[randy3k]

Thanks for bringing up this, I didn't realize there is such a usage.