The current single *.log pattern collects just config.log, which
usually contains little useful information.
Collect also log files in subdirectories, tools/config.log usually
contains information about configure failures.

Signed-off-by: Olaf Hering <olaf@aepfle.de>
---
 automation/gitlab-ci/build.yaml | 1 +
 1 file changed, 1 insertion(+)

No idea if the syntax is correct, and how I would test such changes myself.

diff --git a/automation/gitlab-ci/build.yaml b/automation/gitlab-ci/build.yaml
index 20d1d0cb34..d177da1710 100644
--- a/automation/gitlab-ci/build.yaml
+++ b/automation/gitlab-ci/build.yaml
@@ -8,6 +8,7 @@
       - binaries/
       - xen-config
       - '*.log'
+      - '*/*.log'
     when: always
   except:
     - master

On 08/07/2021 07:54, Olaf Hering wrote:
> The current single *.log pattern collects just config.log, which
> usually contains little useful information.
> Collect also log files in subdirectories, tools/config.log usually
> contains information about configure failures.
>
> Signed-off-by: Olaf Hering <olaf@aepfle.de>
> ---
>  automation/gitlab-ci/build.yaml | 1 +
>  1 file changed, 1 insertion(+)
>
> No idea if the syntax is correct, and how I would test such changes myself.

https://gitlab.com/xen-project/people/andyhhp/xen/-/pipelines/333797480
is a pipeline running with this patch in place.

As for testing, get an account on Gitlab.  I'll add you to xen-project,
after which pushes to your local fork of Xen here will use the
project-wide runner configuration, rather than using the Gitlab's pool
of public workers (which amongst other things, lack ARM).

~Andrew

Am Thu, 8 Jul 2021 12:43:41 +0100
schrieb Andrew Cooper <andrew.cooper3@citrix.com>:

> As for testing, get an account on Gitlab.  I'll add you to xen-project,
> after which pushes to your local fork of Xen here will use the
> project-wide runner configuration, rather than using the Gitlab's pool
> of public workers (which amongst other things, lack ARM).

Now there is https://gitlab.com/xen-project/people/olafhering
This should have been a "group" I think, so that I could create a xen.git below.
Now it is an empty repository. Pushing anything to it fails because it lacks a default branch.
Undoing the mistake fails as well because the webui lacks a knob to delete this repository.


Olaf

Am Thu, 8 Jul 2021 12:43:41 +0100
schrieb Andrew Cooper <andrew.cooper3@citrix.com>:

> https://gitlab.com/xen-project/people/andyhhp/xen/-/pipelines/333797480
> is a pipeline running with this patch in place.

Thanks, apparently the logs are in place now.

My github/gitlab username is 'olafhering'.

Olaf