Cannot get the build to fail with force:apex:test-run

[afawcett]

When i run the following from the command line on my workstation with failing tests in place...

sfdx force:apex:test:run --wait 10

And echo the return code i see the following...

echo $?
100

However when i run the same command (all be it with an alias arg) in Travis it returns 0?

Is there something contextual about the commands return code?

You can see my project at https://github.com/afawcett/declarative-lookup-rollup-summaries

[afawcett]

Take a look at this latest build for an example.

[dcarroll]

Taking a look. Please stand by.

[amphro]

The only conditional is that the failing property is set and not 0. You could run the command with --json and look at that property in the summary. Something like ... | jq .result.summary.failing. I'm not sure how that would happen, but if there is no summary or something else looks off, that could explain it.

[dcarroll]

Ah, --json might be the key, I'll test it out.

…

On Tue, Apr 17, 2018 at 11:06 AM, Thomas Dvornik ***@***.***> wrote: The only conditional is that the failing property is set and not 0. You could run the command with --json and look at that property in the summary. Something like ... | jq .result.summary.failing. I'm not sure how that would happen, but if there is no summary or something else looks off, that could explain it. — You are receiving this because you commented. Reply to this email directly, view it on GitHub <#58 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AAHGHjALLbABOMk5lI0xqgkhSwArCG13ks5tpi8XgaJpZM4TVTng> .

[afawcett]

@amphro yeah the really odd thing is i get a 100 status code when running locally. This repo however does seem to work, yet @dcarroll and i can see now difference between my repos yaml config and this one (that is working). So i would say the output could be the difference if it was not for the fact it outputs the correct status locally... its a complete mystery.... i think i will try CircleCI next...

[afawcett]

@amphro and thanks for the jq idea... i will keep that in mind, cool tool!

[jcory]

@afawcett @dcarroll Did you ever reach any sort of resolution for this? We're encountering the same issue. I'd like to avoid switching to CircleCI, but at this point, that may be our best option.

[christianmoustrides]

Anyone figure this one out?

[ccheevers]

Any update on this issue, a failing assertion still results in a passed test with travis....