Skip to content

Conversation

cccclai
Copy link
Contributor

@cccclai cccclai commented Sep 12, 2025

As title. xrefs will hang if the files change too much, however it's a bit hard to tell. Make file size check explicit. The rule is following

  1. For all files, the file size can't be larger than 1MB
  2. For images/vidoes, the files size can't be larger than 7MB
  3. There is an exception list defined in the script if it's really needed

Copy link

pytorch-bot bot commented Sep 12, 2025

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/14274

Note: Links to docs will display an error until the docs builds have been completed.

⏳ No Failures, 106 Pending

As of commit 4d3f622 with merge base 30a904b (image):
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Sep 12, 2025
@cccclai cccclai marked this pull request as draft September 12, 2025 19:04
@zingo
Copy link
Collaborator

zingo commented Sep 13, 2025

Might be nice to have this check in lintrunner also down the line.

@cccclai
Copy link
Contributor Author

cccclai commented Sep 15, 2025

Might be nice to have this check in lintrunner also down the line.

I think this check each file already. What does it mean by down the line?

@cccclai cccclai marked this pull request as ready for review September 15, 2025 21:32
Copy link
Contributor

@swolchok swolchok left a comment

Choose a reason for hiding this comment

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

minor quibbles but directionally this is fine

runner: linux.2xlarge
docker-image: ci-image:executorch-ubuntu-22.04-linter
submodules: false
fetch-depth: 0
Copy link
Contributor

Choose a reason for hiding this comment

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

IIRC 0 is unlimited. couldn't we make this some large (because it gates the maximum depth of a stack) but finite number, like say 50?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

I tried look up fetch-depth in both executorch and pytorch, and looks like all are defined as 0 or 1...I can't find definition for this variable so using the same as other jobs to be safe

if: ${{ github.event_name == 'pull_request' }}
uses: pytorch/test-infra/.github/workflows/linux_job_v2.yml@main
with:
runner: linux.2xlarge
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 have smaller runners we can use? this isn't particularly resource-intensive

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Tried linux.large and docker image pulling failed. Bump it to 2x

@swolchok swolchok added the release notes: none Do not include this in the release notes label Sep 16, 2025
@cccclai cccclai merged commit 720aea5 into main Sep 16, 2025
124 checks passed
@cccclai cccclai deleted the lint_file_size branch September 16, 2025 22:51
StrycekSimon pushed a commit to nxp-upstream/executorch that referenced this pull request Sep 23, 2025
As title. xrefs will hang if the files change too much, however it's a
bit hard to tell. Make file size check explicit. The rule is following
1. For all files, the file size can't be larger than 1MB
2. For images/vidoes, the files size can't be larger than 7MB
3. There is an exception list defined in the script if it's really
needed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants