| Message ID | 20210708065435.24515-1-olaf@aepfle.de (mailing list archive) |
|---|---|
| State | New, archived |
| Headers | show |
| Series | [v1] automation: collect log files in subdirectories | expand |
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>: > 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
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
On Wed, Jul 14, 2021 at 09:31:04AM +0200, Olaf Hering wrote: > 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. Actually, it's possible to delete the repo. Navigate to the repo you want to delete ( https://gitlab.com/xen-project/people/olafhering ) then in the sidebar/menu (hopefully on the left) there is "Setting". Navigate to "Settings/General", in the "Advanced section" there is "Delete project", read it all, hopefully it says which repo you want to delete (olafhering). At this point, you can probably create a new "subgroup". Navigate to https://gitlab.com/xen-project/people then click on "New subgroup". Hopefully, you have your own subgroup now, time to fork Xen! Navigate to the Xen repo ( https://gitlab.com/xen-project/xen ), then click "Fork". Choose your new subgroup as "namespace" (project url section). Hopefully, those instructions are enough to get you were you want to be. Otherwise, I think I can do all that if needed. Cheers,
Am Fri, 16 Jul 2021 15:28:43 +0100 schrieb Anthony PERARD <anthony.perard@citrix.com>: > Actually, it's possible to delete the repo. > Navigate to the repo you want to delete ( https://gitlab.com/xen-project/people/olafhering ) > then in the sidebar/menu (hopefully on the left) there is "Setting". This entry exists elsewhere, but not in this repo. I guess a project admin has to wipe the repo. Olaf
On Fri, Jul 16, 2021 at 04:41:57PM +0200, Olaf Hering wrote: > Am Fri, 16 Jul 2021 15:28:43 +0100 > schrieb Anthony PERARD <anthony.perard@citrix.com>: > > > Actually, it's possible to delete the repo. > > Navigate to the repo you want to delete ( https://gitlab.com/xen-project/people/olafhering ) > > then in the sidebar/menu (hopefully on the left) there is "Setting". > > This entry exists elsewhere, but not in this repo. > I guess a project admin has to wipe the repo. BTW, I did that 4 days ago, but an MTA never managed to send the email and told me only now ... Anyway Olaf, I've deleted the repo, feel free to try again, or let me now if you want me to set things up. Cheers,
Am Tue, 20 Jul 2021 16:41:23 +0100 schrieb Anthony PERARD <anthony.perard@citrix.com>: > Anyway Olaf, I've deleted the repo, feel free to try again, or let me > now if you want me to set things up. I'm sure if I create a fresh repo 'xen.git' in a "group" 'olafhering', I will be unable to push there because it is empty. Not sure if I can force-push in case I choose to populate it with just a README and or License file, just to get some initial branch. But I can try once more and see if I can let gitlab populate it from an existing repo, such as the main xen.git. Olaf
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
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.