[TEST] dummy change #280
Closed
[TEST] dummy change #280
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit updates the twister workflow to use the new zephyr-runner v2 CI runner deployment. It also updates the workflow to use the `ci-repo-cache` Docker image, which includes the Zephyr repository cache, because the node level repository cache is no longer available in the zephyr-runner v2. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the twister workflow jobs that run on the zephyr-runner v2 to print the underlying cloud service information in the logs to help trace and debug potential runner issues. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the twister workflow to store ccache data in the zephyr-runner v2 node cache. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the twister workflow to, when available, use Redis remote storage backend for the ccache compilation cache data. The Redis cache server is hosted in the Kubernetes cluster in which the zephyr-runner pods run -- the Redis remote storage backend will be ignored if the server is unavailable. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit adds the compiler `--specs=*` flag to the ccache ignore option list because ccache is unable to resolve the toolchain-provided specs file path and will consider source files to be uncacheable if it is unable to read the specified specs file. Note that adding `--specs=*` to the ignore option list is not a problem because it is unlikely for the content of the toolchain libc spec file to change without the compiler executable itself changing. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the twister workflow such that ccache only uses remote Redis cache storage when available. The purpose of this to reduce the individual runner local disk IOPS requirement; thereby, reducing the overall load on the SAN. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit sets the twister timeout multiplier to 2, which effectively increases the default test timeout from 60 to 120 seconds, because the new cost-effective Zephyr runners may take longer to execute tests and the default timeout is not sufficient for some tests to complete. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit increases the default value of `ZTEST_TEST_DELAY_MS` from 3000 to 5000 milliseconds because the current value of 3000ms may not be sufficient for the hosts with lower CPU clock frequency (e.g. new Zephyr CI runners with cost-effective processors). Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit relaxes the idle event statistics test precision requirement for emulated QEMU targets because the cycle counts may be inaccurate when the host CPU is overloaded (e.g. when running tests with twister) and a high failure rate is observed for this test in the CI. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit increases the twister build job timeout from the default value of 6 hours to 24 hours because scheduled (weekly) build runs take longer than 6 hours to complete. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the bsim-tests workflow to use the new zephyr-runner v2 CI runner deployment. It also updates the workflow to use the `ci-repo-cache` Docker image, which includes the Zephyr repository cache, because the node level repository cache is no longer available in the zephyr-runner v2. Signed-off-by: Stephanos Ioannidis <[email protected]>
stephanosio
force-pushed
the
test_240311_1
branch
from
6ec239f
to
2245d93
Compare
stephanosio
force-pushed
the
test_240311_1
branch
from
2245d93
to
b2bde3a
Compare
stephanosio
force-pushed
the
test_240311_1
branch
from
b2bde3a
to
e73fa26
Compare
stephanosio
force-pushed
the
test_240311_1
branch
from
6109f34
to
ce53e74
Compare
This commit updates the doc-build workflow to use the new zephyr-runner v2 CI runner deployment. It also installs additional system packages that are not available by default in the zephyr-runner v2. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the bsim-tests workflow to use the new zephyr-runner v2 CI runner deployment. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the codecov workflow to run on all forks under the zephyrproject-rtos organisation. The purpose of this is mainly to simplify the process of testing of this workflow under the zephyr-testing repository. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the codecov workflow to use the new zephyr-runner v2 CI runner deployment. It also updates the workflow to use the `ci-repo-cache` Docker image, which includes the Zephyr repository cache, because the node level repository cache is no longer available in the zephyr-runner v2. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the codecov workflow to store ccache data in the zephyr-runner v2 node cache. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the codecov workflow to, when available, use Redis remote storage backend for the ccache compilation cache data. The Redis cache server is hosted in the Kubernetes cluster in which the zephyr-runner pods run -- the Redis remote storage backend will be ignored if the server is unavailable. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit adds the compiler `--specs=*` flag to the ccache ignore option list because ccache is unable to resolve the toolchain-provided specs file path and will consider source files to be uncacheable if it is unable to read the specified specs file. Note that adding `--specs=*` to the ignore option list is not a problem because it is unlikely for the content of the toolchain libc spec file to change without the compiler executable itself changing. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the codecov workflow such that ccache only uses remote Redis cache storage when available. The purpose of this to reduce the individual runner local disk IOPS requirement; thereby, reducing the overall load on the SAN. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the clang workflow to use the new zephyr-runner v2 CI runner deployment. It also updates the workflow to use the `ci-repo-cache` Docker image, which includes the Zephyr repository cache, because the node level repository cache is no longer available in the zephyr-runner v2. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the clang workflow to store ccache data in the zephyr-runner v2 node cache. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the clang workflow to, when available, use Redis remote storage backend for the ccache compilation cache data. The Redis cache server is hosted in the Kubernetes cluster in which the zephyr-runner pods run -- the Redis remote storage backend will be ignored if the server is unavailable. Signed-off-by: Stephanos Ioannidis <[email protected]>
This commit updates the clang workflow such that ccache only uses remote Redis cache storage when available. The purpose of this to reduce the individual runner local disk IOPS requirement; thereby, reducing the overall load on the SAN. Signed-off-by: Stephanos Ioannidis <[email protected]>
stephanosio
force-pushed
the
test_240311_1
branch
from
ce53e74
to
419784c
Compare
stephanosio
force-pushed
the
main
branch
3 times, most recently
from
e51249b
to
efce10c
Compare
stephanosio
force-pushed
the
main
branch
3 times, most recently
from
6838d95
to
b30ca16
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.