Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[CI] UT logs post op and artifact #671

Closed
wants to merge 24 commits into from
Closed

Conversation

RUIJIEZHONG66166
Copy link
Contributor

No description provided.

@@ -28,6 +28,12 @@ on:
type: string
default: 'linux.idc.xpu'
description: Runner label
expected_fail_num:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we really need this parameter?

- name: UT Test Results Check
if: ${{ inputs.expected_fail_num }}
shell: bash
run: |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we abstract this step as a script and put it into .github/scripts? and in this step, we not only check the test pass or not, but also show the failure cases and logs directly

- name: Upload Inductor XPU UT Data
uses: actions/upload-artifact@v4
with:
name: Inductor-XPU-UT-Data-${{ github.event.pull_request.number || github.sha }}
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Change the name to Torch-XPU-UT-Log-xxx. And we can move the upload step after the result check step with if: always()

@@ -120,7 +122,7 @@ jobs:
if [[ "$xpu_case" != *"*"* && "$xpu_case" != *.so && "$xpu_case" != *.a ]]; then
case_name=$(basename "$xpu_case")
echo "Testing ${case_name} ..."
"$xpu_case" --gtest_output=xml:"$TEST_REPORTS_DIR"/"$case_name".xml
"$xpu_case" --gtest_output=xml:"$TEST_REPORTS_DIR"/"$case_name".xml 2>&1 | tee ${{ github.workspace }}/ut_log/binary_UT_${ut_suite}_${case_name}_Test.log
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

add one more folder under ut_log, for example ut_log/binary_ut/${case_name}...log

@@ -142,3 +144,31 @@ jobs:
test_cmd="${test_cmd} test_xpu.py"
fi
eval $test_cmd
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

How about inductor test logs? will we upload those logs too? Seems the pytorch ut test log under ./test/test-reports/ by default

$contains_status
cd ${{ github.workspace }}/ut_log
bash ut_result_check.sh ${ut_suite}
done
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Better to add a space line at the end of file

@chuanqi129
Copy link
Contributor

build failure need rebase the code to the latest main

@fengyuan14
Copy link
Contributor

Please wait for preci fixing.

@xytintel xytintel marked this pull request as draft October 25, 2024 04:33
@chuanqi129
Copy link
Contributor

@RUIJIEZHONG66166 Can we transfer the status of this PR to ready for review? And can this PR address the issue #1166?

@chuanqi129 chuanqi129 changed the title UT log save and analysis [CI] UT logs post op and artifact Dec 16, 2024
@RUIJIEZHONG66166 RUIJIEZHONG66166 deleted the ruijie/update_ut_log branch December 19, 2024 05:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants