[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [PATCH v2 01/10] automation: Use custom build jobs when extra config options are needed


  • To: xen-devel@xxxxxxxxxxxxxxxxxxxx
  • From: Ayan Kumar Halder <ayankuma@xxxxxxx>
  • Date: Mon, 26 Sep 2022 15:42:56 +0100
  • Arc-authentication-results: i=1; mx.microsoft.com 1; spf=pass smtp.mailfrom=amd.com; dmarc=pass action=none header.from=amd.com; dkim=pass header.d=amd.com; arc=none
  • Arc-message-signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=microsoft.com; s=arcselector9901; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version:X-MS-Exchange-AntiSpam-MessageData-ChunkCount:X-MS-Exchange-AntiSpam-MessageData-0:X-MS-Exchange-AntiSpam-MessageData-1; bh=3ZMY5OwHwl2FddXGTHXtDteiRYwUkwfAWOIZsQT0Vok=; b=WQ0rQL3TW3oY+PBMbxKezgpSUgQezzXm7JjsKrDn/ZY6TYTL6jn68Waec03BtQn5QpJH2KD0Lt34xfEbyuELTMcSHX8QsJJpR3IzMXbrQGW/1dfv0UsZCsDCOB2mP6s/Vj/rx8YtJg7+JhHF2nkZF577aNeJ1DDIXxB/DAkcfOC5stp3jU8pfnxsE7ggaC4gczhU1sSBcethLpljZlfW7DBC70B1/G8PE8emp4dUaxA/SgTtW1rZb8r7tYGk8j9TY4ayPhxjgFMfsn8NS5cWg3yHXu4SnI/yN+X6eUdbyi9aJLNlG29SAB+v46ElARKrb7F7UOHjKa9RY0HhwME9cg==
  • Arc-seal: i=1; a=rsa-sha256; s=arcselector9901; d=microsoft.com; cv=none; b=gscYOrx5QE02p9GOMftJ3A/Ns56RnA5y32xmdVQsp6ZB6ZhPgiedjS1qfTf79qs7e7RTPRZJAvPWAESioATBNYUtfpHsXxzdd5bY3lpIEMHXUBbo28pwTfVvsZvLLVubIqc9qewmjldEc0P4lEsZyiaOiJpunlEYAlBUj+hsAXrvcxIzmc1elYpIYg/A5k3O5Gd1f1XneWzwf49zgvLZNNmP8rd7Bp8Qkz2k7cdo4kprQK/NJGKqx/4pU3M3qmVHSiTKBJpakxIVUDVHr1bkPajvpFm/innBakFDNQCogu3xZ2o8h45YqDGiuOhwEVu3M/QqoJDb3rWgorbShgKOaA==
  • Authentication-results: dkim=none (message not signed) header.d=none;dmarc=none action=none header.from=amd.com;
  • Delivery-date: Mon, 26 Sep 2022 14:43:17 +0000
  • List-id: Xen developer discussion <xen-devel.lists.xenproject.org>


On 26/09/2022 12:04, Michal Orzel wrote:
Currently, all the arm64 defconfig build jobs, regardless of the
container used, end up building Xen with the extra config options
specified in the main build script (e.g. CONFIG_EXPERT,
CONFIG_STATIC_MEMORY). Because these options are only needed for
specific test jobs, the current behavior of the CI is incorrect
as we add the extra options to all the defconfig builds. This means
that on arm64 there is not a single job performing proper defconfig build.

To fix this issue, add custom build jobs each time there is a need for
building Xen with additional config options. Introduce EXTRA_XEN_CONFIG
variable to be used by these jobs to store the required options. This
variable will be then read by the main build script to modify the .config
file. This will also help users to understand what is needed to run specific
test.

Signed-off-by: Michal Orzel <michal.orzel@xxxxxxx>
Reviewed-by: Ayan Kumar halder <ayankuma@xxxxxxx>
---
This patch is supposed to be merged for 4.17. The release manager agreed
on that.

Changes in v2:
- replace [ with [[ to be consistent with other ifs in build script
---
  automation/gitlab-ci/build.yaml | 15 +++++++++++++++
  automation/gitlab-ci/test.yaml  |  4 ++--
  automation/scripts/build        |  8 ++------
  3 files changed, 19 insertions(+), 8 deletions(-)

diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index 720ce6e07ba0..a39ed72aac6d 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -566,6 +566,21 @@ alpine-3.12-gcc-debug-arm64:
    variables:
      CONTAINER: alpine:3.12-arm64v8
+alpine-3.12-gcc-arm64-staticmem:
+  extends: .gcc-arm64-build
+  variables:
+    CONTAINER: alpine:3.12-arm64v8
+    EXTRA_XEN_CONFIG: |
+      CONFIG_EXPERT=y
+      CONFIG_UNSUPPORTED=y
+      CONFIG_STATIC_MEMORY=y
+
+alpine-3.12-gcc-arm64-boot-cpupools:
+  extends: .gcc-arm64-build
+  variables:
+    CONTAINER: alpine:3.12-arm64v8
+    EXTRA_XEN_CONFIG: |
+      CONFIG_BOOT_TIME_CPUPOOLS=y
## Test artifacts common diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
index d899b3bdbf7a..4f96e6e322de 100644
--- a/automation/gitlab-ci/test.yaml
+++ b/automation/gitlab-ci/test.yaml
@@ -88,7 +88,7 @@ qemu-smoke-arm64-gcc-staticmem:
    script:
      - ./automation/scripts/qemu-smoke-arm64.sh static-mem 2>&1 | tee 
qemu-smoke-arm64.log
    needs:
-    - alpine-3.12-gcc-arm64
+    - alpine-3.12-gcc-arm64-staticmem
      - alpine-3.12-arm64-rootfs-export
      - kernel-5.19-arm64-export
      - qemu-system-aarch64-6.0.0-arm64-export
@@ -107,7 +107,7 @@ qemu-smoke-arm64-gcc-boot-cpupools:
    script:
      - ./automation/scripts/qemu-smoke-arm64.sh boot-cpupools 2>&1 | tee 
qemu-smoke-arm64.log
    needs:
-    - alpine-3.12-gcc-arm64
+    - alpine-3.12-gcc-arm64-boot-cpupools
      - alpine-3.12-arm64-rootfs-export
      - kernel-5.19-arm64-export
      - qemu-system-aarch64-6.0.0-arm64-export
diff --git a/automation/scripts/build b/automation/scripts/build
index 2f15ab3198e6..bcfa6838f0bb 100755
--- a/automation/scripts/build
+++ b/automation/scripts/build
@@ -15,12 +15,8 @@ if [[ "${RANDCONFIG}" == "y" ]]; then
      make -j$(nproc) -C xen KCONFIG_ALLCONFIG=tools/kconfig/allrandom.config 
randconfig
      hypervisor_only="y"
  else
-    if [[ "${XEN_TARGET_ARCH}" = "arm64" ]]; then
-        echo "
-CONFIG_EXPERT=y
-CONFIG_UNSUPPORTED=y
-CONFIG_STATIC_MEMORY=y
-CONFIG_BOOT_TIME_CPUPOOLS=y" > xen/.config
+    if [[ -n "${EXTRA_XEN_CONFIG}" ]]; then
+        echo "${EXTRA_XEN_CONFIG}" > xen/.config
          make -j$(nproc) -C xen olddefconfig
      else
          make -j$(nproc) -C xen defconfig



 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.