Some Merged Tests Will Never Fail or Pass Correctly Due to a Void Return Value

[ivdiazsa]

While browsing some tests in the src/tests subtree, I found out some tests have their TestEntryPoint() method defined as void type. Consequently, the merged test's respective script will never know how the test truly went since it requires a return value.

For example, the way the script defines whether the test passed or not is with the following code:

{ ... }

export CLRTestExpectedExitCode=100

{ ... }

if [ $CLRTestExitCode -ne $CLRTestExpectedExitCode ]
then
  echo END EXECUTION - FAILED
  exit 1
else
  echo END EXECUTION - PASSED
  exit 0
fi

The script expects a 100 return code upon success, so the test would need to return an int type value.

[ghost]

Tagging subscribers to this area: @hoyosjs
See info in area-owners.md if you want to be subscribed.

Issue Details

---

While browsing some tests in the src/tests subtree, I found out some tests have their TestEntryPoint() method defined as void type. Consequently, the merged test's respective script will never know how the test truly went since it requires a return value.

For example, the way the script defines whether the test passed or not is with the following code:

{ ... }

export CLRTestExpectedExitCode=100

{ ... }

if [ $CLRTestExitCode -ne $CLRTestExpectedExitCode ]
then
  echo END EXECUTION - FAILED
  exit 1
else
  echo END EXECUTION - PASSED
  exit 0
fi

The script expects a 100 return code upon success, so the test would need to return an int type value.

Author:	ivdiazsa
Assignees:	ivdiazsa
Labels:	area-Infrastructure-coreclr
Milestone:	9.0.0

[ivdiazsa]

There is a system that handles void return tests appropriately now, so closing this issue.