Merge build fails in Travis CI but the publish build is still started

[juwara0]

BUG REPORT

• I have ensured that the issue isn't already reported
• I have confirmed that the issue is reproducible with the latest released version
• I have deleted the FEATURE REQUEST / CODE CHANGE section

Summary

• Provide a general summary of the issue in the title above

In travis CI the merge build failed but the publish build still happened.

Expected Behavior

• What should happen?
  I would expect that if the merge build fails that a new version is not published

Actual Behavior

• What happens instead of the expected behavior?
• Is something broken, or not behaving as you expected?
• Attach a screenshot or recording as appropriate.

In travis CI the merge build failed but the publish build still started: https://travis-ci.org/ciena-blueplanet/ember-test-utils/builds/350444654?utm_source=github_status&utm_medium=notification

Publish build worked: A new release version 8.1.1 was created: b8fd51d

Possible Solution

I am not sure why this is happening.

Steps to Reproduce

n/a

Context

• How has this issue affected you? What are you trying to accomplish?
• Providing context helps us come up with a solution that is most useful in the real world.

Environment

Travis CI - linux 64
version of Node is: 8.1.2
version of npm is: 5.0.3
(answer all that are applicable)

• I am using the latest released version (can check with npm ls <package-name>)
• I am using these browsers:
  • Latest Chrome
  • Latest Firefox
• My version of Node is:
• My version of npm is:
• My OS is:
• Include the contents of your package.json file

[juwara0]

There are 17 tests that are failing in the merge build. They are the mocha tests in tests/cli