Home
last modified time | relevance | path

Searched +full:linux +full:- +full:container +full:- +full:ci (Results 1 – 25 of 162) sorted by relevance

1234567

/external/aws-crt-java/.github/workflows/
Dci.yml1 name: CI
5 branches-ignore:
6 - 'main'
7 - 'docs'
13 PACKAGE_NAME: aws-crt-java
14 LINUX_BASE_IMAGE: ubuntu-18-x64
15 RUN: ${{ github.run_id }}-${{ github.run_number }}
19 AWS_REGION: us-east-1
20 AWS_DEVICE_FARM_REGION: us-west-2 # Device Farm only available in us-west-2 region
23 linux-compat:
[all …]
/external/mesa3d/.gitlab-ci/container/debian/
Dandroid_build.sh5 # .gitlab-ci/image-tags.yml tags:
8 set -ex
16 apt-get install -y --no-remove "${EPHEMERAL[@]}"
20 curl -L --retry 4 -f --retry-all-errors --retry-delay 60 \
21 -o $ndk.zip https://dl.google.com/android/repository/$ndk-linux.zip
22 unzip -d / $ndk.zip "$ndk/toolchains/llvm/*"
25 # duplicate files. Turn them into hardlinks to save on container space.
26 rdfind -makehardlinks true -makeresultsfile false /${ndk}/
28 find /${ndk}/ -type f \( -iname '*clang-check*' -o -iname '*clang-tidy*' -o -iname '*lldb*' \) -exe…
30 sh .gitlab-ci/container/create-android-ndk-pc.sh /$ndk zlib.pc "" "-lz" "1.2.3" $ANDROID_SDK_VERSION
[all …]
Dx86_64_test-android.sh5 set -e
6 set -o xtrace
12 build-essential:native
15 config-package-dev
16 debhelper-compat
17 dpkg-dev
18 ninja-build
25 apt-get install -y --no-remove --no-install-recommends \
30 . .gitlab-ci/container/container_pre_build.sh
36 curl -L --retry 4 -f --retry-all-errors --retry-delay 60 \
[all …]
/external/mesa3d/.gitlab-ci/container/
Dlava_build.sh6 # .gitlab-ci/image-tags.yml tags:
9 set -e
10 set -o xtrace
17 S3_PATH="${S3_HOST}/mesa-lava/$1/${DISTRIBUTION_TAG}/${DEBIAN_ARCH}"
18 if curl -L --retry 4 -f --retry-delay 60 -s -X HEAD \
20 echo "Remote files are up-to-date, skip rebuilding them."
28 . .gitlab-ci/container/container_pre_build.sh
30 # Install rust, which we'll be using for deqp-runner. It will be cleaned up at the end.
31 . .gitlab-ci/container/build-rust.sh
34 GCC_ARCH="aarch64-linux-gnu"
[all …]
/external/mesa3d/docs/ci/
Dindex.rst4 GitLab CI
5 ---------
8 We use it to test merge requests (MRs) before merging them (pre-merge testing),
9 as well as post-merge testing, for everything that hits ``main``
11 and even then the MR CI runs in the forked repository, which might have been
14 The CI runs a number of tests, from trivial build-testing to complex GPU rendering:
16 - Build testing for a number of configurations and platforms
17 - Sanity checks (``meson test``)
18 - Most drivers are also tested using several test suites, such as the
19 `Vulkan/GL/GLES conformance test suite <https://github.com/KhronosGroup/VK-GL-CTS>`__,
[all …]
Dkernel.rst1 Upreving Linux Kernel
4 Occasionally, the GitLab CI needs a Linux Kernel update to enable new kernel
5 features, device drivers, bug fixes etc to CI jobs.
6 Kernel uprevs in GitLab CI are relatively simple, but prone to lots of
7 side-effects since many devices from different platforms are involved in the
11 -----------------
13 The Linux Kernel used in the GitLab CI is stored at the following repository:
14 https://gitlab.freedesktop.org/gfx-ci/linux
17 Linux mainline, that is why Mesa has its own kernel version which should be used
20 So, one should base the kernel uprev from the last tag used in the Mesa CI,
[all …]
/external/libffi/.travis/
Dbuild.sh3 set -x
5 if [ -z ${QEMU_CPU+x} ]; then
8 export SET_QEMU_CPU="-e QEMU_CPU=${QEMU_CPU}"
13 if test -z "$DOCKER"; then
24 …curl -u ${CFARM_AUTH} https://cfarm-test-libffi-libffi.apps.home.labdroid.net/test?host=${HOST}\&c…
27 echo $(tail build.log | grep '^==LOGFILE==' | cut -b13-)
29 curl -u ${CFARM_AUTH} "$(tail build.log | grep '^==LOGFILE==' | cut -b13-)" > libffi.log
33 ./rlgl e --id=$ID --policy=https://github.com/libffi/rlgl-policy.git libffi.log
40 ./configure ${HOST+--host=$HOST} ${CONFIGURE_OPTIONS}
43 make check RUNTESTFLAGS="-a $RUNTESTFLAGS"
[all …]
/external/perfetto/docs/design-docs/
Dcontinuous-integration.md1 # Perfetto CI design document
3 This CI is used on-top of (not in replacement of) AOSP's TreeHugger.
12 ![Architecture diagram](/docs/images/continuous-integration.png)
22 whole CI.
26 The Controller orchestrates the CI. It's the most trusted piece of the system.
32 It uses a non-privileged gmail account and has no meaningful voting power.
36 - It periodically (every 5s) polls Gerrit for CLs updated in the last 24h.
37 - It checks the list of CLs against the list of already known CLs in the DB.
38 - For each new CL it enqueues `N` new jobs in the database, one for each
39 configuration defined in [config.py](/infra/ci/config.py) (e.g. `linux-debug`,
[all …]
/external/ltp/.github/workflows/
Dci.yml1 # Copyright (c) 2021-2023 Petr Vorel <pvorel@suse.cz>
3 name: "CI: docker based builds"
11 runs-on: ubuntu-latest
14 fail-fast: false
18 - container: "debian:stable"
24 - container: "debian:stable"
27 CC: powerpc64le-linux-gnu-gcc
30 VARIANT: cross-compile
32 - container: "debian:stable"
35 CC: aarch64-linux-gnu-gcc
[all …]
/external/rust/crates/grpcio-sys/grpc/third_party/cares/cares/
D.travis.yml7 - cmake
8 - lcov
9 - clang-tools-7
10 - valgrind
14 - os: linux
17 - os: linux
20 - os: linux
23 - os: linux
26 - os: linux
29 - os: linux
[all …]
/external/mesa3d/.gitlab-ci/container/alpine/
Dx86_64_build.sh5 # .gitlab-ci/image-tags.yml tags:
8 set -e
9 set -o xtrace
21 clang16-dev
23 clang-dev
32 linux-headers
33 llvm16-static
34 llvm16-dev
36 expat-dev
37 elfutils-dev
[all …]
/external/mesa3d/.gitlab-ci/windows/
DREADME.md1 # Native Windows GitLab CI builds
3 Unlike Linux, Windows cannot reuse the freedesktop ci-templates as they exist
4 as we do not have Podman, Skopeo, or even Docker-in-Docker builds available
7 We still reuse the same model: build a base container with the core operating
8 system and infrequently-changed build dependencies, then execute Mesa builds
9 only inside that base container. This is open-coded in PowerShell scripts.
11 ## Base container build
13 The base container build job executes the `mesa_container.ps1` script which
14 reproduces the ci-templates behaviour. It looks for the registry image in
20 container to fetch and install all build dependencies. This includes Visual
[all …]
/external/cronet/third_party/libc++/src/utils/ci/
DDockerfile1 #===----------------------------------------------------------------------===##
5 # SPDX-License-Identifier: Apache-2.0 WITH LLVM-exception
7 #===----------------------------------------------------------------------===##
17 # docker compose build buildkite-builder
18 # docker compose push buildkite-builder
22 # ghcr.io/libcxx/buildkite-builder
23 # ghcr.io/libcxx/actions-builder
24 # ghcr.io/libcxx/android-buildkite-builder
28 # ===----------------------------------------------------------------------===##
30 # ===----------------------------------------------------------------------===##
[all …]
Drun-buildbot-container3 # This script starts a shell in a container running the libc++ build bot Docker
4 # image. That image emulates the environment used by libc++'s Linux builders on
8 # `run-buildbot` script.
11 # monorepo will be mounted as `/llvm` inside the container. Be careful, the
12 # state in `/llvm` is shared between the container and the host machine, which
13 # is useful for editing files on the host machine and re-running the build bot
14 # in the container.
16 # If you are on Linux you will likely not be able to write to the mount because
17 # the user in the container doesn't have permissions to do so.
19 # the container or add this flag to run the container as your local user IDs:
[all …]
/external/sdv/vsomeip/third_party/boost/concept_check/.github/workflows/
Dci.yml1 name: GitHub Actions CI
7 - master
8 - develop
9 - githubactions*
10 - feature/**
11 - fix/**
12 - pr/**
20 fail-fast: false
23 - name: "B2_TOOLSET=gcc-4.8 B2_CXXSTD=03,11 Job 0"
25 packages: "g++-4.8"
[all …]
/external/python/pyfakefs/
DREADME.md1-dev/pyfakefs/workflows/Testsuite/badge.svg) [![Documentation Status](https://readthedocs.org/proj…
9 Pyfakefs creates a new empty in-memory file system at each test start, which replaces
10 the real filesystem during the test. Think of pyfakefs as making a per-test temporary
20 pyfakefs works with current versions of Linux, Windows and macOS.
27 * The [Release documentation](https://pytest-pyfakefs.readthedocs.io/en/stable)
31 * The [Development documentation](https://pytest-pyfakefs.readthedocs.io/en/latest)
33 * The [Release 3.7 documentation](https://pytest-pyfakefs.readthedocs.io/en/v3.7.2/)
36 * The [Release Notes](https://github.com/pytest-dev/pyfakefs/blob/main/CHANGES.md)
42 [usage documentation](https://pytest-pyfakefs.readthedocs.io/en/latest/usage.html)
47 Apart from automatically mocking most file-system functions, pyfakefs
[all …]
/external/mesa3d/.gitlab-ci/test/
Dgitlab-ci.yml7 - !reference [default, before_script]
9 - rm -rf install
10 - tar -xf artifacts/install.tar
11 - section_start ldd_section "Checking ldd on driver build"
12 - LD_LIBRARY_PATH=install/lib find install/lib -name "*.so" -print -exec ldd {} \;
13 - section_end ldd_section
18 - results/
20 - !reference [.never-post-merge-rules, rules]
22 .formatting-check:
25 stage: code-validation
[all …]
/external/cpu_features/cmake/ci/
DREADME.md5 * You are independent of third party CI runner config
6 (e.g. [github action virtual-environnments](https://github.com/actions/virtual-environments)).
7 * You can run it locally on your linux system.
8 * Most CI provide runners with docker and Makefile installed.
11 * Only GNU/Linux distro supported.
21 make --directory=cmake/ci
25 For example to test mips32 inside an container:
/external/cronet/third_party/cpu_features/src/cmake/ci/
DREADME.md5 * You are independent of third party CI runner config
6 (e.g. [github action virtual-environnments](https://github.com/actions/virtual-environments)).
7 * You can run it locally on your linux system.
8 * Most CI provide runners with docker and Makefile installed.
11 * Only GNU/Linux distro supported.
21 make --directory=cmake/ci
25 For example to test mips32 inside an container:
/external/ltp/
DREADME.md1 Linux Test Project
4 Linux Test Project is a joint project started by SGI, OSDL and Bull developed
7 reliability, robustness, and stability of Linux.
9 The LTP testsuite contains a collection of tools for testing the Linux kernel
10 and related features. Our goal is to improve the Linux kernel and system
14 Project pages are located at: http://linux-test-project.github.io/
17 https://github.com/linux-test-project/ltp/releases
20 http://lists.linux.it/listinfo/ltp
28 https://github.com/linux-test-project/ltp
45 If you have git, autoconf, automake, m4, pkgconf / pkg-config, libc headers,
[all …]
/external/sdv/vsomeip/third_party/boost/date_time/.github/workflows/
Dci.yml1 name: GitHub Actions CI
7 - master
8 - develop
9 - githubactions*
10 - feature/**
11 - fix/**
12 - pr/**
20 fail-fast: false
23 - name: "B2_TOOLSET=gcc-4.8 B2_CXXSTD=03,11 BOOST_DATE Job 0"
25 packages: "g++-4.8"
[all …]
/external/crosvm/infra/recipes/build_linux.expected/
Dbuild_x86_64.json6 "--list-checks",
15 "name": "crosvm/crosvm:ci"
31 "--no-interactive",
32 "--verbose",
34 "--no-delta",
44 "name": "crosvm/crosvm:ci"
60 "--no-interactive",
61 "--verbose",
63 "--no-delta",
73 "name": "crosvm/crosvm:ci"
[all …]
/external/mesa3d/src/gfxstream/codegen/vulkan/vulkan-docs-next/scripts/
DrunDocker2 # Copyright 2022-2023 The Khronos Group Inc.
3 # SPDX-License-Identifier: Apache-2.0
5 # runDocker - run the Khronos `asciidoctor-spec` Docker image with a local
8 # The following command-line tools are required to run this script:
10 # These are all normal Linux developer tools except for 'docker' itself.
16 # Get SHA256 of the asciidoctor-spec image build used by CI.
17 image=`grep -m 1 khronosgroup/docker-images@sha256: $repopath/.gitlab-ci.yml | \
20 uid=`id -u`
21 gid=`id -g`
24 # --user causes Docker to run as the specified UID:GID instead of as root
[all …]
/external/mesa3d/.gitlab-ci/
Dlava-gitlab-ci.yml2 DISTRIBUTION_TAG: "2020-11-09-kmod-fix"
5 stage: container-2
7 - .ci-run-policy
10 …_URL: "https://gitlab.freedesktop.org/tomeu/linux/-/archive/v5.10-rc2-for-mesa-ci/linux-v5.10-rc2-
14 - .gitlab-ci/container/lava_build.sh
18 - .use-x86_build-base
19 - .kernel+rootfs
20 image: "$CI_REGISTRY_IMAGE/debian/x86_build-base:$BASE_TAG"
26 - .use-arm_build
27 - .kernel+rootfs
[all …]
/external/libusb/.github/workflows/
Dlinux.yml1 name: linux
12 runs-on: ubuntu-latest
16 # Checks-out your repository under $GITHUB_WORKSPACE, so your job
18 - uses: actions/checkout@v3
20 - name: setup prerequisites
23 sudo apt install autoconf automake libtool libudev-dev m4
25 - name: bootstrap
28 - name: netlink
29 # Disable tests for netlink as it doesn't seem to work in the CI environment.
30 run: .private/ci-build.sh --build-dir build-netlink --no-test -- --disable-udev
[all …]

1234567