Let "neither SUCCESS nor FAILURE" result in failed builds
Don't exit with non-zero status if builderCI is tested
Fix tests
Use env variable instead
Merge pull request #66 from fniephaus/error-handling

Let "neither SUCCESS nor FAILURE" result in failed builds ... for this purpose I think we are fine ...  there may be one or two places in the wild that will fail now, but I think that they should be cleaned up with an explicit test result
Add support for explict success on no failure:

Using the following at end of test will explicitly mark the test as success:

    Smalltalk
        at: #'TravisCISuccessNoFailure'
        put: [ :successFilename  |
          MetacelloBuilderTravisCI successOnNoFailures: successFilename ]

Using this in tests/travisCI.st since Sample configs have no tests...

Pare down lineup for testing...

Restore unconditional `exit 1` in buildTravisStatusCheck.sh.

Cross fingers:)
tighten up syntax
the last syntax error?
those periods running off an hiding ... tsk, tsk
okay ... looks like skipMetacelloBootstrap.st needs the success on no failure handling
include test harness in the skipMetacello bootstrap case
okay down to debugging squeak4.5 failure
must have been a different failure mechanism ... setting -x in a script should not impact execution ... removing -x and crossing fingers
Merge branch 'dev'