Timeline for Is there a simple test for anything printed on stderr in shell/Bash?
Current License: CC BY-SA 3.0
13 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Mar 18, 2021 at 19:14 | answer | added | Notiz Me | timeline score: 0 | |
| Aug 23, 2017 at 16:11 | answer | added | Stéphane Chazelas | timeline score: 4 | |
| Aug 23, 2017 at 15:59 | history | edited | gertvdijk | CC BY-SA 3.0 |
added 184 characters in body
|
| Aug 23, 2017 at 15:51 | comment | added | DopeGhoti | "CI" is generally "Continuous Integration"; this is likely being rolled into a Bamboo or Jenkins (et cetera) stack. | |
| Aug 23, 2017 at 15:50 | comment | added | gertvdijk |
@Alex Not from inside the subshell. At least not in my situation. E.g. mycommand 2> >(if grep .; then exit 1; else echo OK; fi) won't exit the main shell script.
|
|
| Aug 23, 2017 at 15:50 | answer | added | DopeGhoti | timeline score: 0 | |
| Aug 23, 2017 at 15:43 | comment | added | Alex |
exit 1 exits the script... what do you mean, it won't exit the main program?
|
|
| Aug 23, 2017 at 15:10 | comment | added | gertvdijk | @Alex clarified in Q I hope :) | |
| Aug 23, 2017 at 15:07 | history | edited | gertvdijk | CC BY-SA 3.0 |
update from comments
|
| Aug 23, 2017 at 15:04 | comment | added | Alex |
I agree with Ulrich; also, what do you mean however, I am not able to control the main shell here to exit?
|
|
| Aug 23, 2017 at 15:04 | comment | added | gertvdijk | @UlrichSchwarz yeah, but there's also perfectly valid output on stdout. Forgot to mention that. I'd like to maintain all output. Will update Q. | |
| Aug 23, 2017 at 15:01 | comment | added | Ulrich Schwarz | My vague thought would be that if you modify attempt 2 to use a pipe instead, you'd get the exit code of the piped-through code, right? | |
| Aug 23, 2017 at 14:49 | history | asked | gertvdijk | CC BY-SA 3.0 |