RunSamples.cmd should signal failure if non-zero RC from sparkclr-submit script #257
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This tweak to
RunSamples.cmd
script makes it easier to detect any problems in the build environment, because build agent [eg VSO] will detect non-zero exit code which was previously being masked by extra commands at end of script.RunSamples.cmd
should signal runtime failure if non-zero RC from underlying call tosparkclr-submit.cmd
script. [The finalpopd
was previously masking this value.]Should have no affect on the core team's Appveyor build, but my private VSO build was not detecting / marking build failures when it should have been due to some test config issues.