- Jul 04, 2024
-
-
Signed-off-by:
Jiaxun Yang <jiaxun.yang@flygoat.com>
-
Tom Rini authored
Both GitLab and Azure (and other CI systems) have native support for displaying JUnitXML test report results. The pytest framework that we use can generate these reports. Change our CI tests so that they will generate these reports and then have the respective CI platform pick them up. We write to different locations because of where each CI is (and isn't) able to easily pass things along. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Mar 15, 2024
-
-
Tom Rini authored
This moves us to our latest container image, which is now based on the current "Jammy" tag. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Mar 14, 2024
-
-
Tom Rini authored
Currently, llvm-17 is the stable release. Update our container and CI to fetch and use that. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Mar 01, 2024
-
-
Since devicetree-rebasing is an external repo with its own coding style, exclude it from Azure and gitlab CI CONFIG checks. Reviewed-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Ilias Apalodimas <ilias.apalodimas@linaro.org> Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Sumit Garg <sumit.garg@linaro.org>
-
- Feb 27, 2024
-
-
Tom Rini authored
This moves us to our latest container image, which is now based on the current "Jammy" tag. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
Instead of downloading coreboot binaries from a Google drive location, use the ones we have built ourselves. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Jan 18, 2024
-
-
Tom Rini authored
Move to the latest "Jammy" tag from Ubuntu. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Nov 07, 2023
-
-
Tom Rini authored
The primary motivation for having a sandbox without LTO build in CI is to ensure that we don't have that option break. We now have the ability to run tests of specific options being enabled/disabled, so drop the parts of CI that build and test that configuration specifically and add a build test instead. We still test that "NO_LTO=1" rather than editing the config file works via the ftrace tests. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Nov 02, 2023
-
-
Heinrich Schuchardt authored
Use the most recent upstream release of OpenSBI for CI testing. Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Leo Yu-Chi Liang <ycliang@andestech.com>
-
- Oct 23, 2023
-
-
Tom Rini authored
At this point we have all of the defconfigs maintained again, so re-enable the check to prevent further regressions. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Oct 18, 2023
-
-
This add some basic functions to create images, and a test for said functions. This is not intended to be a test of the image parsing functions, but rather a framework for creating minimal images for testing load methods. That said, it does do an OK job at finding bugs in the image parsing directly. Since we have two methods for loading/parsing FIT images, add LOAD_FIT_FULL as a separate CI run. Signed-off-by:
Sean Anderson <seanga2@gmail.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Sep 30, 2023
-
-
Out-of-tree users could run an out-of-tree CI with limited coverage, however it is convenient to be able to run the upstream CI from time to time. To enable that we would need to change job rules to be able to run on any GitLab event. Excerpt from GitLab documentation: > Jobs with no rules default to except: merge_requests Signed-off-by:
Andrejs Cainikovs <andrejs.cainikovs@toradex.com> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
- Sep 06, 2023
-
-
Test both 32bit and 64bit sandbox boards in CI. Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
- We have added more TODO/etc comments since this task was created and never focused on removing them. - The output of sloccount isn't preserved or looked at, and if desired should be in the release stats pages instead somehow. - The results of cppcheck aren't investigated and require modeling work to be useful to start with. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
These jobs are to confirm specific build targets, on a Linux host. We can safely combine these two build tests, with a make mrproper in between. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Sep 05, 2023
-
-
Tom Rini authored
This platform is behind on migrations (it is the sole user of the oldest legacy version of the USB gadget stack and is long overdue for migration) and with Pali no longer being a maintainer, we remove this platform. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 29, 2023
-
-
When running the trace test on the sandbox platform, the current size of 16MiB is no longer large enough for capturing the entire trace history, and results in truncation. Use a size of 32MiB for the trace buffer on the sandbox platform while running the trace test. Signed-off-by:
Sughosh Ganu <sughosh.ganu@linaro.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Aug 26, 2023
-
-
Tom Rini authored
Move to the latest "Jammy" tag from Ubuntu. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
Tom Rini authored
The latest kernel.org toolchains for gcc are now 13.2.0, so upgrade to that. Reviewed-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Aug 17, 2023
-
-
Tom Rini authored
When running tools for various tests use the tools-only build rather than sandbox_spl. We used sandbox_spl here for historical reasons that are no longer true. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Use a recent coreboot build for this test. The coreboot commit is: 6f5ead14b4 mb/google/nissa/var/joxer: Update eMMC DLL settings This is build with default settings, i.e. QEMU x86 i440fx/piix4 Add some documentation as to how to update it next time. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jul 24, 2023
-
-
Simon Glass authored
Rather than using the -R option to get this report as a side effect, add a dedicated option for it. Disable CI for now as there are some missing maintainers, unfortunately. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Jul 21, 2023
-
-
Tom Rini authored
Now that buildman has a requirements.txt file we need to make use of it. Reviewed-by:
Simon Glass <sjg@chromium.org> [n-francis@ti.com: Adding missing command from .azure-pipelines.yml] Signed-off-by:
Neha Malcom Francis <n-francis@ti.com> Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Jul 20, 2023
-
-
Tom Rini authored
It is not uncommon for some of the QEMU-based jobs to fail not because of a code issue but rather because of a timing issue or similar problem that is out of our control. Make use of the keywords that Azure and GitLab provide so that we will automatically re-run these when they fail 2 times. If they fail that often it is likely we have found a real issue to investigate. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
Move to the latest "Jammy" tag from Ubuntu. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
Tom Rini authored
As this is the current version of the public cross toolchains we use, upgrade to this now. Suggested-by:
Alexey Brodkin <Alexey.Brodkin@synopsys.com> Signed-off-by:
Tom Rini <trini@konsulko.com> Acked-by:
Alexey Brodkin <abrodkin@synopsys.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Jul 06, 2023
-
-
Bin Meng authored
Use the latest OpenSBI v1.2 release binaries for the RISC-V CI. Signed-off-by:
Bin Meng <bmeng@tinylab.org> Reviewed-by:
Leo Yu-Chi Liang <ycliang@andestech.com>
-
- May 04, 2023
-
-
Heinrich Schuchardt authored
We do not want to merge documentation that produces Sphinx warnings. scripts/kernel-doc uses environment variable KDOC_WERROR to determine if warnings should be treated as errors. Reported-by:
Tom Rini <trini@konsulko.com> Signed-off-by:
Heinrich Schuchardt <heinrich.schuchardt@canonical.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Apr 15, 2023
-
-
Add M5208EVBE board to CI. This does not use default config due to limitations of QEMU emulation, instead the timer is switched from DMA timer to PIT timer and RAMBAR accesses are inhibited. Local QEMU launch command is as follows: $ qemu-system-m68k -nographic -machine mcf5208evb -cpu m5208 -bios u-boot.bin Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org> Acked-by:
Angelo Dureghello <angelo@kernel-space.org>
-
- Apr 04, 2023
-
-
Tom Rini authored
As this is now the stable release, move to using that now for our tests. Signed-off-by:
Tom Rini <trini@konsulko.com> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Apr 02, 2023
-
-
Simon Glass authored
This is actually skipped at present due to the condition in the file. Fix this by running all vpl tests. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Mar 22, 2023
-
-
To conserve bandwidth and potentially avoid rate limits, allow a local mirror of Docker Hub to be specified globally. The default value is unchanged. Signed-off-by:
Peter Hoyes <Peter.Hoyes@arm.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
The default behavior of Gitlab runners is to only run jobs which match the configured tag, although there is an option to run untagged jobs [1]. To support running the CI in more complex environments where different types of runners may be present that support different tags, allow the DEFAULT_TAG for all jobs in the pipeline to be set globally using an environment variable. An empty default value is provided to retain support for untagged runners. [1] https://docs.gitlab.com/ee/ci/runners/configure_runners.html#use-tags-to-control-which-jobs-a-runner-can-run Signed-off-by:
Peter Hoyes <Peter.Hoyes@arm.com> Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com>
-
Copy build artifacts for all test.py tests, so they show up in artifacts storage for later inspection. The test.py tests output in CI is basically useless, but it is far more useful in the html output for analysis and debugging. Reviewed-by:
Simon Glass <sjg@chromium.org> Reviewed-by:
Tom Rini <trini@konsulko.com> Suggested-by:
Simon Glass <sjg@chromium.org> Signed-off-by:
Marek Vasut <marek.vasut+renesas@mailbox.org>
-
Tom Rini authored
Update to using the latest "Jammy" tag as our base. Signed-off-by:
Tom Rini <trini@konsulko.com>
-
- Mar 08, 2023
-
-
Simon Glass authored
Add a simple check that the PyPi packages can be built. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Feb 24, 2023
-
-
Now that the Dockerfile creates images which have the binaries we require included, have CI make symlinks for them and update the existing script to support this. Signed-off-by:
Tom Rini <trini@konsulko.com> Signed-off-by:
Pali Rohár <pali@kernel.org> Reviewed-by:
Simon Glass <sjg@chromium.org>
-
- Feb 14, 2023
-
-
Simon Glass authored
These should not be used anymore. Add a check to ensure they don't creek back into U-Boot. Use bootph-... instead. Signed-off-by:
Simon Glass <sjg@chromium.org>
-
- Feb 11, 2023
-
-
Tom Rini authored
Move to the latest tag for "Jammy" and rebuild the containers. Signed-off-by:
Tom Rini <trini@konsulko.com>
-