Skip to content

Add YTS test support#817

Open
isarkis wants to merge 10 commits intomainfrom
feature/yts_tests
Open

Add YTS test support#817
isarkis wants to merge 10 commits intomainfrom
feature/yts_tests

Conversation

@isarkis
Copy link
Copy Markdown
Member

@isarkis isarkis commented Dec 3, 2025

Issue: 454941148

Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request adds support for YTS tests by introducing a new GitHub composite action and updating the Android ARM configuration. The changes in the configuration file look correct. However, the new GitHub action in .github/actions/yts_tests/action.yaml appears to have some copy-paste errors from an E2E test action. It's incorrectly configured to run E2E tests instead of YTS tests, which would cause it to fail. I've left specific comments with suggestions to fix these issues.

--token ${GITHUB_TOKEN} \
trigger \
--test_type ${TEST_TYPE} \
--targets '${{ inputs.e2e_test_targets }}' \
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

critical

The --targets argument is using inputs.e2e_test_targets, but this input is not defined for this action. This will cause the action to fail. It should use inputs.yts_test_targets.

          --targets '${{ inputs.yts_test_targets }}' \

GITHUB_RUN_NUMBER: ${{ github.run_number }}
GITHUB_RUN_URL: ${{ github.server_url }}/${{ github.repository }}/actions/runs/${{ github.run_id }}
GITHUB_WORKFLOW: ${{ github.workflow }}
TEST_TYPE: e2e_test
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

high

This action is for YTS tests, but TEST_TYPE is hardcoded to e2e_test. This should be yts_test to correctly categorize and run the tests.

        TEST_TYPE: yts_test

description: "Test dimensions JSON string."
required: true
yts_test_targets:
description: "E2E test targets."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

The description for the yts_test_targets input is 'E2E test targets.', which is misleading for an action that runs YTS tests. It should be updated for clarity.

    description: "YTS test targets."

--label author_id-${GITHUB_PR_HEAD_USER_ID:-$GITHUB_COMMIT_AUTHOR_EMAIL} \
--dimensions '${{ inputs.test_dimensions }}' \
--cobalt_path "${GCS_ARTIFACTS_PATH}" || {
echo "Finished running tests..."
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

medium

This echo statement inside the failure block is confusing. The same message 'Finished running tests...' is also printed on success (line 84). This can make it harder to quickly identify a failure from the logs. I'd recommend removing this line from the failure block to avoid ambiguity.

test_device_family=$(cat ${GITHUB_WORKSPACE}/.github/config/${{ inputs.platform }}.json | jq -rc '.test_device_family // empty')
echo "test_device_family=${test_device_family}" >> $GITHUB_OUTPUT
- name: Set YTS test targets
id: set-e2e-test-targets
Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Shouldn't this be set-yts-test-targets ? set-e2e-test-targets is an id in l.180 (no idea how this works tho :)

@Libzu Libzu force-pushed the feature/yts_tests branch 8 times, most recently from 6e5d325 to e5f6892 Compare December 6, 2025 02:33
config: [devel]
steps:
- name: Checkout
uses: actions/checkout@v4

Check warning

Code scanning / Scorecard

Pinned-Dependencies Medium

score is 0: GitHub-owned GitHubAction not pinned by hash
Remediation tip: update your workflow using https://app.stepsecurity.io
Click Remediation section below for further remediation help
isarkis and others added 2 commits December 9, 2025 18:11
@Libzu Libzu force-pushed the feature/yts_tests branch from ba05872 to cf09978 Compare December 9, 2025 18:14
@Libzu Libzu force-pushed the feature/yts_tests branch from cf09978 to c69cb91 Compare December 9, 2025 18:17
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.

4 participants