c4e3267868
In order to validate drm/msm register definition files against schema, reuse the nodebugfs build step. The validation entry is guarded by the EXPERT Kconfig option and we don't want to enable that option for all the builds. Reviewed-by: Abhinav Kumar <quic_abhinavk@quicinc.com> Acked-by: Helen Koike <helen.koike@collabora.com> Link: https://patchwork.freedesktop.org/patch/msgid/20240503-fd-fix-lxml-v2-2-f80a60ce21a1@linaro.org Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
113 lines
2.8 KiB
YAML
113 lines
2.8 KiB
YAML
.build:
|
|
extends:
|
|
- .build-rules
|
|
- .container+build-rules
|
|
stage: build
|
|
artifacts:
|
|
paths:
|
|
- artifacts
|
|
script:
|
|
- FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build.sh
|
|
|
|
.build:arm32:
|
|
extends:
|
|
- .build
|
|
- .use-debian/arm64_build
|
|
tags:
|
|
- aarch64
|
|
variables:
|
|
DEFCONFIG: "arch/arm/configs/multi_v7_defconfig"
|
|
KERNEL_IMAGE_NAME: "zImage"
|
|
KERNEL_ARCH: "arm"
|
|
|
|
.build:arm64:
|
|
extends:
|
|
- .build
|
|
- .use-debian/arm64_build
|
|
tags:
|
|
- aarch64
|
|
variables:
|
|
DEFCONFIG: "arch/arm64/configs/defconfig"
|
|
KERNEL_IMAGE_NAME: "Image"
|
|
KERNEL_ARCH: "arm64"
|
|
|
|
.build:x86_64:
|
|
extends:
|
|
- .build
|
|
- .use-debian/x86_64_build
|
|
variables:
|
|
DEFCONFIG: "arch/x86/configs/x86_64_defconfig"
|
|
KERNEL_IMAGE_NAME: "bzImage"
|
|
KERNEL_ARCH: "x86_64"
|
|
|
|
|
|
# Build IGT for testing on devices
|
|
|
|
igt:arm32:
|
|
extends: .build:arm32
|
|
script:
|
|
- FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build-igt.sh
|
|
|
|
igt:arm64:
|
|
extends: .build:arm64
|
|
script:
|
|
- FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build-igt.sh
|
|
|
|
igt:x86_64:
|
|
extends: .build:x86_64
|
|
script:
|
|
- FDO_CI_CONCURRENT=${FDO_CI_CONCURRENT} bash drivers/gpu/drm/ci/build-igt.sh
|
|
|
|
# Build kernels for testing on devices
|
|
|
|
testing:arm32:
|
|
extends: .build:arm32
|
|
variables:
|
|
# Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
|
|
# PROVE_LOCKING and KASAN as of 5.17.
|
|
#
|
|
# db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
|
|
# becoming too big for their bootloaders.
|
|
ENABLE_KCONFIGS: "PROVE_LOCKING DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT"
|
|
UPLOAD_TO_MINIO: 1
|
|
MERGE_FRAGMENT: arm.config
|
|
|
|
testing:arm64:
|
|
extends: .build:arm64
|
|
variables:
|
|
# Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
|
|
# PROVE_LOCKING and KASAN as of 5.17.
|
|
#
|
|
# db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
|
|
# becoming too big for their bootloaders.
|
|
ENABLE_KCONFIGS: "PROVE_LOCKING DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT"
|
|
UPLOAD_TO_MINIO: 1
|
|
MERGE_FRAGMENT: arm64.config
|
|
|
|
testing:x86_64:
|
|
extends: .build:x86_64
|
|
variables:
|
|
# Would be good to have DEBUG_KMEMLEAK, but it doesn't work well with any of
|
|
# PROVE_LOCKING and KASAN as of 5.17.
|
|
#
|
|
# db410c and db820c don't boot with KASAN_INLINE, probably due to the kernel
|
|
# becoming too big for their bootloaders.
|
|
ENABLE_KCONFIGS: "PROVE_LOCKING DEBUG_INFO_DWARF_TOOLCHAIN_DEFAULT"
|
|
UPLOAD_TO_MINIO: 1
|
|
MERGE_FRAGMENT: x86_64.config
|
|
|
|
|
|
# Jobs for build-testing different configurations
|
|
|
|
build:arm32:
|
|
extends: .build:arm32
|
|
|
|
build-nodebugfs:arm64:
|
|
extends: .build:arm64
|
|
variables:
|
|
DISABLE_KCONFIGS: "DEBUG_FS"
|
|
ENABLE_KCONFIGS: "EXPERT DRM_MSM_VALIDATE_XML"
|
|
|
|
build:x86_64:
|
|
extends: .build:x86_64
|