From: Uladzimir Bely <ubely@ilbers.de>
To: Henning Schild <henning.schild@siemens.com>
Cc: isar-users@googlegroups.com
Subject: Re: [PATCH v4 00/15] Add developers test
Date: Fri, 10 Feb 2023 05:42:40 +0300 [thread overview]
Message-ID: <5502260.ZASKD2KPVS@home> (raw)
In-Reply-To: <20230209164602.06343cbc@md1za8fc.ad001.siemens.net>
In the email from Thursday, 9 February 2023 18:46:02 +03 user Henning Schild
wrote:
> Am Thu, 09 Feb 2023 11:39:24 +0300
>
> schrieb Uladzimir Bely <ubely@ilbers.de>:
> > In the email from Monday, 6 February 2023 15:33:47 +03 user Uladzimir
> >
> > Bely wrote:
> > > Add developers test
> >
> > Hi all.
> >
> > Patchset passes our internal CI (Jenkins fast / full, also internal
> > Gitlab).
>
> i tested something called "fe689990a9f42242401e00af2e2c7699dde862be"
> that i once saw on ubely/devel
>
Yes, that was a combination of several patchsets
- (merged) fix cyclic dep on crossbuild-essential-riscv64
- (merged) Revert "dpkg: sbuild allows extra arguments via
DPKG_SBUILD_EXTRA_ARGS"
- (merged) initramfs: Add missing TASK_USE_SUDO
- (v2) deb-dl-dir: Fallback to copying when import-export
- (v4) Add developers tests
- (pre-v2) Support running custom commands in VM
It passed full/fast Jenkins CI, but failed in Gitlab ("Operation not
permitted" for ssh private key, so new vm_run tests failed. Fixed in v2)
> that went red but i did not yet look why.
>
Probably, you also faced "Operation not permitted". It seems in case of Gitlab
we can't do any modifications on cloned repo itself, including "chmod 600
testsute/keys/ssh/id_rsa" that is required for non-interactive ssh access
working.
Unfortunally, Git doesn't allow to store files with permissions different than
0755 and 0644.
> Is that what we are talking about? For this one it would really help if
> i could pull it somewhere .. long series i just have to push to a
> mirror.
To test, you can pick `948af8e7` (I've just pushed it to ubely/devel_runtest)
that includes both "(v4) Add developers tests" and "(v2) Support running
custom commands in VM". Or take just `30dadcb` from the same branch, that is
only "(v4) Add developers tests".
>
> > We are planning to merge this at ~Tue, Feb 14, if there are no any
> > objections.
>
> lovely date for patches instead of chocolates and flowers
>
> Henning
next prev parent reply other threads:[~2023-02-10 2:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 12:33 Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 01/15] CI: Enable downloads dir sharing Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 02/15] CI: Add IMAGE_INSTALL override Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 03/15] CI: Add developers test Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 04/15] CI: Remove duplicated targets Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 05/15] CI: move to avocado to 99.0 Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 06/15] CI: fix shell coding style Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 07/15] CI: install qemu-system when qemu testing is requested Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 08/15] testsuite: remove tests from "fast" set Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 09/15] CI: Get rid of setting cross from outside Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 10/15] CI: Make cross compile to be default Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 11/15] CI: Get rid of setting repro from outside Uladzimir Bely
2023-02-06 12:33 ` [PATCH v4 12/15] CI: Allow example module checking disabling Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 13/15] testsuite: Fix terminal broken after run test executed Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 14/15] CI: Update testsuite documentation Uladzimir Bely
2023-02-06 12:34 ` [PATCH v4 15/15] CI: Add single target test case Uladzimir Bely
2023-02-09 8:39 ` [PATCH v4 00/15] Add developers test Uladzimir Bely
2023-02-09 15:46 ` Henning Schild
2023-02-10 2:42 ` Uladzimir Bely [this message]
2023-02-10 9:44 ` Henning Schild
2023-02-10 9:51 ` Uladzimir Bely
2023-02-10 10:19 ` Henning Schild
2023-02-10 17:13 ` Baurzhan Ismagulov
2023-02-10 19:54 ` Henning Schild
2023-02-10 20:04 ` Henning Schild
2023-02-12 17:16 ` Baurzhan Ismagulov
2023-02-10 17:36 ` Henning Schild
2023-02-14 5:43 ` Uladzimir Bely
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=5502260.ZASKD2KPVS@home \
--to=ubely@ilbers.de \
--cc=henning.schild@siemens.com \
--cc=isar-users@googlegroups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox