jinx/python-uncompyle6
1
Fork 0
mirror of https://github.com/rocky/python-uncompyle6.git synced 2025-08-02 16:44:46 +08:00
Code Issues Packages Projects Releases Wiki Activity

Update build to large resource class in config.yml

Browse Source
This commit is contained in:
R. Bernstein
2023-06-30 16:34:55 -04:00
parent 4b296e1ead
commit 3f21b2a115
1 changed files with 57 additions and 54 deletions
Download Patch File Download Diff File Expand all files Collapse all files

111
.circleci/config.yml
View File

@@ -18,60 +18,63 @@ jobs:
docker: docker:
- image: circleci/python:3.6.9 - image: circleci/python:3.6.9
steps: steps:
# Machine Setup # Machine Setup
# If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each # If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each
# The following `checkout` command checks out your code to your working directory. In 1.0 we did this implicitly. In 2.0 you can choose where in the course of a job your code should be checked out. # The following `checkout` command checks out your code to your working directory. In 1.0 we did this implicitly. In 2.0 you can choose where in the course of a job your code should be checked out.
- checkout - checkout
# Prepare for artifact and test results collection equivalent to how it was done on 1.0. # Prepare for artifact and test results collection equivalent to how it was done on 1.0.
# In many cases you can simplify this from what is generated here. # In many cases you can simplify this from what is generated here.
# 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/' # 'See docs on artifact collection here https://circleci.com/docs/2.0/artifacts/'
- run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS - run: mkdir -p $CIRCLE_ARTIFACTS $CIRCLE_TEST_REPORTS
# This is based on your 1.0 configuration file or project settings # This is based on your 1.0 configuration file or project settings
- run: - run:
working_directory: ~/rocky/python-uncompyle6 working_directory: ~/rocky/python-uncompyle6
command: pip install --user virtualenv && pip install --user nose && pip install --user pep8 command: pip install --user virtualenv && pip install --user nose && pip install
# Dependencies --user pep8
# This would typically go in either a build or a build-and-test job when using workflows # Dependencies
# Restore the dependency cache # This would typically go in either a build or a build-and-test job when using workflows
- restore_cache: # Restore the dependency cache
keys: - restore_cache:
- v2-dependencies-{{ .Branch }}- keys:
# fallback to using the latest cache if no exact match is found - v2-dependencies-{{ .Branch }}-
- v2-dependencies- # fallback to using the latest cache if no exact match is found
- v2-dependencies-
- run: - run:
command: | # Use pip to install dependengcies command: | # Use pip to install dependengcies
pip install --user --upgrade setuptools pip install --user --upgrade setuptools
# Until the next release # Until the next release
pip install git+https://github.com/rocky/python-xdis#egg=xdis pip install git+https://github.com/rocky/python-xdis#egg=xdis
pip install --user -e . pip install --user -e .
pip install --user -r requirements-dev.txt pip install --user -r requirements-dev.txt
# Save dependency cache # Save dependency cache
- save_cache: - save_cache:
key: v2-dependencies-{{ .Branch }}-{{ epoch }} key: v2-dependencies-{{ .Branch }}-{{ epoch }}
paths: paths:
# This is a broad list of cache paths to include many possible development environments # This is a broad list of cache paths to include many possible development environments
# You can probably delete some of these entries # You can probably delete some of these entries
- vendor/bundle - vendor/bundle
- ~/virtualenvs - ~/virtualenvs
- ~/.m2 - ~/.m2
- ~/.ivy2 - ~/.ivy2
- ~/.bundle - ~/.bundle
- ~/.cache/bower - ~/.cache/bower
# Test # Test
# This would typically be a build job when using workflows, possibly combined with build # This would typically be a build job when using workflows, possibly combined with build
# This is based on your 1.0 configuration file or project settings # This is based on your 1.0 configuration file or project settings
- run: sudo python ./setup.py develop && make check-3.6 - run: sudo python ./setup.py develop && make check-3.6
- run: cd ./test/stdlib && bash ./runtests.sh 'test_[p-z]*.py' - run: cd ./test/stdlib && bash ./runtests.sh 'test_[p-z]*.py'
# Teardown # Teardown
# If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each # If you break your build into multiple jobs with workflows, you will probably want to do the parts of this that are relevant in each
# Save test results # Save test results
- store_test_results: - store_test_results:
path: /tmp/circleci-test-results path: /tmp/circleci-test-results
# Save artifacts # Save artifacts
- store_artifacts: - store_artifacts:
path: /tmp/circleci-artifacts path: /tmp/circleci-artifacts
- store_artifacts: - store_artifacts:
path: /tmp/circleci-test-results path: /tmp/circleci-test-results
# The resource_class feature allows configuring CPU and RAM resources for each job. Different resource classes are available for different executors. https://circleci.com/docs/2.0/configuration-reference/#resourceclass
resource_class: large