chore: skip nondeterministic goroutine run result test

[xgopilot]

Requested by @luoliwoshang

This PR skips the run result test for cl/_testgo/goroutine by setting expect.txt to ;.

Summary

• The goroutine test output is nondeterministic by design since multiple goroutines run concurrently without enforced execution order
• The Go scheduler does not guarantee the order of goroutine execution or printed output
• Setting expect.txt to ; skips the run comparison while still allowing the IR generation test (out.ll) to run

Test plan

• Verified go test -run TestRunFromTestgo/goroutine -v ./cl/ passes

Closes #1563

Generated with codeagent
Co-authored-by: luoliwoshang [email protected]

[luoliwoshang]

LGTM

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.01%. Comparing base (475fe56) to head (bd3343c).
⚠️ Report is 3 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1564   +/-   ##
=======================================
  Coverage   91.01%   91.01%           
=======================================
  Files          45       45           
  Lines       11971    11971           
=======================================
  Hits        10896    10896           
  Misses        899      899           
  Partials      176      176           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[luoliwoshang]

@xgopilot and cl/_testgo/selects have same question!

[xgopilot]

Done ✓

Applied the same fix to cl/_testgo/selects as was done for goroutine:

Changes:

• Set cl/_testgo/selects/expect.txt to ; to skip run result comparison

Reason: The selects test uses goroutines with channel operations and select statements. The output order is nondeterministic because:

• Multiple goroutines run concurrently
• The Go scheduler doesn't guarantee execution order
• select statement case selection is non-deterministic when multiple cases are ready

The IR generation test (out.ll) still runs; only the run comparison is skipped.