Bump to v0.10.1 Docker Image to get access to SDK 0.11.0-alpha8,
Ubuntu 18.04, gcc-9, clang-9, and python 3.6.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Update to CI image 0.9.1 to have pylint installed. Bump ci-tools sha
that re-enables running the pylint test.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Update SDK version to 0.10.2 to pick up new qemu and risc-v support.
Use Docker image 0.8.1 that includes an install of that SDK version.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
The main change is the elimination of the bootstrapper, a design flaw
/ misfeature.
Update the documentation to be compatible with the 0.6.x releases as
well. This has to be done atomically, as there were incompatible
changes. Make use of the versionchanged and versionadded directives
to begin keeping track of how these APIs are evolving.
(Note that west 0.6.0 will remain compatible with the extension
commands in Zephyr v1.14 LTS as long as that is still alive. This
change is targeted towards Zephyr 2.0 users.)
This requires a bump in the shippable container and allows us to
simplify the west_commands test procedure.
Signed-off-by: Marti Bolivar <marti.bolivar@nordicsemi.no>
CI always runs after new PRs are merged into master. Report failures to
mailing list to get more attention if master fails to build.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Use latest docker image with renode and an update to the SDK pre-release
0.10.0-rc3 (not used by default).
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
In order to be able to merge the topic branch, we require a few
fixes to CI.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Signed-off-by: Carles Cufi <carles.cufi@nordicsemi.no>
After some discussion, we've decided to ensure that shippable runs
with the latest west bootstrapper on PyPI by making that happen in
.shippable.yml for now, rather than updating our CI container.
Signed-off-by: Marti Bolivar <marti@foundries.io>
Added a missing option in run_ci.sh to control the placement of the
xml results file. (Before it was just propagated thru the enviroment)
+
Changed .shippable to use this option when callign it.
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
- Has cmake 3.8.2 that matches min. required version
- Has west pre-installed
- Uses latest python dependencies from scripts/requirements.txt
- remove ISSM toolchain
- added scancode-toolkit for scanning licenses and copyrights.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Compile and run the tests avaliable in bsim_bt
and collect the coverage results into the coverage report.
Also, detect if bsim's component folder already contains the
nRF52 HW models, and if it does instead of trying to fetch
them again (which will fail) check that the right versio is
present. This should ease testing locally.
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
move CI scripting to a dedicated script. For example, to simulate what
is run in CI when a pull request is submitted:
./scripts/ci/run_ci.sh -b master -r upstream -p
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Use the docker image which has BabbleSim precompiled
Fetch the NRF52 hardware models required by the nrf52_bsim board
and compile them.
Collect the coverage report from the nrf52_bsim board
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
CI is failing sporadically with a corrupted
ToolchainCapabilityDatabase.cmake file.
To gain insight into how the file is corrupted we print it to the log.
Signed-off-by: Sebastian Bøe <sebastian.boe@nordicsemi.no>
Ninja is much faster than make in the context of CI. The issues with
ninja and parallel builds has been partially resolved in sanitycheck.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Disable cache which increases total execution time without any visible
benefits in the current setup. Need to revisit how we can better use
ccache for CI builds.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Go back to 5 minions, 7 minions is increasing the queue significantly
without any improvements visible in total execution time.
This was changed to 7 to address PRs changing many boards and tests,
which is the exception and not the rule.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Since builds have drastically increased in time, we end up timing out CI
if we have a larger number of tests to build. Try bumping up the number
of slaves to 7 and see if that helps.
Signed-off-by: Kumar Gala <kumar.gala@linaro.org>
Now that the native_posix board is not built by default
with coverage, and that sanitycheck has an option to set it to,
let's explicitly tell sanitycheck to build unit tests and
for the native_board with coverage enabled.
Signed-off-by: Alberto Escolar Piedras <alpi@oticon.com>
Tests and samples are not part of the Zephyr code and should not
contribute to the final coverage reports. This will allow us to get
exact numbers about what is being covered or not in CI without the need
to go and look into files individually.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
ext/ code is not always entirely used or tested from Zephyr, we use only
subset of the features and available code. To get accurate coverage
data, exclude the files in ext/ from the coverage report.
Signed-off-by: Anas Nashif <anas.nashif@intel.com>
Anas Nashif