From: "Pavel Machek" <pavel@ucw.cz>
To: cip-dev@lists.cip-project.org
Cc: nobuhiro1.iwamatsu@toshiba.co.jp, iwamatsu@nigauri.org,
Chris.Paterson2@renesas.com, quirin.gylstorff@siemens.com
Subject: Re: [cip-dev] Everything failed in gitlab
Date: Fri, 28 Aug 2020 18:53:25 +0200 [thread overview]
Message-ID: <20200828165324.GA9883@amd> (raw)
In-Reply-To: <d985a86c-97fb-f1c2-9b91-2bfba8185cd5@siemens.com>
[-- Attachment #1.1: Type: text/plain, Size: 979 bytes --]
Hi!
> >>> This is happening not only in cip-testing (kernel test) but also in
> >>> cip-core[0][1].
> >>> I don't manage these runners. Has anyone changed permissions etc?
> >>
> >> I do. Just restarted a build
> >> (https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/707991738), and
> >> it is apparently working.
> >>
> >> Is there in issue with who is triggering the build and what permission
> >> that person has? Just restarted [0], and that also works:
> >>
> >> https://gitlab.com/cip-project/cip-core/isar-cip-core/-/jobs/707992917
> >
> > Gitlab runner is now working on all repositories.
> > Thanks!
> ...but I didn't change anything for that. I guess is was a temporal hick-up.
I can confirm that builds now work. Thanks to whoever (or whatever)
fixed it :-).
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
[-- Attachment #2: Type: text/plain, Size: 419 bytes --]
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#5321): https://lists.cip-project.org/g/cip-dev/message/5321
Mute This Topic: https://lists.cip-project.org/mt/76423839/4520388
Group Owner: cip-dev+owner@lists.cip-project.org
Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/8129055/727948398/xyzzy [cip-dev@archiver.kernel.org]
-=-=-=-=-=-=-=-=-=-=-=-
prev parent reply other threads:[~2020-08-28 16:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-26 7:24 [cip-dev] Everything failed in gitlab Pavel Machek
2020-08-27 6:48 ` Nobuhiro Iwamatsu
2020-08-27 7:36 ` Jan Kiszka
2020-08-27 8:21 ` Michael Adler
2020-08-27 13:10 ` Pavel Machek
2020-08-27 21:40 ` Nobuhiro Iwamatsu
2020-08-28 4:44 ` Jan Kiszka
2020-08-28 7:11 ` Nobuhiro Iwamatsu
2020-08-28 7:51 ` Jan Kiszka
2020-08-28 16:53 ` Pavel Machek [this message]
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=20200828165324.GA9883@amd \
--to=pavel@ucw.cz \
--cc=Chris.Paterson2@renesas.com \
--cc=cip-dev@lists.cip-project.org \
--cc=iwamatsu@nigauri.org \
--cc=nobuhiro1.iwamatsu@toshiba.co.jp \
--cc=quirin.gylstorff@siemens.com \
/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.