-
Notifications
You must be signed in to change notification settings - Fork 764
Upgrade Docker container from gcc9 to gcc11 and add gcc9-nopytorch variant #16227
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
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
|
|
@@ -51,7 +51,7 @@ jobs: | |||||
| fail-fast: false | ||||||
| with: | ||||||
| runner: linux.2xlarge | ||||||
| docker-image: ci-image:executorch-ubuntu-22.04-gcc9 | ||||||
| docker-image: ci-image:executorch-ubuntu-22.04-gcc11 | ||||||
| submodules: 'recursive' | ||||||
| ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }} | ||||||
| timeout: 90 | ||||||
|
|
@@ -391,7 +391,7 @@ jobs: | |||||
| fail-fast: false | ||||||
| with: | ||||||
| runner: linux.2xlarge | ||||||
| docker-image: ci-image:executorch-ubuntu-22.04-gcc9 | ||||||
| docker-image: ci-image:executorch-ubuntu-22.04-gcc9-nopytorch | ||||||
| submodules: 'recursive' | ||||||
| ref: ${{ github.event_name == 'pull_request' && github.event.pull_request.head.sha || github.sha }} | ||||||
| timeout: 90 | ||||||
|
|
@@ -400,15 +400,16 @@ jobs: | |||||
| CONDA_ENV=$(conda env list --json | jq -r ".envs | .[-1]") | ||||||
| conda activate "${CONDA_ENV}" | ||||||
|
|
||||||
| ./install_requirements.sh --use-pt-pinned-commit | ||||||
| ./install_requirements.sh | ||||||
| # build module for executorch.extension.pybindings.portable_lib | ||||||
| bash test/build_size_test.sh | ||||||
| strip cmake-out/test/size_test | ||||||
| output=$(ls -la cmake-out/test/size_test) | ||||||
| arr=($output) | ||||||
| size=${arr[4]} | ||||||
| # threshold=48120 on devserver with gcc11.4 | ||||||
| # threshold=48120 on devserver with gcc9 | ||||||
| # todo(lfq): update once binary size is below 50kb. | ||||||
| # Note: using gcc9-nopytorch container with pinned nightly PyTorch | ||||||
|
||||||
| # Note: using gcc9-nopytorch container with pinned nightly PyTorch | |
| # Note: using gcc9-nopytorch container with nightly PyTorch |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The timeout has been increased from 45 to 145 minutes (over 3x increase). This seems excessive. Building the gcc9-nopytorch container should actually be faster than building the gcc11 container since it skips PyTorch installation. Consider using a more reasonable timeout value (e.g., 60-90 minutes) unless there's a specific reason for this large increase.