[ https://issues.apache.org/jira/browse/CASSANDRA-15623?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087004#comment-17087004 ]
Michael Semb Wever commented on CASSANDRA-15623: ------------------------------------------------ [~djoshi], [~jrwest], looks like this broke ~25 cqlsh tests. That's nearly half of the cqlsh tests. - 3.0: https://ci-cassandra.apache.org/view/branches/job/Cassandra-3.0/16/testReport/ - 3.11: https://ci-cassandra.apache.org/view/Cassandra%203.11/job/Cassandra-3.11/20/testReport/ - 4.0: https://ci-cassandra.apache.org/view/Cassandra%204.0/job/Cassandra-trunk/84/testReport/ Where were the CI runs before this was committed? > When running CQLSH with STDIN input, exit with error status code if script > fails > -------------------------------------------------------------------------------- > > Key: CASSANDRA-15623 > URL: https://issues.apache.org/jira/browse/CASSANDRA-15623 > Project: Cassandra > Issue Type: Bug > Components: Legacy/Tools > Reporter: Jacob Becker > Assignee: Jacob Becker > Priority: Normal > Labels: pull-request-available > Fix For: 3.0.21, 3.11.7, 4.0 > > Time Spent: 0.5h > Remaining Estimate: 0h > > Assuming CASSANDRA-6344 is in place for years and considering that scripts > submitted with the `-e` option behave in a similar fashion, it is very > surprising that scripts submitted to STDIN (i.e. piped in) always exit with a > zero code, regardless of errors. I believe this should be fixed. -- This message was sent by Atlassian Jira (v8.3.4#803005) --------------------------------------------------------------------- To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org For additional commands, e-mail: commits-h...@cassandra.apache.org