Skip to content

Commit

Permalink
chore: update lean-pr-testing reporting logic, now that the linter al…
Browse files Browse the repository at this point in the history
…ways runs (#12202)

As reported [elsewhere](leanprover/lean4#3808 (comment)).

Co-authored-by: Scott Morrison <[email protected]>
  • Loading branch information
kim-em and kim-em committed Apr 18, 2024
1 parent a4c2a1e commit 071b2ee
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions scripts/lean-pr-testing-comments.sh
Original file line number Diff line number Diff line change
Expand Up @@ -83,6 +83,8 @@ if [[ "$branch_name" =~ ^lean-pr-testing-([0-9]+)$ ]]; then
message="- 🟡 Mathlib branch $branch build against this PR was cancelled. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$CHECK_OUTCOME" == "success" ]; then
message="- ✅ Mathlib branch $branch has successfully built against this PR. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$BUILD_OUTCOME" == "failure" ] ; then
message="- 💥 Mathlib branch $branch build failed against this PR. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$CHECK_OUTCOME" == "failure" ]; then
message="- ❌ Mathlib branch $branch built against this PR, but lean4checker failed. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$LINT_OUTCOME" == "failure" ]; then
Expand All @@ -95,8 +97,6 @@ if [[ "$branch_name" =~ ^lean-pr-testing-([0-9]+)$ ]]; then
message="- ❌ Mathlib branch $branch built against this PR, but was unexpectedly noisy. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$TEST_OUTCOME" == "failure" ]; then
message="- ❌ Mathlib branch $branch built against this PR, but testing failed. ($current_time) [View Log]($WORKFLOW_URL)"
elif [ "$BUILD_OUTCOME" == "failure" ] ; then
message="- 💥 Mathlib branch $branch build failed against this PR. ($current_time) [View Log]($WORKFLOW_URL)"
else
message="- 🟡 Mathlib branch $branch build this PR didn't complete normally. ($current_time) [View Log]($WORKFLOW_URL)"
fi
Expand Down

0 comments on commit 071b2ee

Please sign in to comment.