From: 이형주/MDE Lab(SR)/삼성전자 <leee.lee@samsung.com>
Date: Thu, 14 Nov 2024 05:47:23 +0000 (+0900)
Subject: [Tizen] Bypass GBS build fail for exitcode 143 (#110)
X-Git-Tag: accepted/tizen/unified/x/20241114.135524^0
X-Git-Url: http://review.tizen.org/git/?a=commitdiff_plain;h=refs%2Fheads%2Ftizen_dev;p=platform%2Fcore%2Fdotnet%2Fdiagnostics.git

[Tizen] Bypass GBS build fail for exitcode 143 (#110)

* [Tizen] Bypass GBS build fail for exitcode 143

* [Tizen] Fix typo
---

diff --git a/eng/common/tools.sh b/eng/common/tools.sh
index 618757546..6abe54cff 100644
--- a/eng/common/tools.sh
+++ b/eng/common/tools.sh
@@ -502,7 +502,7 @@ function MSBuild-Core {
   function RunBuildTool {
     export ARCADE_BUILD_TOOL_COMMAND="$_InitializeBuildTool $@"
 
-    "$_InitializeBuildTool" "$@" || {
+    "$_InitializeBuildTool" "$@" || "$_InitializeBuildTool" "$@" || {
       local exit_code=$?
       # We should not Write-PipelineTaskError here because that message shows up in the build summary
       # The build already logged an error, that's the reason it failed. Producing an error here only adds noise.