This created a few head scratches - due to the subshell command, the checkout of a concrete hash fails silently, creating mismatched packages downstream. This PR propagates the error message in that case. I wonder if there is a more general solution to this (not being a shell expert), as similar things happen for us in a few scenarios (e.g. install.sh fails silently, too)
This created a few head scratches - due to the subshell command, the checkout of a concrete hash fails silently, creating mismatched packages downstream. This PR propagates the error message in that case. I wonder if there is a more general solution to this (not being a shell expert), as similar things happen for us in a few scenarios (e.g. install.sh fails silently, too)
This created a few head scratches - due to the subshell command, the checkout of a concrete hash fails silently, creating mismatched packages downstream. This PR propagates the error message in that case. I wonder if there is a more general solution to this (not being a shell expert), as similar things happen for us in a few scenarios (e.g. install.sh fails silently, too)
Not sure what a general solutions would be. May be we should add more checking into install.sh, too.