alex/esp-idf
alex/esp-idf
1
0
Fork 0
mirror of https://github.com/espressif/esp-idf.git synced 2024-10-05 20:47:46 -04:00
Code Issues Actions 2 Packages Projects Releases Wiki Activity
release/v3.1
esp-idf/.gitlab-ci.yml

1454 lines
33 KiB
YAML
Raw Permalink Normal View History

gitlab-ci: push master to GitHub master on success
2016-08-22 06:19:08 -04:00
stages:
- build
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
- assign_test
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
- host_test
ci: combine unit_test and integration_test stage: The number of runners of integration test is not bottleneck to CI pipeline performance now. Combine these 2 stages will make integration test executed even unit test fails. This could help us to collect more info about test history.
2018-11-26 03:40:32 -05:00
- target_test
gitlab-ci: push master to GitHub master on success
2016-08-22 06:19:08 -04:00
- deploy
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
- post_check
gitlab-ci: push master to GitHub master on success
2016-08-22 06:19:08 -04:00
CI: Assign a common variable
2017-06-06 21:58:35 -04:00
variables:
CI: Add CI options to use more attempts in some transfer situations
2017-06-12 03:22:09 -04:00
# System environment
CI: Use the environment variable MAKEFLAGS for 'make' instead of the in-place '-j' option.
2017-06-07 03:42:36 -04:00
# Common parameters for the 'make' during CI tests
MAKEFLAGS: "-j5 --no-keep-going"
CI: Add CI options to use more attempts in some transfer situations
2017-06-12 03:22:09 -04:00
# GitLab-CI environment
# more attempts for more robust
GET_SOURCES_ATTEMPTS: "10"
ARTIFACT_DOWNLOAD_ATTEMPTS: "10"
ci: Fix the parsing of submodule paths
2019-03-06 06:37:34 -05:00
# We use get-full-sources.sh script to fetch the submodules and/or re-fetch the repo
CI: Use custom get_full_sources.sh script instead of gitlab-ci's strategies Work around problems caused by failed submodule clones corrupting the working directory on the build runner. Add 10 retries for cloning submodules.
2017-06-14 03:52:33 -04:00
# if it was corrupted (if submodule update fails this can happen)
GIT_STRATEGY: fetch
GIT_SUBMODULE_STRATEGY: none
CI: Use the environment variable MAKEFLAGS for 'make' instead of the in-place '-j' option.
2017-06-07 03:42:36 -04:00
# IDF environment
CI: Add CI options to use more attempts in some transfer situations
2017-06-12 03:22:09 -04:00
CI: Assign a common variable
2017-06-06 21:58:35 -04:00
IDF_PATH: "$CI_PROJECT_DIR"
build: Fix problems with building kconfig and generating sdkconfig We had some problems: simultaneous compiling of kconfig in the same tree; attempt to use menuconfig in some examples and ut in batch mode (w/o interactive console) Also increase debug abilities in CI: force non-interactive building; add variable DEBUG_SHELL to toggle verbosity of scripts
2018-03-27 01:13:35 -04:00
BATCH_BUILD: "1"
V: "0"
CI: support customize test with @bot
2017-10-18 07:53:10 -04:00
APPLY_BOT_FILTER_SCRIPT: "$CI_PROJECT_DIR/tools/ci/apply_bot_filter.py"
CHECKOUT_REF_SCRIPT: "$CI_PROJECT_DIR/tools/ci/checkout_project_ref.py"
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
# Docker images
BOT_DOCKER_IMAGE_TAG: ":latest"
# target test repo parameters
TEST_ENV_CONFIG_REPO: "${GITLAB_SSH_SERVER}/qa/ci-test-runner-configs.git"
CI_AUTO_TEST_SCRIPT_REPO_URL: "${GITLAB_SSH_SERVER}/qa/auto_test_script.git"
CI_AUTO_TEST_SCRIPT_REPO_BRANCH: "ci/v3.1"
ci: remove stale submodules after checkout When ‘fetch’ strategy is used, Gitlab removes untracked files before checking out new revision. However if the new revision doesn’t include some of the submodules which were present in the old revision, such submodule directories would not be removed by the checkout. This extra step ensures that these stale submodules are removed.
2018-06-08 07:41:18 -04:00
# When 'fetch' strategy is used, Gitlab removes untracked files before checking out
# new revision. However if the new revision doesn't include some of the submodules
# which were present in the old revision, such submodule directories would not be
# removed by the checkout. This extra step ensures that these stale submodules
# are removed.
.git_clean_stale_submodules: &git_clean_stale_submodules >
find . -name '.git' -not -path './.git' -printf '%P\n'
| sed 's|/.git||'
| xargs -I {} sh -c '
grep -q {} .gitmodules
|| (echo "Removing {}, has .git directory but not in .gitmodules file"
&& rm -rf {});'
CI: support customize test with @bot
2017-10-18 07:53:10 -04:00
# before each job, we need to check if this job is filtered by bot stage/job filter
.apply_bot_filter: &apply_bot_filter
python $APPLY_BOT_FILTER_SCRIPT || exit 0
CI: Assign a common variable
2017-06-06 21:58:35 -04:00
gitlab-ci: update submodules before build Gitlab CI will cache build directory per branch and per build step. Also it doesn't try to update submodules. We have to do this manually because otherwise we end up with old version of submodule in cached directory.
2016-09-01 03:13:15 -04:00
before_script:
CI: Support switching between various versions of Python
2018-09-25 08:43:07 -04:00
- source tools/ci/setup_python.sh
ci: remove stale submodules after checkout When ‘fetch’ strategy is used, Gitlab removes untracked files before checking out new revision. However if the new revision doesn’t include some of the submodules which were present in the old revision, such submodule directories would not be removed by the checkout. This extra step ensures that these stale submodules are removed.
2018-06-08 07:41:18 -04:00
- *git_clean_stale_submodules
CI: support customize test with @bot
2017-10-18 07:53:10 -04:00
# apply bot filter in before script
- *apply_bot_filter
ci: Use github repo for wifi libraries on master branch, gitlab repo otherwise
2016-09-12 21:34:28 -04:00
# add gitlab ssh key
- mkdir -p ~/.ssh
- chmod 700 ~/.ssh
gitlab-ci: fix setting GitHub deploy key - don't run default before_script before push_master_to_github job - replace echo >> with echo > to avoid mistakes in the future
2016-09-13 09:24:57 -04:00
- echo -n $GITLAB_KEY > ~/.ssh/id_rsa_base64
ci: Use github repo for wifi libraries on master branch, gitlab repo otherwise
2016-09-12 21:34:28 -04:00
- base64 --decode --ignore-garbage ~/.ssh/id_rsa_base64 > ~/.ssh/id_rsa
- chmod 600 ~/.ssh/id_rsa
- echo -e "Host gitlab.espressif.cn\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config
Revert "Merge branch 'feature/ci_checkout_same_branch_for_submodule' into 'master'" This reverts merge request !178
2016-11-07 22:55:48 -05:00
ci: Swap github/gitlab submodules for release branches & tags also
2017-03-22 06:39:28 -04:00
# Set IS_PRIVATE or IS_PUBLIC depending on if our branch is public or not
#
# (the same regular expressions are used to set these are used in 'only:' sections below
CI: Move the ci-related staff to a separate directory
2017-06-16 00:38:32 -04:00
- source tools/ci/configure_ci_environment.sh
ci: Swap github/gitlab submodules for release branches & tags also
2017-03-22 06:39:28 -04:00
CI: Use custom get_full_sources.sh script instead of gitlab-ci's strategies Work around problems caused by failed submodule clones corrupting the working directory on the build runner. Add 10 retries for cloning submodules.
2017-06-14 03:52:33 -04:00
# fetch the submodules (& if necessary re-fetch repo) from gitlab
- time ./tools/ci/get-full-sources.sh
gitlab-ci: update submodules before build Gitlab CI will cache build directory per branch and per build step. Also it doesn't try to update submodules. We have to do this manually because otherwise we end up with old version of submodule in cached directory.
2016-09-01 03:13:15 -04:00
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
.do_nothing_before:
before_script: &do_nothing_before
CI: Support switching between various versions of Python
2018-09-25 08:43:07 -04:00
- source tools/ci/setup_python.sh
ci: remove stale submodules after checkout When ‘fetch’ strategy is used, Gitlab removes untracked files before checking out new revision. However if the new revision doesn’t include some of the submodules which were present in the old revision, such submodule directories would not be removed by the checkout. This extra step ensures that these stale submodules are removed.
2018-06-08 07:41:18 -04:00
- *git_clean_stale_submodules
CI: support customize test with @bot
2017-10-18 07:53:10 -04:00
# apply bot filter in before script
- *apply_bot_filter
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
- echo "Not setting up GitLab key, not fetching submodules"
- source tools/ci/configure_ci_environment.sh
.add_gitlab_key_before:
before_script: &add_gitlab_key_before
CI: Support switching between various versions of Python
2018-09-25 08:43:07 -04:00
- source tools/ci/setup_python.sh
ci: remove stale submodules after checkout When ‘fetch’ strategy is used, Gitlab removes untracked files before checking out new revision. However if the new revision doesn’t include some of the submodules which were present in the old revision, such submodule directories would not be removed by the checkout. This extra step ensures that these stale submodules are removed.
2018-06-08 07:41:18 -04:00
- *git_clean_stale_submodules
CI: support customize test with @bot
2017-10-18 07:53:10 -04:00
# apply bot filter in before script
- *apply_bot_filter
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
- echo "Not fetching submodules"
- source tools/ci/configure_ci_environment.sh
# add gitlab ssh key
- mkdir -p ~/.ssh
- chmod 700 ~/.ssh
- echo -n $GITLAB_KEY > ~/.ssh/id_rsa_base64
- base64 --decode --ignore-garbage ~/.ssh/id_rsa_base64 > ~/.ssh/id_rsa
- chmod 600 ~/.ssh/id_rsa
- echo -e "Host gitlab.espressif.cn\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
# for parallel jobs, CI_JOB_NAME will be "job_name index/total" (for example, "IT_001 1/2")
# we need to convert to pattern "job_name_index.yml"
.define_config_file_name: &define_config_file_name |
JOB_NAME_PREFIX=$(echo ${CI_JOB_NAME} | awk '{print $1}')
JOB_FULL_NAME="${JOB_NAME_PREFIX}_${CI_NODE_INDEX}"
CONFIG_FILE="${CONFIG_FILE_PATH}/${JOB_FULL_NAME}.yml"
gitlab-ci: initial version This change adds gitlab CI support. It tests if latest master of esp-idf-template can be built with the commit of ESP-IDF in question. Currently it's a bit lax because both SDK_PATH and IDF_PATH are defined. This change also changes components/esp32/lib submodule to point to Github over HTTPS instead of SSH, because CI server might not have its SSH keys uploaded to Github.
2016-08-22 03:02:22 -04:00
build_template_app:
gitlab-ci: push master to GitHub master on success
2016-08-22 06:19:08 -04:00
stage: build
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
tags:
- build
gitlab-ci: initial version This change adds gitlab CI support. It tests if latest master of esp-idf-template can be built with the commit of ESP-IDF in question. Currently it's a bit lax because both SDK_PATH and IDF_PATH are defined. This change also changes components/esp32/lib submodule to point to Github over HTTPS instead of SSH, because CI server might not have its SSH keys uploaded to Github.
2016-08-22 03:02:22 -04:00
variables:
Build system: Add new BATCH_BUILD flag to disable interactive parts of the build Mostly useful for Eclipse (where accidentally running interactive config hangs the build), but also good for CI and other automated build systems.
2017-02-10 01:38:24 -05:00
BATCH_BUILD: "1"
AWS IoT Device SDK Support Use device cert/key embedded in firmware, or loaded from filesystem.
2016-10-05 01:32:09 -04:00
IDF_CI_BUILD: "1"
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_REGULAR_TEST
gitlab-ci: initial version This change adds gitlab CI support. It tests if latest master of esp-idf-template can be built with the commit of ESP-IDF in question. Currently it's a bit lax because both SDK_PATH and IDF_PATH are defined. This change also changes components/esp32/lib submodule to point to Github over HTTPS instead of SSH, because CI server might not have its SSH keys uploaded to Github.
2016-08-22 03:02:22 -04:00
script:
ci: If there is no sdkconfig, we have to generate one
2018-11-14 01:13:28 -05:00
# Set the variable for 'esp-idf-template' testing
- ESP_IDF_TEMPLATE_GIT=${ESP_IDF_TEMPLATE_GIT:-"https://github.com/espressif/esp-idf-template.git"}
- git clone ${ESP_IDF_TEMPLATE_GIT}
CI: Build the esp-idf-template with the matching branch name, if it exists
2016-09-01 04:58:06 -04:00
# Try to use the same branch name for esp-idf-template that we're
# using on esp-idf. If it doesn't exist then just stick to the default
# branch
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT esp-idf-template esp-idf-template
- cd esp-idf-template
ci: If there is no sdkconfig, we have to generate one
2018-11-14 01:13:28 -05:00
- make defconfig
Add test for compiling in release mode, fix warnings and errors which appeared
2016-10-17 00:45:42 -04:00
# Test debug build (default)
- make all V=1
# Now test release build
- make clean
- sed -i.bak -e's/CONFIG_OPTIMIZATION_LEVEL_DEBUG\=y/CONFIG_OPTIMIZATION_LEVEL_RELEASE=y/' sdkconfig
make debugging: With V=1, output when including each Makefile.projbuild also enable V=1 on CI builds
2016-09-08 20:49:35 -04:00
- make all V=1
implement esp_deep_sleep, fix build issues
2016-11-21 10:05:23 -05:00
# Check if there are any stray printf/ets_printf references in WiFi libs
- cd ../components/esp32/lib
component/esp32 : clear some minor thingsw about PM and coexistence
2018-04-03 03:37:28 -04:00
- test $(xtensa-esp32-elf-nm *.a | grep -w printf | wc -l) -eq 0
- test $(xtensa-esp32-elf-nm *.a | grep -w ets_printf | wc -l) -eq 0
gitlab-ci: push master to GitHub master on success
2016-08-22 06:19:08 -04:00
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
ci: Reorder the clauses for more convenience
2017-04-26 06:09:14 -04:00
.build_template: &build_template
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
stage: build
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
tags:
- build
variables:
Build system: Add new BATCH_BUILD flag to disable interactive parts of the build Mostly useful for Eclipse (where accidentally running interactive config hangs the build), but also good for CI and other automated build systems.
2017-02-10 01:38:24 -05:00
BATCH_BUILD: "1"
ci: Build with V=0 BATCH_BUILD implies V=1, but SSC produces a *lot* of log output in verbose mode. For now, disable setting V=1 for all CI build modes.
2017-04-19 23:43:20 -04:00
V: "0"
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
CI: support build SSC in multiple jobs
2017-11-30 23:00:40 -05:00
.build_ssc_template: &build_ssc_template
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
<<: *build_template
artifacts:
paths:
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
- SSC/ssc_bin
CI: support build SSC in multiple jobs
2017-11-30 23:00:40 -05:00
expire_in: 1 mos
variables:
SSC_CONFIG_FOLDER: "$CI_PROJECT_DIR/SSC/configs/ESP32_IDF"
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_INTEGRATION_TEST
- $BOT_LABEL_REGULAR_TEST
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
script:
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
- git clone $SSC_REPOSITORY
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT SSC SSC
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
- cd SSC
CI: support build SSC in multiple jobs
2017-11-30 23:00:40 -05:00
- MAKEFLAGS= ./ci_build_ssc.sh "${CI_JOB_NAME}" "${IDF_PATH}/.gitlab-ci.yml"
# don't forget to add to dependency to test_template when adding new build_ssc jobs
build_ssc_00:
<<: *build_ssc_template
build_ssc_01:
<<: *build_ssc_template
build_ssc_02:
<<: *build_ssc_template
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
# If you want to add new build ssc jobs, please add it into dependencies of `assign_test` and `.test_template`
integrate unit test to CI
2016-11-01 07:30:42 -04:00
build_esp_idf_tests:
<<: *build_template
artifacts:
paths:
unit-test-app: new targets for building different configurations
2017-09-12 13:40:54 -04:00
- tools/unit-test-app/output
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
- components/idf_test/unit_test/TestCaseAll.yml
- components/idf_test/unit_test/CIConfigs/*.yml
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
expire_in: 1 mos
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_UNIT_TEST
- $BOT_LABEL_REGULAR_TEST
integrate unit test to CI
2016-11-01 07:30:42 -04:00
script:
add unit tests to esp-idf rename nvs host test folder, modify .gitlab-ci.yml remove unit-test-app build re-format unit test files remove extra newlines in project.mk some refactoring for unit test part in project.mk add build files of unit-test-app in gitignore add README.md for unit test app correct headings in README.md remove files and make minor tweaks in unit test app update .gitlab-ci.yml to use unit test app delete unused lines in component_wrapper.mk delete periph_i2s.h and lcd test add text floating point in components/esp32/test/Kconfig correct idf test build paths in .gitlab-ci.yml
2016-11-17 03:36:10 -05:00
- cd tools/unit-test-app
unit-test-app: allow specifying subset of tests for configuration For some test configurations, not all tests need to be run. This change allows adding a comment in the configuration file of the following form: unit-test-app makefile will use it to determine which components to build. If the comment is not present, all components will be built (TESTS_ALL=1). Also add test configuration for libsodium. It is a separate test configuration due to the large binary size generated when building libsodium tests.
2018-04-28 06:56:25 -04:00
- MAKEFLAGS= make help # make sure kconfig tools are built in single process
unit-test-app: new targets for building different configurations
2017-09-12 13:40:54 -04:00
- make ut-clean-all-configs
unit tests: fix warnings, build with -Werror - libsodium: silence warnings - unit tests: fix warnings - spiram: fix warnings - ringbuf test: enable by default, reduce delays
2017-10-18 09:09:53 -04:00
- export EXTRA_CFLAGS="-Werror -Werror=deprecated-declarations"
- export EXTRA_CXXFLAGS=${EXTRA_CFLAGS}
unit-test-app: allow specifying subset of tests for configuration For some test configurations, not all tests need to be run. This change allows adding a comment in the configuration file of the following form: unit-test-app makefile will use it to determine which components to build. If the comment is not present, all components will be built (TESTS_ALL=1). Also add test configuration for libsodium. It is a separate test configuration due to the large binary size generated when building libsodium tests.
2018-04-28 06:56:25 -04:00
- make ut-build-all-configs
CI: revise unit test parser
2017-03-24 06:38:06 -04:00
- python tools/UnitTestParser.py
integrate unit test to CI
2016-11-01 07:30:42 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
.build_examples_make_template: &build_examples_make_template
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
<<: *build_template
CI: Try to build examples in second time in case of error It will help to work around the weird bug during buillding a batch of examples
2018-04-04 03:37:28 -04:00
retry: 1
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
artifacts:
CI: Fix a sporadic bug when building of the examples. Add logs to the artifacts
2017-12-28 05:20:14 -05:00
when: always
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
paths:
CI: Fix incorrect path to the artifacts in build_examples
2017-06-05 02:39:11 -04:00
- build_examples/*/*/*/build/*.bin
- build_examples/*/*/*/build/*.elf
- build_examples/*/*/*/build/*.map
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
- build_examples/*/*/*/build/download.config
CI: Fix incorrect path to the artifacts in build_examples
2017-06-05 02:39:11 -04:00
- build_examples/*/*/*/build/bootloader/*.bin
CI: Fix a sporadic bug when building of the examples. Add logs to the artifacts
2017-12-28 05:20:14 -05:00
- $LOG_PATH
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
expire_in: 1 week
CI: Fix build_examples to cover the deep hierarchy examples Now we have 57 building examples against 49 before. Also, a short message prints at the end of the job for found warnings.
2017-06-06 06:26:31 -04:00
variables:
IDF_CI_BUILD: "1"
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
LOG_PATH: "$CI_PROJECT_DIR/log_examples_make"
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_EXAMPLE_TEST
- $BOT_LABEL_REGULAR_TEST
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
script:
# it's not possible to build 100% out-of-tree and have the "artifacts"
# mechanism work, but this is the next best thing
build_examples: Small cleanups * Override MAKEFLAGS via make not via shell variables * Remove build_examples in gitlab-ci * Don't use mktemp for any logs
2017-08-31 23:42:39 -04:00
- rm -rf build_examples
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
- mkdir build_examples
- cd build_examples
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
# build some of examples
CI: Fix a sporadic bug when building of the examples. Add logs to the artifacts
2017-12-28 05:20:14 -05:00
- mkdir -p ${LOG_PATH}
CI: Move the ci-related staff to a separate directory
2017-06-16 00:38:32 -04:00
- ${IDF_PATH}/tools/ci/build_examples.sh "${CI_JOB_NAME}"
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
# same as above, but for CMake
.build_examples_cmake_template: &build_examples_cmake_template
<<: *build_template
retry: 1
artifacts:
when: always
paths:
- build_examples_cmake/*/*/*/build/*.bin
- build_examples_cmake/*/*/*/build/*.elf
- build_examples_cmake/*/*/*/build/*.map
- build_examples_cmake/*/*/*/build/download.config
- build_examples_cmake/*/*/*/build/bootloader/*.bin
- $LOG_PATH
expire_in: 1 week
variables:
IDF_CI_BUILD: "1"
LOG_PATH: "$CI_PROJECT_DIR/log_examples_cmake"
script:
# it's not possible to build 100% out-of-tree and have the "artifacts"
# mechanism work, but this is the next best thing
- rm -rf build_examples_cmake
- mkdir build_examples_cmake
- cd build_examples_cmake
# build some of examples
- mkdir -p ${LOG_PATH}
- ${IDF_PATH}/tools/ci/build_examples_cmake.sh "${CI_JOB_NAME}"
build_examples_make_00:
<<: *build_examples_make_template
build_examples_make_01:
<<: *build_examples_make_template
build_examples_make_02:
<<: *build_examples_make_template
build_examples_make_03:
<<: *build_examples_make_template
build_examples_make_04:
<<: *build_examples_make_template
build_examples_make_05:
<<: *build_examples_make_template
build_examples_make_06:
<<: *build_examples_make_template
build_examples_make_07:
<<: *build_examples_make_template
build_examples_cmake_00:
<<: *build_examples_cmake_template
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_01:
<<: *build_examples_cmake_template
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_02:
<<: *build_examples_cmake_template
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_03:
<<: *build_examples_cmake_template
CI: Build examples in parallel Now you can create several 'build_examples_N' jobs in the .gitlab-ci.yaml and get parallel execution.
2017-06-07 04:30:25 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_04:
<<: *build_examples_cmake_template
Reinstate build_examples gitlab CI case Had been removed in 42e31116
2016-10-11 01:41:05 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_05:
<<: *build_examples_cmake_template
ci: Add two more example build jobs per CI pass
2017-09-01 03:29:51 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_06:
<<: *build_examples_cmake_template
ci: Add two more example build jobs per CI pass
2017-09-01 03:29:51 -04:00
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
build_examples_cmake_07:
<<: *build_examples_cmake_template
ci: increase number of example build jobs
2017-11-22 09:40:49 -05:00
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
# If you want to add new build example jobs, please add it into dependencies of `.example_test_template`
ci: increase number of example build jobs
2017-11-22 09:40:49 -05:00
docs: fix typos, build docs with gitlab CI
2016-11-01 08:08:29 -04:00
build_docs:
stage: build
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
docs: fix typos, build docs with gitlab CI
2016-11-01 08:08:29 -04:00
tags:
- build_docs
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
artifacts:
Fail CI build on Sphinx warnings
2017-09-06 15:16:34 -04:00
when: always
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
paths:
Adjusted CI configuration to handle 'en' and 'zh_CN' language versions
2018-02-03 16:12:13 -05:00
# English version of documentation
- docs/en/doxygen-warning-log.txt
- docs/en/sphinx-warning-log.txt
- docs/en/sphinx-warning-log-sanitized.txt
- docs/en/_build/html
# Chinese version of documentation
- docs/zh_CN/doxygen-warning-log.txt
- docs/zh_CN/sphinx-warning-log.txt
- docs/zh_CN/sphinx-warning-log-sanitized.txt
- docs/zh_CN/_build/html
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
expire_in: 1 mos
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_BUILD_DOCS
- $BOT_LABEL_REGULAR_TEST
docs: fix typos, build docs with gitlab CI
2016-11-01 08:08:29 -04:00
script:
Introduced a CI check if folders with localized documentation are in sync, i.e. if they contain the same list of files
2018-03-16 02:54:58 -04:00
- cd docs
- ./check_lang_folder_sync.sh
- cd en
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
- make gh-linkcheck
docs: fix typos, build docs with gitlab CI
2016-11-01 08:08:29 -04:00
- make html
Adjusted CI configuration to handle 'en' and 'zh_CN' language versions
2018-02-03 16:12:13 -05:00
- ../check_doc_warnings.sh
- cd ../zh_CN
- make gh-linkcheck
- make html
- ../check_doc_warnings.sh
docs: fix typos, build docs with gitlab CI
2016-11-01 08:08:29 -04:00
cmake: Style cleanup, add cmake linter to gitlab CI
2018-03-19 21:27:00 -04:00
verify_cmake_style:
stage: build
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
ci: Fix runner choice for CMake verification job
2018-11-27 03:31:37 -05:00
tags:
- host_test
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD
- $BOT_LABEL_REGULAR_TEST
cmake: Style cleanup, add cmake linter to gitlab CI
2018-03-19 21:27:00 -04:00
script:
tools/cmake/run_cmake_lint.sh
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
.host_test_template: &host_test_template
stage: host_test
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
tags:
ci: Use new host_test tag
2018-06-06 03:18:52 -04:00
- host_test
CI: Put in order the job dependences
2017-06-09 07:05:17 -04:00
dependencies: []
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_HOST_TEST
- $BOT_LABEL_REGULAR_TEST
Merge branch 'release/v3.1' into feature/cmake_v3.1
2018-08-15 22:58:31 -04:00
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
test_nvs_on_host:
<<: *host_test_template
components/nvs: run small number of tests as part of CI builds
2016-08-23 00:54:09 -04:00
script:
add unit tests to esp-idf rename nvs host test folder, modify .gitlab-ci.yml remove unit-test-app build re-format unit test files remove extra newlines in project.mk some refactoring for unit test part in project.mk add build files of unit-test-app in gitignore add README.md for unit test app correct headings in README.md remove files and make minor tweaks in unit test app update .gitlab-ci.yml to use unit test app delete unused lines in component_wrapper.mk delete periph_i2s.h and lcd test add text floating point in components/esp32/test/Kconfig correct idf test build paths in .gitlab-ci.yml
2016-11-17 03:36:10 -05:00
- cd components/nvs_flash/test_nvs_host
components/nvs: run small number of tests as part of CI builds
2016-08-23 00:54:09 -04:00
- make test
nvs: add long ci test for power off recovery and coverage This test can be triggered manually: `bot test name: test_nvs_coverage`
2018-04-15 23:50:12 -04:00
test_nvs_coverage:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
nvs: add long ci test for power off recovery and coverage This test can be triggered manually: `bot test name: test_nvs_coverage`
2018-04-15 23:50:12 -04:00
artifacts:
paths:
- components/nvs_flash/test_nvs_host/coverage_report
only:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
refs:
- triggers
variables:
- $BOT_LABEL_NVS_COVERAGE
nvs: add long ci test for power off recovery and coverage This test can be triggered manually: `bot test name: test_nvs_coverage`
2018-04-15 23:50:12 -04:00
script:
- cd components/nvs_flash/test_nvs_host
- make coverage_report
gen_esp32part: Run unit tests on host as part of gitlab-ci
2017-05-11 22:30:27 -04:00
test_partition_table_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
gen_esp32part: Run unit tests on host as part of gitlab-ci
2017-05-11 22:30:27 -04:00
tags:
- build
script:
- cd components/partition_table/test_gen_esp32part_host
- ./gen_esp32part_tests.py
wear_levelling: run host side test in CI
2017-04-10 09:41:19 -04:00
test_wl_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
wear_levelling: run host side test in CI
2017-04-10 09:41:19 -04:00
artifacts:
paths:
- components/wear_levelling/test_wl_host/coverage_report.zip
script:
- cd components/wear_levelling/test_wl_host
- make test
ci: Add spiffs, fatfs host runs to CI Adds running the fatfs, spiffs sanity check to CI.
2018-05-22 06:26:19 -04:00
test_fatfs_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
heap: Refactor heap regions/capabilities out of FreeRTOS Remove tagged heap API, rename caps_xxx to heap_caps_xxx Also includes additional heap_caps_xxx inspection functions.
2017-05-03 04:03:28 -04:00
tags:
ci: Add spiffs, fatfs host runs to CI Adds running the fatfs, spiffs sanity check to CI.
2018-05-22 06:26:19 -04:00
- wl_host_test
script:
- cd components/fatfs/test_fatfs_host/
- make test
test_spiffs_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
ci: Add spiffs, fatfs host runs to CI Adds running the fatfs, spiffs sanity check to CI.
2018-05-22 06:26:19 -04:00
tags:
- wl_host_test
script:
- cd components/spiffs/test_spiffs_host/
- make test
heap: Refactor heap regions/capabilities out of FreeRTOS Remove tagged heap API, rename caps_xxx to heap_caps_xxx Also includes additional heap_caps_xxx inspection functions.
2017-05-03 04:03:28 -04:00
test_multi_heap_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
heap: Refactor heap regions/capabilities out of FreeRTOS Remove tagged heap API, rename caps_xxx to heap_caps_xxx Also includes additional heap_caps_xxx inspection functions.
2017-05-03 04:03:28 -04:00
script:
- cd components/heap/test_multi_heap_host
heap: Change test_multi_heap_on_host multi-config to bash script not Makefile Hopefully fix some CI building issues with parallel builds.
2018-04-02 22:04:12 -04:00
- ./test_all_configs.sh
heap: Refactor heap regions/capabilities out of FreeRTOS Remove tagged heap API, rename caps_xxx to heap_caps_xxx Also includes additional heap_caps_xxx inspection functions.
2017-05-03 04:03:28 -04:00
kconfig: Add confserver.py to expose sdkconfig to clients
2018-05-16 02:54:22 -04:00
test_confserver:
Merge branch 'release/v3.1' into feature/cmake_v3.1
2018-08-15 22:58:31 -04:00
<<: *host_test_template
kconfig: Add confserver.py to expose sdkconfig to clients
2018-05-16 02:54:22 -04:00
script:
- cd tools/kconfig_new/test
- ./test_confserver.py
Add build system test (via bash script) Currently fails due to bootloader not automatically rebuilding anything, and ELF/BIN files generating when nothing changed.
2016-08-24 00:16:26 -04:00
test_build_system:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
Add build system test (via bash script) Currently fails due to bootloader not automatically rebuilding anything, and ELF/BIN files generating when nothing changed.
2016-08-24 00:16:26 -04:00
script:
build system tests: Run inside PWD same as build_examples.sh
2017-09-03 21:15:04 -04:00
- ${IDF_PATH}/tools/ci/test_configure_ci_environment.sh
- rm -rf test_build_system
- mkdir test_build_system
- cd test_build_system
- ${IDF_PATH}/tools/ci/test_build_system.sh
Add build system test (via bash script) Currently fails due to bootloader not automatically rebuilding anything, and ELF/BIN files generating when nothing changed.
2016-08-24 00:16:26 -04:00
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
test_build_system_cmake:
Merge branch 'release/v3.1' into feature/cmake_v3.1
2018-08-15 22:58:31 -04:00
<<: *host_test_template
cmake: Add build system tests
2018-04-17 19:30:27 -04:00
script:
- ${IDF_PATH}/tools/ci/test_configure_ci_environment.sh
- rm -rf test_build_system
- mkdir test_build_system
- cd test_build_system
- ${IDF_PATH}/tools/ci/test_build_system_cmake.sh
Make it easier to look up error messages tools/gen_esp_err_to_name.py generates components/esp32/esp_err_to_name.c for lookup of the error codes from all of the IDF project and easily identify all codes in one place
2018-02-01 07:14:47 -05:00
test_esp_err_to_name_on_host:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
<<: *host_test_template
Make it easier to look up error messages tools/gen_esp_err_to_name.py generates components/esp32/esp_err_to_name.c for lookup of the error codes from all of the IDF project and easily identify all codes in one place
2018-02-01 07:14:47 -05:00
script:
- cd tools/
- ./gen_esp_err_to_name.py
- git diff --exit-code -- ../components/esp32/esp_err_to_name.c || (echo 'Differences found. Please run gen_esp_err_to_name.py and commit the changes.'; exit 1)
ci: Simplify github deployment CI_COMMIT_REF_NAME lets us use a single line to git push
2018-07-26 22:01:58 -04:00
push_to_github:
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
stage: deploy
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
ci: Reorder the clauses for more convenience
2017-04-26 06:09:14 -04:00
tags:
- deploy
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
only:
ci: Don't push to Github or deploy docs on customized pipelines BOT_TRIGGER_WITH_LABEL must be empty (meaning all tests are running).
2020-05-22 01:04:39 -04:00
refs:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
variables:
- $BOT_TRIGGER_WITH_LABEL == null
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
when: on_success
CI: Put in order the job dependences
2017-06-09 07:05:17 -04:00
dependencies: []
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *do_nothing_before
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
script:
- mkdir -p ~/.ssh
- chmod 700 ~/.ssh
- echo -n $GH_PUSH_KEY > ~/.ssh/id_rsa_base64
- base64 --decode --ignore-garbage ~/.ssh/id_rsa_base64 > ~/.ssh/id_rsa
- chmod 600 ~/.ssh/id_rsa
- echo -e "Host github.com\n\tStrictHostKeyChecking no\n" >> ~/.ssh/config
CI: Fix error in the push_master_to_github job when using the fetch strategy
2017-07-03 23:52:57 -04:00
- git remote remove github &>/dev/null || true
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
- git remote add github git@github.com:espressif/esp-idf.git
ci: Fix spurious pipeline failure when deploying a tag to GitHub Everything succeeds, but because [ -z ${CI_COMMIT_TAG} ] on the last line returns non-zero, it fails the job.
2018-08-15 21:04:28 -04:00
- tools/ci/push_to_github.sh
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
docs: deploy built docs
2016-11-01 08:58:47 -04:00
deploy_docs:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
stage: deploy
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
ci: Reorder the clauses for more convenience
2017-04-26 06:09:14 -04:00
tags:
- deploy
ci: fix tags for internal deploy jobs
2020-01-10 05:36:52 -05:00
- shiny
docs: deploy built docs
2016-11-01 08:58:47 -04:00
only:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
refs:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
- triggers
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD_DOCS
CI: Put in order the job dependences
2017-06-09 07:05:17 -04:00
dependencies:
- build_docs
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *do_nothing_before
docs: deploy built docs
2016-11-01 08:58:47 -04:00
script:
- mkdir -p ~/.ssh
- chmod 700 ~/.ssh
- echo -n $DOCS_DEPLOY_KEY > ~/.ssh/id_rsa_base64
- base64 --decode --ignore-garbage ~/.ssh/id_rsa_base64 > ~/.ssh/id_rsa
- chmod 600 ~/.ssh/id_rsa
- echo -e "Host $DOCS_SERVER\n\tStrictHostKeyChecking no\n\tUser $DOCS_SERVER_USER\n" >> ~/.ssh/config
- export GIT_VER=$(git describe --always)
doc: two languages support for deploy_docs stage.
2018-02-09 04:17:06 -05:00
- cd docs/en/_build/
- mv html $GIT_VER
- tar czvf $GIT_VER.tar.gz $GIT_VER
- scp $GIT_VER.tar.gz $DOCS_SERVER:$DOCS_PATH/en
- ssh $DOCS_SERVER -x "cd $DOCS_PATH/en && tar xzvf $GIT_VER.tar.gz && rm -f latest && ln -s $GIT_VER latest"
- cd ../../zh_CN/_build/
docs: deploy built docs
2016-11-01 08:58:47 -04:00
- mv html $GIT_VER
- tar czvf $GIT_VER.tar.gz $GIT_VER
doc: two languages support for deploy_docs stage.
2018-02-09 04:17:06 -05:00
- scp $GIT_VER.tar.gz $DOCS_SERVER:$DOCS_PATH/zh_CN
- ssh $DOCS_SERVER -x "cd $DOCS_PATH/zh_CN && tar xzvf $GIT_VER.tar.gz && rm -f latest && ln -s $GIT_VER latest"
CI: print document preview link in `deploy_docs`
2018-02-12 01:30:02 -05:00
# add link to preview doc
- echo "[document preview][en] $CI_DOCKER_REGISTRY/docs/esp-idf/en/${GIT_VER}/index.html"
- echo "[document preview][zh_CN] $CI_DOCKER_REGISTRY/docs/esp-idf/zh_CN/${GIT_VER}/index.html"
docs: deploy built docs
2016-11-01 08:58:47 -04:00
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
check_doc_links:
CI: add stage `host_test`: 1. Add `host_test` stage for test jobs running on host. 2. Rename stage `test` to `integration_test`.
2018-06-24 22:33:59 -04:00
stage: host_test
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
tags:
- check_doc_links
only:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
refs:
# can only be triggered
- triggers
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_BUILD_DOCS
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
artifacts:
paths:
- docs/_build/linkcheck
expire_in: 1 mos
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
script:
# must be triggered with CHECK_LINKS=Yes, otherwise exit without test
ci: fix release branch being pushed into master Also fix variable quoting issue in link check build.
2017-03-04 05:17:59 -05:00
- test "$CHECK_LINKS" = "Yes" || exit 0
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
# can only run on master branch (otherwise the commit is not on Github yet)
fix bug that files missing commit in MR 773
2017-05-31 05:20:29 -04:00
- test "${CI_COMMIT_REF_NAME}" = "master" || exit 0
docs: use custom roles to generate GitHub links This change replaces direct links to GitHub master branch with auto-generated links using docutils custom roles. These auto-generated links point to the tree or blob for the git commit ID (or tag) of the repository. This is needed to ensure that links don’t become broken when files in master branch are moved around or deleted. The following roles are introduced: - :idf:`path` - points to directory inside ESP-IDF - :idf_blob:`path` - points to file inside ESP-IDF - :idf_raw:`path` - points to raw view of the file inside ESP-IDF - :component:`path` - points to directory inside ESP-IDF components dir - :component_blob:`path` - points to file inside ESP-IDF components dir - :component_raw:`path` - points to raw view of the file inside ESP-IDF components dir - :example:`path` - points to directory inside ESP-IDF examples dir - :example_blob:`path` - points to file inside ESP-IDF examples dir - :example_raw:`path` - points to raw view of the file inside ESP-IDF examples dir A check is added to the CI build script, which searches RST files for presence of hard-coded links (identified by tree/master, blob/master, or raw/master part of the URL). This check can be run manually: cd docs && make gh-linkcheck Additionally, Sphinx linkcheck build type is used to create new CI test, which check for broken links. This test has to be triggered explicitly, because including it in normal build process (when the commit is not yet deployed to Github) will not work. It can be triggered in a regular fashion using a combination of cron and Curl, similar to stress tests.
2017-01-19 03:16:06 -05:00
- cd docs
- make linkcheck
CI: check if commit history need revise
2017-03-31 06:52:59 -04:00
check_commit_msg:
stage: deploy
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
CI: check if commit history need revise
2017-03-31 06:52:59 -04:00
tags:
- build
except:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
CI: Put in order the job dependences
2017-06-09 07:05:17 -04:00
dependencies: []
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *do_nothing_before
CI: check if commit history need revise
2017-03-31 06:52:59 -04:00
script:
ci check_commit_msg: Use CI_COMMIT_SHA to avoid ambiguity
2017-06-16 00:36:34 -04:00
- git status
- git log -n10 --oneline
CI: check if commit history need revise
2017-03-31 06:52:59 -04:00
# commit start with "WIP: " need to be squashed before merge
ci check_commit_msg: Use CI_COMMIT_SHA to avoid ambiguity
2017-06-16 00:36:34 -04:00
- 'git log --pretty=%s master.. -- | grep "^WIP: " && exit 1 || exit 0'
docs: deploy built docs
2016-11-01 08:58:47 -04:00
ci: check for executable flag on source files
2018-05-28 14:01:43 -04:00
check_permissions:
stage: deploy
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
tags:
- build
except:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
dependencies: []
before_script: *do_nothing_before
script:
- tools/ci/check-executable.sh
cmake: Add missing example CMakeLists.txt files, CI check all examples have both
2018-08-27 23:10:48 -04:00
check_examples_cmake_make:
stage: deploy
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
tags:
- build
except:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
dependencies: []
before_script: *do_nothing_before
script:
- tools/ci/check_examples_cmake_make.sh
CI: check if internal submodule synced to GH See MR !834
2017-06-07 23:55:27 -04:00
check_submodule_sync:
stage: deploy
CI: support sepcify docker image tag with bot
2017-11-22 21:13:14 -05:00
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
CI: check if internal submodule synced to GH See MR !834
2017-06-07 23:55:27 -04:00
tags:
- build
except:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
CI: Put in order the job dependences
2017-06-09 07:05:17 -04:00
dependencies: []
ci: Only use "github_sync" tagged runners to talk to GitHub
2019-02-24 18:41:39 -05:00
tags:
- github_sync
CI: Use local mirrors for submodules The CI uses the mirror-submodule-update.sh for non-permanent reassignment of 3rdparty sub-modules to local mirrors (only for 'non-master' branches). List of the mirrors in mirror-list.txt You can use the script locally to speed up data retrieval on network problems check_submodule_sync job uses 'GIT_STRATEGY: clone' to check the availability of public sources
2017-06-18 21:59:18 -04:00
variables:
GIT_STRATEGY: clone
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *do_nothing_before
ci: Retry submodule sync 2 more times before failing
2019-02-20 18:48:55 -05:00
retry: 2
CI: check if internal submodule synced to GH See MR !834
2017-06-07 23:55:27 -04:00
script:
# check if all submodules are correctly synced to public repostory
- git submodule update --init --recursive
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
check_pipeline_triggered_by_label:
stage: post_check
image: $CI_DOCKER_REGISTRY/esp32-ci-env$BOT_DOCKER_IMAGE_TAG
dependencies: []
before_script: *do_nothing_before
tags:
- build
only:
variables:
- $BOT_TRIGGER_WITH_LABEL
script:
# If the pipeline is triggered with label, the pipeline will only succeeded if "regular_test" label is added.
# We want to make sure some jobs are always executed to detect regression.
- test "$BOT_LABEL_REGULAR_TEST" = "true" || exit -1
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
assign_test:
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
tags:
- assign_test
image: $CI_DOCKER_REGISTRY/ubuntu-test-env$BOT_DOCKER_IMAGE_TAG
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
stage: assign_test
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
# gitlab ci do not support match job with RegEx or wildcard now in dependencies.
# we have a lot build example jobs. now we don't use dependencies, just download all artificats of build stage.
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
dependencies:
- build_ssc_00
- build_ssc_01
- build_ssc_02
- build_esp_idf_tests
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
variables:
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
TEST_FW_PATH: "$CI_PROJECT_DIR/tools/tiny-test-fw"
EXAMPLE_CONFIG_OUTPUT_PATH: "$CI_PROJECT_DIR/examples/test_configs"
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
INTEGRATION_CONFIG_OUTPUT_PATH: "${CI_PROJECT_DIR}/components/idf_test/integration_test/CIConfigs"
TEST_CASE_FILE_PATH: "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
ASSIGN_TEST_CASE_SCRIPT: "${CI_PROJECT_DIR}/auto_test_script/bin/CIAssignTestCases.py"
PYTHONPATH: "${CI_PROJECT_DIR}/auto_test_script/packages"
PYTHON_VER: 3.7.7
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
artifacts:
paths:
- components/idf_test/*/CIConfigs
- components/idf_test/*/TC.sqlite
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
- $EXAMPLE_CONFIG_OUTPUT_PATH
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
expire_in: 1 mos
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_UNIT_TEST
- $BOT_LABEL_INTEGRATION_TEST
- $BOT_LABEL_EXAMPLE_TEST
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *add_gitlab_key_before
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
script:
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
# assign example tests
- python $TEST_FW_PATH/CIAssignExampleTest.py $IDF_PATH/examples $IDF_PATH/.gitlab-ci.yml $EXAMPLE_CONFIG_OUTPUT_PATH
CI: new CI ut framework, and can run it in local PC
2018-01-31 05:59:10 -05:00
# assign unit test cases
- python $TEST_FW_PATH/CIAssignUnitTest.py $IDF_PATH/components/idf_test/unit_test/TestCaseAll.yml $IDF_PATH/.gitlab-ci.yml $IDF_PATH/components/idf_test/unit_test/CIConfigs
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
# clone test script to assign tests
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT auto_test_script auto_test_script
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
# assgin integration test cases
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- python ${ASSIGN_TEST_CASE_SCRIPT} -t $TEST_CASE_FILE_PATH -c $IDF_PATH/.gitlab-ci.yml -b $IDF_PATH/SSC/ssc_bin -o $INTEGRATION_CONFIG_OUTPUT_PATH
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
.example_test_template: &example_test_template
ci: combine unit_test and integration_test stage: The number of runners of integration test is not bottleneck to CI pipeline performance now. Combine these 2 stages will make integration test executed even unit test fails. This could help us to collect more info about test history.
2018-11-26 03:40:32 -05:00
stage: target_test
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
when: on_success
only:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
refs:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
- triggers
- schedules
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_EXAMPLE_TEST
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
dependencies:
- assign_test
ci: Split build_examples jobs into make & cmake Fix problem where failures in make were being ignored.
2018-09-13 00:32:41 -04:00
- build_examples_make_00
- build_examples_make_01
- build_examples_make_02
- build_examples_make_03
- build_examples_make_04
- build_examples_make_05
- build_examples_make_06
- build_examples_make_07
- build_examples_cmake_00
- build_examples_cmake_01
- build_examples_cmake_02
- build_examples_cmake_03
- build_examples_cmake_04
- build_examples_cmake_05
- build_examples_cmake_06
- build_examples_cmake_07
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
artifacts:
when: always
paths:
- $LOG_PATH
ci: use artifacts:reports feature of Gitlab CI
2018-11-13 08:26:58 -05:00
expire_in: 1 week
reports:
junit: $LOG_PATH/*/XUNIT_RESULT.xml
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
variables:
TEST_FW_PATH: "$CI_PROJECT_DIR/tools/tiny-test-fw"
TEST_CASE_PATH: "$CI_PROJECT_DIR/examples"
CONFIG_FILE: "$CI_PROJECT_DIR/examples/test_configs/$CI_JOB_NAME.yml"
LOG_PATH: "$CI_PROJECT_DIR/TEST_LOGS"
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
ENV_FILE: "$CI_PROJECT_DIR/ci-test-runner-configs/$CI_RUNNER_DESCRIPTION/EnvConfig.yml"
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
script:
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
# clone test env configs
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
- cd $TEST_FW_PATH
# run test
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
- python Runner.py $TEST_CASE_PATH -c $CONFIG_FILE -e $ENV_FILE
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
CI: new CI ut framework, and can run it in local PC
2018-01-31 05:59:10 -05:00
.unit_test_template: &unit_test_template
<<: *example_test_template
ci: combine unit_test and integration_test stage: The number of runners of integration test is not bottleneck to CI pipeline performance now. Combine these 2 stages will make integration test executed even unit test fails. This could help us to collect more info about test history.
2018-11-26 03:40:32 -05:00
stage: target_test
CI: new CI ut framework, and can run it in local PC
2018-01-31 05:59:10 -05:00
dependencies:
- assign_test
CI: remove unnecessary artifacts of assign_test
2018-05-15 11:04:21 -04:00
- build_esp_idf_tests
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
only:
refs:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
- triggers
- schedules
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_UNIT_TEST
CI: new CI ut framework, and can run it in local PC
2018-01-31 05:59:10 -05:00
variables:
TEST_FW_PATH: "$CI_PROJECT_DIR/tools/tiny-test-fw"
TEST_CASE_PATH: "$CI_PROJECT_DIR/tools/unit-test-app"
CONFIG_FILE: "$CI_PROJECT_DIR/components/idf_test/unit_test/CIConfigs/$CI_JOB_NAME.yml"
LOG_PATH: "$CI_PROJECT_DIR/TEST_LOGS"
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
ENV_FILE: "$CI_PROJECT_DIR/ci-test-runner-configs/$CI_RUNNER_DESCRIPTION/EnvConfig.yml"
CI: new CI ut framework, and can run it in local PC
2018-01-31 05:59:10 -05:00
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
.test_template: &test_template
ci: combine unit_test and integration_test stage: The number of runners of integration test is not bottleneck to CI pipeline performance now. Combine these 2 stages will make integration test executed even unit test fails. This could help us to collect more info about test history.
2018-11-26 03:40:32 -05:00
stage: target_test
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
when: on_success
only:
CI: only create required jobs when use bot to trigger test: Gitlab CI now allow us to define if a job need to be created by varialbes. This commit add label to CI jobs, so we can make some jobs not created in certain scenarios when we trigger pipeline with @bot.
2018-09-29 02:51:43 -04:00
refs:
- master
- /^release\/v/
- /^v\d+\.\d+(\.\d+)?($|-)/
- triggers
- schedules
variables:
- $BOT_TRIGGER_WITH_LABEL == null
- $BOT_LABEL_INTEGRATION_TEST
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
dependencies:
- assign_test
CI: support build SSC in multiple jobs
2017-11-30 23:00:40 -05:00
- build_ssc_00
- build_ssc_01
- build_ssc_02
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
artifacts:
when: always
paths:
- $LOG_PATH
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
expire_in: 1 mos
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
variables:
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
LOCAL_ENV_CONFIG_PATH: "$CI_PROJECT_DIR/ci-test-runner-configs/$CI_RUNNER_DESCRIPTION/ESP32_IDF"
fix bug that files missing commit in MR 773
2017-05-31 05:20:29 -04:00
LOG_PATH: "$CI_PROJECT_DIR/$CI_COMMIT_SHA"
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
TEST_CASE_FILE_PATH: "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
CONFIG_FILE_PATH: "${CI_PROJECT_DIR}/components/idf_test/integration_test/CIConfigs"
KNOWN_ISSUE_FILE: "${CI_PROJECT_DIR}/components/idf_test/integration_test/KnownIssues"
PYTHONPATH: "${CI_PROJECT_DIR}/auto_test_script/packages"
CI_RUNNER_SCRIPT: "${CI_PROJECT_DIR}/auto_test_script/bin/CIRunner.py"
PYTHON_VER: 3.7.7
CI: Use anchors to get rid of code dublication in the 'before_script' clauses
2017-06-26 06:42:28 -04:00
before_script: *add_gitlab_key_before
CI: Use custom get_full_sources.sh script instead of gitlab-ci's strategies Work around problems caused by failed submodule clones corrupting the working directory on the build runner. Add 10 retries for cloning submodules.
2017-06-14 03:52:33 -04:00
script:
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- *define_config_file_name
CI: Use custom get_full_sources.sh script instead of gitlab-ci's strategies Work around problems caused by failed submodule clones corrupting the working directory on the build runner. Add 10 retries for cloning submodules.
2017-06-14 03:52:33 -04:00
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
CI: get test env config from gitlab Previous design was put test env config on local runners. It's not easy to manage as test runners count growing. Now we'll put config files for test runners to a Gitlab repository. Test runners will get its config from Gitlab every time before running.
2017-02-02 08:59:00 -05:00
# clone local test env configs
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
add gitlab key in test template job
2016-09-29 01:38:29 -04:00
# clone test bench
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT auto_test_script auto_test_script
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- cat ${KNOWN_ISSUE_FILE} >> ${TEST_CASE_FILE_PATH}/KnownIssues
add gitlab key in test template job
2016-09-29 01:38:29 -04:00
# run test
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- python ${CI_RUNNER_SCRIPT} -l "$LOG_PATH/$CI_JOB_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
nvs_compatible_test:
<<: *test_template
artifacts:
when: always
paths:
- $LOG_PATH
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
- nvs_wifi.bin
CI: minor optimize of CI config file: 1. set shorter expire time for artifacts 2. set dependency for example test jobs, to limit the artifacts it downloads
2018-06-24 02:11:57 -04:00
expire_in: 1 mos
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
tags:
- ESP32_IDF
- NVS_Compatible
script:
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- *define_config_file_name
# first test if config file exists, if not exist, exit 0
- test -e $CONFIG_FILE || exit 0
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
# clone local test env configs
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone $TEST_ENV_CONFIG_REPO
CI: try to use the correct branch of other projects used in CI: 1. revision defined in bot message 2. branch name (or tag name) of current IDF 3. CI_MERGE_REQUEST_TARGET_BRANCH_NAME 4. branch name parsed from `git describe` 5. default branch
2019-07-21 04:28:50 -04:00
- python $CHECKOUT_REF_SCRIPT ci-test-runner-configs ci-test-runner-configs
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
# clone test bench
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- ./tools/ci/retry_failed.sh git clone ${CI_AUTO_TEST_SCRIPT_REPO_URL} -b empty_branch
- ./tools/ci/retry_failed.sh git -C auto_test_script checkout -f ${CI_AUTO_TEST_SCRIPT_REPO_BRANCH}
- python $CHECKOUT_REF_SCRIPT auto_test_script "$CI_PROJECT_DIR/auto_test_script/TestCaseFiles"
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
# prepare nvs bins
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- cd auto_test_script
- ./tools/prepare_nvs_bin.sh
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
# run test
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
- python ${CI_RUNNER_SCRIPT} -l "$LOG_PATH/$JOG_FULL_NAME" -c $CONFIG_FILE -e $LOCAL_ENV_CONFIG_PATH -t $TEST_CASE_FILE_PATH
test: add NVS compatible test case and CI job
2017-06-02 03:03:56 -04:00
CI: integrate example test to CI
2017-10-09 22:55:25 -04:00
example_test_001_01:
<<: *example_test_template
tags:
- ESP32
- Example_WIFI
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
example_test_002_01:
<<: *example_test_template
test: use simplified env to test iperf cases
2018-10-24 01:34:05 -04:00
tags:
- ESP32
- Example_ShieldBox_Basic
example_test_006_01:
<<: *example_test_template
image: $CI_DOCKER_REGISTRY/ubuntu-test-env$BOT_DOCKER_IMAGE_TAG
only:
variables:
- $BOT_LABEL_IPERF_STRESS_TEST
example test: integrate wifi throughput test to CI
2018-01-08 07:33:09 -05:00
tags:
- ESP32
- Example_ShieldBox
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
UT_001_01:
use correct template for unit test jobs
2016-11-01 08:33:23 -04:00
<<: *unit_test_template
integrate unit test to CI
2016-11-01 07:30:42 -04:00
tags:
- ESP32_IDF
- UT_T1_1
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
UT_001_02:
CI: add script for parsing unit test cases for CI from test files Add python script that parses list of unit test cases for CI from component test folder Modify .gitlab-ci.yml to run this script as part of build unit tests stage
2016-12-07 00:58:51 -05:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
UT_001_03:
<<: *unit_test_template
CI: add one more UT runner
2017-06-02 21:56:13 -04:00
tags:
- ESP32_IDF
- UT_T1_1
UT_001_04:
<<: *unit_test_template
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
tags:
- ESP32_IDF
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
- UT_T1_1
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
unit test: add sd env and spi env for sdmmc
2017-08-11 03:25:55 -04:00
UT_001_05:
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_1
unit test: add sd env and spi env for sdmmc
2017-08-11 03:25:55 -04:00
UT_001_06:
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_1
unit test: add sd env and spi env for sdmmc
2017-08-11 03:25:55 -04:00
ci: add extra unit test job
2017-09-04 08:39:35 -04:00
UT_001_07:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
UT_001_08:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: fix C++ unit test cases not executed by CI
2017-11-23 03:51:28 -05:00
UT_001_09:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
ci: increase number of unit test jobs
2018-05-11 04:42:52 -04:00
UT_001_10:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_11:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_12:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_13:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_14:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_15:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_1
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_16:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_17:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_18:
CI: fix C++ unit test cases not executed by CI
2017-11-23 03:51:28 -05:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_19:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_20:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_21:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_22:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_23:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_001_24:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
esp32: Fix not the right time spent in a deep sleep Before entering the deep sleep, the RTC and FRC counters are synchronized. Updating the boot_time. Added a unit test for this case. Fixed warnings for MULTIPLE_STAGES Closes https://github.com/espressif/esp-idf/issues/1840
2018-06-04 03:39:18 -04:00
UT_001_25:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
esp32: Fix not the right time spent in a deep sleep Before entering the deep sleep, the RTC and FRC counters are synchronized. Updating the boot_time. Added a unit test for this case. Fixed warnings for MULTIPLE_STAGES Closes https://github.com/espressif/esp-idf/issues/1840
2018-06-04 03:39:18 -04:00
UT_001_26:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
UT_001_27:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
unit-test-app: allow specifying subset of tests for configuration For some test configurations, not all tests need to be run. This change allows adding a comment in the configuration file of the following form: unit-test-app makefile will use it to determine which components to build. If the comment is not present, all components will be built (TESTS_ALL=1). Also add test configuration for libsodium. It is a separate test configuration due to the large binary size generated when building libsodium tests.
2018-04-28 06:56:25 -04:00
UT_001_28:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
UT_001_29:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
test: components/driver: timer case
2017-12-16 21:24:49 -05:00
UT_001_30:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
FATFS support without wear levelling This change allows readonly FATFS to be mounted without wear levelling support. This will provide the customers a simple way to mount FATFS images generated on host and flashed onto the chip during factory provisioning. Since NVS encryption is not supported yet and NVS entry size is limited, the change will provide an easy alternative for securing the provisioning data by just marking FATFS parition as encrypted.
2018-06-08 08:09:00 -04:00
UT_001_31:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
aes/sha/mpi: Bugfix a use of shared registers. This commit resolves a blocking in esp_aes_block function. Introduce: The problem was in the fact that AES is switched off at the moment when he should give out the processed data. But because of the disabled, the operation can not be completed successfully, there is an infinite hang. The reason for this behavior is that the registers for controlling the inclusion of AES, SHA, MPI have shared registers and they were not protected from sharing. Fix some related issue with shared using of AES SHA RSA accelerators. Closes: https://github.com/espressif/esp-idf/issues/2295#issuecomment-432898137
2018-10-29 11:55:02 -04:00
UT_001_32:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
mbedtls: Fix compilation errors when CONFIG_MBEDTLS_HARDWARE_AES is disabled
2018-10-17 09:53:46 -04:00
UT_001_32:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
ci: Add test configs for 32kHz crystals
2019-11-14 00:57:32 -05:00
UT_001_33:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_no32kXTAL
UT_001_34:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_no32kXTAL
UT_001_35:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_no32kXTAL
UT_001_36:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_no32kXTAL
- psram
UT_001_37:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_32kXTAL
UT_001_38:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_32kXTAL
UT_001_39:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_32kXTAL
UT_001_40:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_32kXTAL
- psram
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
UT_001_41:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_002_01:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_SDMODE
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_002_02:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SDMODE
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_002_03:
CI: support test UT with different config by CI
2017-09-13 08:39:43 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SDMODE
ci: add extra unit test job
2017-09-04 08:39:35 -04:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_003_01:
ci: add one more job for single core unit tests
2017-11-05 08:50:43 -05:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SPIMODE
ci: add one more job for single core unit tests
2017-11-05 08:50:43 -05:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_003_02:
docs: add information about execution time of ULP instructions
2017-12-10 23:11:24 -05:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SPIMODE
docs: add information about execution time of ULP instructions
2017-12-10 23:11:24 -05:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_003_03:
ci: increase number of unit test jobs
2018-05-11 04:42:52 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SPIMODE
docs: add information about execution time of ULP instructions
2017-12-10 23:11:24 -05:00
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_04:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_05:
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_1
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_06:
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_1
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_07:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
UT_004_08:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- psram
unit tests: add psram configuration
2017-10-19 09:39:45 -04:00
esp32: Fix not the right time spent in a deep sleep Before entering the deep sleep, the RTC and FRC counters are synchronized. Updating the boot_time. Added a unit test for this case. Fixed warnings for MULTIPLE_STAGES Closes https://github.com/espressif/esp-idf/issues/1840
2018-06-04 03:39:18 -04:00
UT_004_09:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
- psram
test: components/driver: timer case
2017-12-16 21:24:49 -05:00
UT_004_10:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
- psram
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
aes/sha/mpi: Bugfix a use of shared registers. This commit resolves a blocking in esp_aes_block function. Introduce: The problem was in the fact that AES is switched off at the moment when he should give out the processed data. But because of the disabled, the operation can not be completed successfully, there is an infinite hang. The reason for this behavior is that the registers for controlling the inclusion of AES, SHA, MPI have shared registers and they were not protected from sharing. Fix some related issue with shared using of AES SHA RSA accelerators. Closes: https://github.com/espressif/esp-idf/issues/2295#issuecomment-432898137
2018-10-29 11:55:02 -04:00
UT_004_11:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
- psram
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_005_01:
CI: fix C++ unit test cases not executed by CI
2017-11-23 03:51:28 -05:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SDMODE
- psram
VFS: Use smaller numbers as file descriptors
2018-05-07 03:01:56 -04:00
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
UT_005_02:
ci: increase number of unit test jobs
2018-05-11 04:42:52 -04:00
<<: *unit_test_template
tags:
- ESP32_IDF
CI: assign unit test cases according to sdkconfig: We have built unit-test-app with different configs. Currently we use the config name as tags to match runners. It's not easy to add new configs (need to update tags to existed runners). Now we'll parse required test runner tags from `sdkconfig` file. For example, if config enables `CONFIG_SPIRAM_SUPPORT`, then it requires `psram` tag. This will make adding new configs easier. In this commit we change the one behavior of assign test: match keys of cases should be exactly the same with job tags. This fixes cases select jobs include their tags, and jobs requires those tags can't be assigned.
2018-05-14 23:51:56 -04:00
- UT_T1_SPIMODE
- psram
CI: fix C++ unit test cases not executed by CI
2017-11-23 03:51:28 -05:00
test: add driver/gpio test case
2017-12-16 21:19:51 -05:00
UT_006_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_GPIO
UT_006_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_GPIO
UT_006_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_GPIO
UT_006_04:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_GPIO
- psram
test: components/driver: ledc case
2017-12-16 21:22:22 -05:00
UT_008_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_LEDC
UT_008_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_LEDC
UT_008_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_LEDC
UT_008_04:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_LEDC
- psram
test: add driver/gpio test case
2017-12-16 21:19:51 -05:00
test: add driver/rmt test case
2018-01-02 07:17:49 -05:00
UT_010_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_RMT
UT_010_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_RMT
UT_010_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_RMT
UT_010_04:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_RMT
- psram
test: add test case to receive ds2ds packet
2018-11-28 08:53:06 -05:00
UT_017_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T2_1
UT_017_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T2_1
UT_017_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T2_1
UT_017_04:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T2_1
- psram
UT_017_05:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T2_1
- 8Mpsram
component/bt: Fixed the vulnerability released by Bluetooth org when using public key not check in the process of ECDH encryption. 1. Add the 100 times test when the private key is generated by the random number; 2. Add the bt components to the unit-test-app/config directory. 3. Added the bt unit test case to CI.
2018-08-05 09:18:31 -04:00
UT_601_01:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
Fix some bugs in phy 1. fix bug PHY/RTC functions called in ISR (update phy to v4007) 2. add UnitTest to test it 3. fix task watchdog bug when wifi change channel 4. disable/enable agc to mac deinit/init 5. add UnitTest Job
2019-01-13 03:05:12 -05:00
UT_601_02:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
UT_601_03:
<<: *unit_test_template
tags:
- ESP32_IDF
- UT_T1_1
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_001:
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 3
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
tags:
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_4
update ci config file with 2 changes: 1. add build SSC and do sanity test config 2. add tags to each job as sanity test need to be executed on special runner
2016-09-08 22:49:03 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_002:
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_2
CI: Minor changes in code formatting and cleanup
2017-06-09 06:14:29 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_003:
CI: add test jobs for BLE cases
2017-06-23 06:06:45 -04:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 14
CI: add test jobs for BLE cases
2017-06-23 06:06:45 -04:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T2_5
CI: add test jobs for BLE cases
2017-06-23 06:06:45 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_004:
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
<<: *test_template
add supported stress test cases to CI
2016-12-06 02:41:02 -05:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_APC
test: update ci test case
2017-12-18 06:24:09 -05:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_005:
test: update ci test case
2017-12-18 06:24:09 -05:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 2
test: update ci test case
2017-12-18 06:24:09 -05:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_5
test: update ci test case
2017-12-18 06:24:09 -05:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_006:
CI: update CI config file for auto assign test: we'll now assign cases to test jobs in assign_test_case job instead of static job config file.
2017-05-05 08:20:31 -04:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 13
update CI config file: 1. add night job define (need to set variable in trigger to run night jobs) 2. move auto generated part to the end of file 3. add auto generated CI jobs
2016-09-26 02:32:58 -04:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_6
test: update ci test case
2017-12-18 06:24:09 -05:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_007:
test: update ci test case
2017-12-18 06:24:09 -05:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 3
test: update ci test case
2017-12-18 06:24:09 -05:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_7
test: update ci test case
2017-12-18 06:24:09 -05:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_008:
test: add mesh basic function test cases
2018-04-28 05:17:05 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_8
test: add mesh basic function test cases
2018-04-28 05:17:05 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_009:
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_3
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_018:
auto_test_script will be cloned from gitlab
2016-09-27 04:22:18 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T1_9
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_019:
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
<<: *test_template
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
parallel: 2
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T2_2
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_020:
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T2_3
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
CI: get git describe from annotated tags: we should only parse IDF version from annotated tags
2020-10-23 21:26:22 -04:00
IT_021:
sync several changes from auto_test_script: 1. use variable for gitlab server 2. add LOCAL_ENV_CONFIG_PATH to template 2. update jobs with feature "allow fail"
2016-09-28 07:48:38 -04:00
<<: *test_template
tags:
- ESP32_IDF
test: split CI test environment: Currently CI test environment is complicated, usually includes NIC, AP. These devices are not used for a lot test cases. Therefore we split the test environment, remove unnecessary devices. Then it will be easier to create CI runners.
2018-08-26 00:15:51 -04:00
- SSC_T2_4
component/bt: fix don't dequeue the command queue after process the read_by_type_req(backport v3.1)
2020-04-03 07:08:52 -04:00
Reference in New Issue Copy Permalink