All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stefano Stabellini <sstabellini@kernel.org>
To: Andrew Cooper <andrew.cooper3@citrix.com>
Cc: Xen-devel <xen-devel@lists.xenproject.org>,
	 Doug Goldstein <cardoe@cardoe.com>,
	 Stefano Stabellini <sstabellini@kernel.org>,
	 Anthony PERARD <anthony.perard@citrix.com>,
	 Michal Orzel <michal.orzel@amd.com>,
	 Oleksii Kurochko <oleksii.kurochko@gmail.com>
Subject: Re: [PATCH 1/6] CI: Drop automation/configs/
Date: Tue, 3 Jan 2023 17:08:01 -0800 (PST)	[thread overview]
Message-ID: <alpine.DEB.2.22.394.2301031707540.4079@ubuntu-linux-20-04-desktop> (raw)
In-Reply-To: <20221230003848.3241-2-andrew.cooper3@citrix.com>

On Fri, 30 Dec 2022, Andrew Cooper wrote:
> Having 3 extra hypervisor builds on the end of a full build is deeply
> confusing to debug if one of them fails, because the .config file presented in
> the artefacts is not the one which caused a build failure.  Also, the log
> tends to be truncated in the UI.
> 
> PV-only is tested as part of PV-Shim in a full build anyway, so doesn't need
> repeating.  HVM-only and neither will come up frequently in randconfig, so
> drop all the logic here to simplify things.
> 
> Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>

Reviewed-by: Stefano Stabellini <sstabellini@kernel.org>


> ---
> CC: Doug Goldstein <cardoe@cardoe.com>
> CC: Stefano Stabellini <sstabellini@kernel.org>
> CC: Anthony PERARD <anthony.perard@citrix.com>
> CC: Michal Orzel <michal.orzel@amd.com>
> CC: Oleksii Kurochko <oleksii.kurochko@gmail.com>
> ---
>  automation/configs/x86/hvm_only_config  |  3 ---
>  automation/configs/x86/no_hvm_pv_config |  3 ---
>  automation/configs/x86/pv_only_config   |  3 ---
>  automation/scripts/build                | 21 ---------------------
>  4 files changed, 30 deletions(-)
>  delete mode 100644 automation/configs/x86/hvm_only_config
>  delete mode 100644 automation/configs/x86/no_hvm_pv_config
>  delete mode 100644 automation/configs/x86/pv_only_config
> 
> diff --git a/automation/configs/x86/hvm_only_config b/automation/configs/x86/hvm_only_config
> deleted file mode 100644
> index 9efbddd5353b..000000000000
> --- a/automation/configs/x86/hvm_only_config
> +++ /dev/null
> @@ -1,3 +0,0 @@
> -CONFIG_HVM=y
> -# CONFIG_PV is not set
> -# CONFIG_DEBUG is not set
> diff --git a/automation/configs/x86/no_hvm_pv_config b/automation/configs/x86/no_hvm_pv_config
> deleted file mode 100644
> index 0bf6a8e46818..000000000000
> --- a/automation/configs/x86/no_hvm_pv_config
> +++ /dev/null
> @@ -1,3 +0,0 @@
> -# CONFIG_HVM is not set
> -# CONFIG_PV is not set
> -# CONFIG_DEBUG is not set
> diff --git a/automation/configs/x86/pv_only_config b/automation/configs/x86/pv_only_config
> deleted file mode 100644
> index e9d8b4a7c753..000000000000
> --- a/automation/configs/x86/pv_only_config
> +++ /dev/null
> @@ -1,3 +0,0 @@
> -CONFIG_PV=y
> -# CONFIG_HVM is not set
> -# CONFIG_DEBUG is not set
> diff --git a/automation/scripts/build b/automation/scripts/build
> index a5934190634b..5dafa72ba540 100755
> --- a/automation/scripts/build
> +++ b/automation/scripts/build
> @@ -85,24 +85,3 @@ if [[ "${XEN_TARGET_ARCH}" != "x86_32" ]]; then
>          cp -r dist binaries/
>      fi
>  fi
> -
> -if [[ "${hypervisor_only}" == "y" ]]; then
> -    # If we are build testing a specific Kconfig exit now, there's no point in
> -    # testing all the possible configs.
> -    exit 0
> -fi
> -
> -# Build all the configs we care about
> -case ${XEN_TARGET_ARCH} in
> -    x86_64) arch=x86 ;;
> -    *) exit 0 ;;
> -esac
> -
> -cfg_dir="automation/configs/${arch}"
> -for cfg in `ls ${cfg_dir}`; do
> -    echo "Building $cfg"
> -    make -j$(nproc) -C xen clean
> -    rm -f xen/.config
> -    make -C xen KBUILD_DEFCONFIG=../../../../${cfg_dir}/${cfg} defconfig
> -    make -j$(nproc) -C xen
> -done
> -- 
> 2.11.0
> 


  parent reply	other threads:[~2023-01-04  1:08 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-30  0:38 [PATCH 0/6] CI: Fixes/cleanup in preparation for RISCV Andrew Cooper
2022-12-30  0:38 ` [PATCH 1/6] CI: Drop automation/configs/ Andrew Cooper
2023-01-02 13:57   ` Michal Orzel
2023-01-04  1:08   ` Stefano Stabellini [this message]
2022-12-30  0:38 ` [PATCH 2/6] CI: Remove guesswork about which artefacts to preserve Andrew Cooper
2023-01-02 14:00   ` Michal Orzel
2023-01-04 12:12     ` Andrew Cooper
2023-01-04 12:18       ` Michal Orzel
2023-01-04  1:10   ` Stefano Stabellini
2023-01-04  1:18     ` Andrew Cooper
2023-01-04  1:22       ` Stefano Stabellini
2022-12-30  0:38 ` [PATCH 3/6] CI: Only calculate ./configure args if needed Andrew Cooper
2023-01-02 14:01   ` Michal Orzel
2023-01-04  1:12   ` Stefano Stabellini
2022-12-30  0:38 ` [PATCH 4/6] CI: Express HYPERVISOR_ONLY in build.yml Andrew Cooper
2022-12-30 10:04   ` Oleksii
2023-01-02 14:05   ` Michal Orzel
2023-01-04  1:15   ` Stefano Stabellini
2023-01-04  1:27     ` Andrew Cooper
2023-01-04  1:36       ` Stefano Stabellini
2023-01-04  1:41         ` Andrew Cooper
2023-01-04  1:48           ` Stefano Stabellini
2023-01-04  1:51             ` Andrew Cooper
2023-01-04  1:55               ` Stefano Stabellini
2022-12-30  0:38 ` [PATCH 5/6] CI: Fix build script when CROSS_COMPILE is in use Andrew Cooper
2023-01-04  1:20   ` Stefano Stabellini
2022-12-30  0:38 ` [PATCH 6/6] CI: Simplify the MUSL check Andrew Cooper
2023-01-04  1:22   ` Stefano Stabellini

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.DEB.2.22.394.2301031707540.4079@ubuntu-linux-20-04-desktop \
    --to=sstabellini@kernel.org \
    --cc=andrew.cooper3@citrix.com \
    --cc=anthony.perard@citrix.com \
    --cc=cardoe@cardoe.com \
    --cc=michal.orzel@amd.com \
    --cc=oleksii.kurochko@gmail.com \
    --cc=xen-devel@lists.xenproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.