Displaying 3 results from an estimated 3 matches for "something_fail".
Did you mean:
something_failed
2015 Jul 23
1
[LLVMdev] [cfe-dev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
...ighlight the problem but otherwise behave as if everything was fine.
This is completely untested and may be bash/Linux specific but we could have something like:
defer_fail() {
local exit_code
set +e
"$@"
exit_code=$?
set -e
if [ "$exit_code" != 0 ]; then
SOMETHING_FAILED=1
fi
}
set -e
set -o pipefail
command1 # The script will stop if command1 fails
command2 | command3 # The script will stop if either command2/command3 fails
defer_fail command4 # The script will report an error later if command4 fails but will proceed
defer_fail command5 |...
2015 Jul 22
0
[LLVMdev] [cfe-dev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
On Wed, Jul 22, 2015 at 7:03 AM, Daniel Sanders
<Daniel.Sanders at imgtec.com> wrote:
>> Ben reports that he didn't get a tarball even after the rpath fix and
>> had to disable -o pipefail to get one. Still not sure what caused
>> this.
>
> 'make check' failures can cause this. I had to revert r241599 to get a package.
Oh, I'm silly. Some part of my
2015 Jul 22
3
[LLVMdev] [cfe-dev] [3.7 Release] RC1 has been tagged, Testing Phase I begins
> Ben reports that he didn't get a tarball even after the rpath fix and
> had to disable -o pipefail to get one. Still not sure what caused
> this.
'make check' failures can cause this. I had to revert r241599 to get a package.
> Appendix: compiler-rt test failures
> ===================================
>
Just to add Mips to this: On big-endian Mips32r2: