gitlab -stable-rc: mirroring not working?

gitlab -stable-rc: mirroring not working?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 442 bytes --]

Hi!

I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/tree/linux-6.1.y

Can someone take a look what is wrong?

Plus, it would be cool to start testing 6.9-stable branch.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: [cip-dev] gitlab -stable-rc: mirroring not working?

[Chris Paterson]

Hi Pavel,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Pavel Machek via lists.cip-project.org
> Sent: Wednesday, May 15, 2024 6:26 PM
> 
> Hi!
> 
> I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> /tree/linux-6.1.y
> 
> Can someone take a look what is wrong?

Thanks for reporting!
It looks like the token on the cip-ci gitlab account expired, so our trigger jobs couldn't push commits.
I've fixed it now and the new pipelines are running:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines?scope=branches&page=1


> 
> Plus, it would be cool to start testing 6.9-stable branch.

Yea I'll get this sorted when the first -rc is out.

Thanks, Chris 


> 
> Best regards,
> 								Pavel
> --
> DENX Software Engineering GmbH,        Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

gitlab testing stuck?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 642 bytes --]

Hi!

There seems to be something wrong with gitlab testing at the moment:

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1302074556

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/6920224416

gitlab says:

This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch, or no runners that match all of the job's tags: small

Go to project CI settings

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: [cip-dev] gitlab testing stuck?

[Michael Adler]

Hi,

the runner is gone because of a breaking change by Gitlab [1].
Basically, someone with the appropriate permissions needs to register a runner
and send me the token, so I can re-register our runner again.

Kind Regards,
  Michael

[1] https://docs.gitlab.com/ee/security/token_overview.html#runner-authentication-tokens

On Thu, May 23, 2024 at 11:33:26AM +0200, Pavel Machek via lists.cip-project.org wrote:
> Hi!
> 
> There seems to be something wrong with gitlab testing at the moment:
> 
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1302074556
> 
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/6920224416
> 
> gitlab says:
> 
> This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch, or no runners that match all of the job's tags: small
> 
> Go to project CI settings
> 
> Best regards,
> 								Pavel
> -- 
> DENX Software Engineering GmbH,        Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany



> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15928): https://lists.cip-project.org/g/cip-dev/message/15928
> Mute This Topic: https://lists.cip-project.org/mt/106259374/4520419
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/12503494/4520419/1780039012/xyzzy [michael.adler@siemens.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Michael Adler

Siemens AG
Technology
Connectivity & Edge
Open Source Embedded Systems
T CED OES-DE
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann
Snabe; Managing Board: Roland Busch, Chairman, President and Chief Executive
Officer; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
Registered offices: Berlin and Munich, Germany; Commercial registries:
Berlin-Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

Re: Re: [cip-dev] gitlab testing stuck?

[Michael Adler]

Thanks to Chris for providing me the new tokens. I've registered the runners
again and it seems to be working.

Kind Regards,
  Michael

On Thu, May 23, 2024 at 11:47:54AM +0200, Michael Adler via lists.cip-project.org wrote:
> Hi,
> 
> the runner is gone because of a breaking change by Gitlab [1].
> Basically, someone with the appropriate permissions needs to register a runner
> and send me the token, so I can re-register our runner again.
> 
> Kind Regards,
>   Michael
> 
> [1] https://docs.gitlab.com/ee/security/token_overview.html#runner-authentication-tokens
> 
> On Thu, May 23, 2024 at 11:33:26AM +0200, Pavel Machek via lists.cip-project.org wrote:
> > Hi!
> > 
> > There seems to be something wrong with gitlab testing at the moment:
> > 
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1302074556
> > 
> > https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/6920224416
> > 
> > gitlab says:
> > 
> > This job is stuck because of one of the following problems. There are no active runners online, no runners for the protected branch, or no runners that match all of the job's tags: small
> > 
> > Go to project CI settings
> > 
> > Best regards,
> > 								Pavel
> > -- 
> > DENX Software Engineering GmbH,        Managing Director: Erika Unter
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
> 
> 
> 
> > 
> > 
> > 
> 
> 
> -- 
> Michael Adler
> 
> Siemens AG
> Technology
> Connectivity & Edge
> Open Source Embedded Systems
> T CED OES-DE
> Friedrich-Ludwig-Bauer-Str. 3
> 85748 Garching, Germany
> 
> Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann
> Snabe; Managing Board: Roland Busch, Chairman, President and Chief Executive
> Officer; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
> Registered offices: Berlin and Munich, Germany; Commercial registries:
> Berlin-Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

> 
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#15929): https://lists.cip-project.org/g/cip-dev/message/15929
> Mute This Topic: https://lists.cip-project.org/mt/106259374/4520419
> Group Owner: cip-dev+owner@lists.cip-project.org
> Unsubscribe: https://lists.cip-project.org/g/cip-dev/leave/12503494/4520419/1780039012/xyzzy [michael.adler@siemens.com]
> -=-=-=-=-=-=-=-=-=-=-=-
> 


-- 
Michael Adler

Siemens AG
Technology
Connectivity & Edge
Open Source Embedded Systems
T CED OES-DE
Friedrich-Ludwig-Bauer-Str. 3
85748 Garching, Germany

Siemens Aktiengesellschaft: Chairman of the Supervisory Board: Jim Hagemann
Snabe; Managing Board: Roland Busch, Chairman, President and Chief Executive
Officer; Cedrik Neike, Matthias Rebellius, Ralf P. Thomas, Judith Wiese;
Registered offices: Berlin and Munich, Germany; Commercial registries:
Berlin-Charlottenburg, HRB 12300, Munich, HRB 6684; WEEE-Reg.-No. DE 23691322

Re: Re: [cip-dev] gitlab testing stuck?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 344 bytes --]

Hi!

> Thanks to Chris for providing me the new tokens. I've registered the runners
> again and it seems to be working.

Thank you, testing seems to work now.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: [cip-dev] gitlab -stable-rc: mirroring not working?

[Chris Paterson]

Hello Pavel,

> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Pavel Machek via lists.cip-project.org
> Sent: Wednesday, May 15, 2024 6:26 PM
> 
> Hi!
> 
> I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> /tree/linux-6.1.y
> 
> Can someone take a look what is wrong?
> 
> Plus, it would be cool to start testing 6.9-stable branch.

Support is now added:
https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines?ref=linux-6.9.y

The initial test results look okay, apart from one thing...

It looks like we're seeing a new failure (VULN) for one of the spectre-meltdown checker tests - CVE-2017-5715.
We're only seeing this failure on the x86 simatic-ipc227e platform.
Failed test case log:
https://lava.ciplatform.org/scheduler/job/1138103#L998

I checked v6.8.11-rc1 and this test case passes:
https://lava.ciplatform.org/scheduler/job/1137807#L976


Perhaps this isn't a massive issue, but I thought I should report it anyway.
For now I won't mark this as a "known issue".

Kind regards, Chris

CVE-2017-5715 on simatic-ipc227e -- was Re: [cip-dev] gitlab -stable-rc: mirroring not working?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1378 bytes --]

Hi!

> > I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
> > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> > /tree/linux-6.1.y
> > 
> > Can someone take a look what is wrong?
> > 
> > Plus, it would be cool to start testing 6.9-stable branch.
> 
> Support is now added:
> https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipelines?ref=linux-6.9.y
> 
> The initial test results look okay, apart from one thing...
> 
> It looks like we're seeing a new failure (VULN) for one of the spectre-meltdown checker tests - CVE-2017-5715.
> We're only seeing this failure on the x86 simatic-ipc227e platform.
> Failed test case log:
> https://lava.ciplatform.org/scheduler/job/1138103#L998
> 
> I checked v6.8.11-rc1 and this test case passes:
> https://lava.ciplatform.org/scheduler/job/1137807#L976
> 
> Perhaps this isn't a massive issue, but I thought I should report it anyway.
> For now I won't mark this as a "known issue".

Hmm. That's Spectre v2. Can you get

cat /sys/devices/system/cpu/vulnerabilities/spectre_v2

from both working and failing versions? Are we using latest version of
spectre-meltdown checker?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: CVE-2017-5715 on simatic-ipc227e -- was Re: [cip-dev] gitlab -stable-rc: mirroring not working?

[nobuhiro1.iwamatsu]

Hi,

> > Perhaps this isn't a massive issue, but I thought I should report it anyway.
> > For now I won't mark this as a "known issue".
> 
> Hmm. That's Spectre v2. Can you get
> 
> cat /sys/devices/system/cpu/vulnerabilities/spectre_v2

Please see https://lava.ciplatform.org/scheduler/job/1140402/definition#defline71 .

> 
> from both working and failing versions? Are we using latest version of
> spectre-meltdown checker?

Probably 0.45.

I will check this as well.
But it seems there is a problem with LAVA ☹

Best regards,
  Nobuhiro 

----Original Message-----
> From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> Behalf Of Pavel Machek
> Sent: Saturday, May 25, 2024 3:59 AM
> To: Chris Paterson <Chris.Paterson2@renesas.com>;
> jan.kiszka@siemens.com
> Cc: cip-dev@lists.cip-project.org
> Subject: CVE-2017-5715 on simatic-ipc227e -- was Re: [cip-dev] gitlab
> -stable-rc: mirroring not working?
> 
> Hi!
> 
> > > I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
> > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> > > /tree/linux-6.1.y
> > >
> > > Can someone take a look what is wrong?
> > >
> > > Plus, it would be cool to start testing 6.9-stable branch.
> >
> > Support is now added:
> > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipeli
> > nes?ref=linux-6.9.y
> >
> > The initial test results look okay, apart from one thing...
> >
> > It looks like we're seeing a new failure (VULN) for one of the
> spectre-meltdown checker tests - CVE-2017-5715.
> > We're only seeing this failure on the x86 simatic-ipc227e platform.
> > Failed test case log:
> > https://lava.ciplatform.org/scheduler/job/1138103#L998
> >
> > I checked v6.8.11-rc1 and this test case passes:
> > https://lava.ciplatform.org/scheduler/job/1137807#L976
> >
> > Perhaps this isn't a massive issue, but I thought I should report it anyway.
> > For now I won't mark this as a "known issue".
> 
> Hmm. That's Spectre v2. Can you get
> 
> cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> 
> from both working and failing versions? Are we using latest version of
> spectre-meltdown checker?
> 
> Best regards,
> 								Pavel
> --
> DENX Software Engineering GmbH,        Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Siemens targets timing out?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 366 bytes --]

Hi!

I'm trying to test Renesas Ethernet changes, but Siemens targets cause
timeouts. Can anyone take a look?

https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1310801626

Thanks,
									Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: Siemens targets timing out?

[Jan Kiszka]

On 30.05.24 13:12, Pavel Machek wrote:
> Hi!
> 
> I'm trying to test Renesas Ethernet changes, but Siemens targets cause
> timeouts. Can anyone take a look?
> 
> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1310801626
> 

I thought our lab was still offline (internal IT...) and only about to
be relaunched. Quirin?

Jan

-- 
Siemens AG, Technology
Linux Expert Center

Re: Siemens targets timing out?

[Gylstorff Quirin]

Our Lab is still not launched, the lab of denx is offline.

https://lava.ciplatform.org/scheduler/worker/lab-cip-denx


Best regards
Quirin	

On 6/3/24 6:46 AM, Jan Kiszka wrote:
> On 30.05.24 13:12, Pavel Machek wrote:
>> Hi!
>>
>> I'm trying to test Renesas Ethernet changes, but Siemens targets cause
>> timeouts. Can anyone take a look?
>>
>> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1310801626
>>
> 
> I thought our lab was still offline (internal IT...) and only about to
> be relaunched. Quirin?
> 
> Jan
> 

Re: Siemens targets timing out?

[Claudius Heine]

Hi Quirin,

On 03/06/2024 10.28, Gylstorff Quirin wrote:
> Our Lab is still not launched, the lab of denx is offline.
>
> https://lava.ciplatform.org/scheduler/worker/lab-cip-denx

I had the bright idea to restart the server and update it beforehand 
last week, I now had to fix the boot issues, but it seems like 
docker-compose/docker now complains:

```
docker-compose client version 1.22 is too old. Minimum supported API 
version is 1.24, please upgrade your client to a newer version
```

It seems now that there is `docker-compose-plugin` package from the 
docker repos, which does not supply a `docker-compose` binary to the 
PATH. Instead now it is used via `docker compose`...

So either patching all `docker-compose` calls to `docker compose`, 
adding `/usr/libexec/docker/cli-plugins/` to the search path, or 
creating a symlink for it.

I will probably try to patch the `docker-compose` calls to `docker compose`.

regards,
Claudius

>
>
> Best regards
> Quirin
>
> On 6/3/24 6:46 AM, Jan Kiszka wrote:
>> On 30.05.24 13:12, Pavel Machek wrote:
>>> Hi!
>>>
>>> I'm trying to test Renesas Ethernet changes, but Siemens targets cause
>>> timeouts. Can anyone take a look?
>>>
>>> https://gitlab.com/cip-project/cip-kernel/linux-cip/-/pipelines/1310801626 
>>>
>>>
>>
>> I thought our lab was still offline (internal IT...) and only about to
>> be relaunched. Quirin?
>>
>> Jan
>>

Re: Siemens targets timing out?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1111 bytes --]

Hi!

> > https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
> 
> I had the bright idea to restart the server and update it beforehand last
> week, I now had to fix the boot issues, but it seems like
> docker-compose/docker now complains:
> 
> ```
> docker-compose client version 1.22 is too old. Minimum supported API version
> is 1.24, please upgrade your client to a newer version
> ```
> 
> It seems now that there is `docker-compose-plugin` package from the docker
> repos, which does not supply a `docker-compose` binary to the PATH. Instead
> now it is used via `docker compose`...
> 
> So either patching all `docker-compose` calls to `docker compose`, adding
> `/usr/libexec/docker/cli-plugins/` to the search path, or creating a symlink
> for it.
> 
> I will probably try to patch the `docker-compose` calls to `docker
> compose`.

Thank you. Can you ping me when I should re-try the tests?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

Re: Siemens targets timing out?

[Claudius Heine]

Hi Pavel,

On 2024-06-03 12:16 pm, Pavel Machek wrote:
> Hi!
> 
>>> https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
>>
>> I had the bright idea to restart the server and update it beforehand last
>> week, I now had to fix the boot issues, but it seems like
>> docker-compose/docker now complains:
>>
>> ```
>> docker-compose client version 1.22 is too old. Minimum supported API version
>> is 1.24, please upgrade your client to a newer version
>> ```
>>
>> It seems now that there is `docker-compose-plugin` package from the docker
>> repos, which does not supply a `docker-compose` binary to the PATH. Instead
>> now it is used via `docker compose`...
>>
>> So either patching all `docker-compose` calls to `docker compose`, adding
>> `/usr/libexec/docker/cli-plugins/` to the search path, or creating a symlink
>> for it.
>>
>> I will probably try to patch the `docker-compose` calls to `docker
>> compose`.
> 
> Thank you. Can you ping me when I should re-try the tests?

The containers do start now, but sadly, there seem other issues with 
lava now. Its a bit of a rabbit hole of issues currently.

regards,
Claudius



-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: ch@denx.de

6.1 plans (rt, ethernet merge) was Re: Siemens targets timing out?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]

Hi!

> > > https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
> > 
> > I had the bright idea to restart the server and update it beforehand last
> > week, I now had to fix the boot issues, but it seems like
> > docker-compose/docker now complains:
> > 
> > ```
> > docker-compose client version 1.22 is too old. Minimum supported API version
> > is 1.24, please upgrade your client to a newer version
> > ```
> > 
> > It seems now that there is `docker-compose-plugin` package from the docker
> > repos, which does not supply a `docker-compose` binary to the PATH. Instead
> > now it is used via `docker compose`...
> > 
> > So either patching all `docker-compose` calls to `docker compose`, adding
> > `/usr/libexec/docker/cli-plugins/` to the search path, or creating a symlink
> > for it.
> > 
> > I will probably try to patch the `docker-compose` calls to `docker
> > compose`.
> 
> Thank you. Can you ping me when I should re-try the tests?

Ok, not sure what to do here.

So, 6.1-rt is due, and we have v6.1.91-cip21, v6.1.91-rt31,
v6.1.91-rt31 and gitlab testing is broken.

I guess Renesas Ethernet patches should not break Siemens boards, so I
propose to apply them. Then I can ask for or do 6.1.92-cip release, to
sync versions, and finally 6.1.92-cip-rt.

If anyone is uncomfortable with the plan, let me know.

Iwamatsu-san, do you want to do 6.1.92-cip or can I do that?

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: 6.1 plans (rt, ethernet merge) was Re: Siemens targets timing out?

[nobuhiro1.iwamatsu]

Hi Pavel,

> > Thank you. Can you ping me when I should re-try the tests?
> 
> Ok, not sure what to do here.
> 
> So, 6.1-rt is due, and we have v6.1.91-cip21, v6.1.91-rt31,
> v6.1.91-rt31 and gitlab testing is broken.
> 
> I guess Renesas Ethernet patches should not break Siemens boards, so I
> propose to apply them. Then I can ask for or do 6.1.92-cip release, to sync
> versions, and finally 6.1.92-cip-rt.
> 
> If anyone is uncomfortable with the plan, let me know.

No problem to me.

> 
> Iwamatsu-san, do you want to do 6.1.92-cip or can I do that?

Please go ahead. Thank you for your -cip-rt maintenance work.　

Best regards,
  Nobuhiro 

> -----Original Message-----
> From: Pavel Machek <pavel@denx.de>
> Sent: Tuesday, June 4, 2024 7:30 PM
> To: Pavel Machek <pavel@denx.de>; iwamatsu nobuhiro(岩松 信洋 ○ＤＩＴ
> Ｃ□ＤＩＴ○ＯＳＴ) <nobuhiro1.iwamatsu@toshiba.co.jp>
> Cc: Claudius Heine <ch@denx.de>; Gylstorff Quirin
> <quirin.gylstorff@siemens.com>; Jan Kiszka <jan.kiszka@siemens.com>;
> cip-dev@lists.cip-project.org; Chris.Paterson2@renesas.com
> Subject: 6.1 plans (rt, ethernet merge) was Re: Siemens targets timing out?
> 
> Hi!
> 
> > > > https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
> > >
> > > I had the bright idea to restart the server and update it beforehand
> > > last week, I now had to fix the boot issues, but it seems like
> > > docker-compose/docker now complains:
> > >
> > > ```
> > > docker-compose client version 1.22 is too old. Minimum supported API
> > > version is 1.24, please upgrade your client to a newer version ```
> > >
> > > It seems now that there is `docker-compose-plugin` package from the
> > > docker repos, which does not supply a `docker-compose` binary to the
> > > PATH. Instead now it is used via `docker compose`...
> > >
> > > So either patching all `docker-compose` calls to `docker compose`,
> > > adding `/usr/libexec/docker/cli-plugins/` to the search path, or
> > > creating a symlink for it.
> > >
> > > I will probably try to patch the `docker-compose` calls to `docker
> > > compose`.
> >
> > Thank you. Can you ping me when I should re-try the tests?
> 
> Ok, not sure what to do here.
> 
> So, 6.1-rt is due, and we have v6.1.91-cip21, v6.1.91-rt31,
> v6.1.91-rt31 and gitlab testing is broken.
> 
> I guess Renesas Ethernet patches should not break Siemens boards, so I
> propose to apply them. Then I can ask for or do 6.1.92-cip release, to sync
> versions, and finally 6.1.92-cip-rt.
> 
> If anyone is uncomfortable with the plan, let me know.
> 
> Iwamatsu-san, do you want to do 6.1.92-cip or can I do that?
> 
> Best regards,
> 								Pavel
> --
> DENX Software Engineering GmbH,        Managing Director: Erika Unter
> HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

Re: Siemens targets timing out?

[Claudius Heine]

Hi Pavel,

On 03/06/2024 12.16, Pavel Machek wrote:
> Hi!
>
>>> https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
>> I had the bright idea to restart the server and update it beforehand last
>> week, I now had to fix the boot issues, but it seems like
>> docker-compose/docker now complains:
>>
>> ```
>> docker-compose client version 1.22 is too old. Minimum supported API version
>> is 1.24, please upgrade your client to a newer version
>> ```
>>
>> It seems now that there is `docker-compose-plugin` package from the docker
>> repos, which does not supply a `docker-compose` binary to the PATH. Instead
>> now it is used via `docker compose`...
>>
>> So either patching all `docker-compose` calls to `docker compose`, adding
>> `/usr/libexec/docker/cli-plugins/` to the search path, or creating a symlink
>> for it.
>>
>> I will probably try to patch the `docker-compose` calls to `docker
>> compose`.
> Thank you. Can you ping me when I should re-try the tests?

The lab-cip-denx is online now, and hopefully stays that for a while.

regards,
Claudius

RE: Siemens targets timing out?

[Chris Paterson]

Hello Claudius,

> From: Claudius Heine <ch@denx.de>
> Sent: Wednesday, June 5, 2024 9:00 AM
> 
> Hi Pavel,
> 
> On 03/06/2024 12.16, Pavel Machek wrote:
> > Hi!
> >
> >>> https://lava.ciplatform.org/scheduler/worker/lab-cip-denx
> >> I had the bright idea to restart the server and update it beforehand
> last
> >> week, I now had to fix the boot issues, but it seems like
> >> docker-compose/docker now complains:
> >>
> >> ```
> >> docker-compose client version 1.22 is too old. Minimum supported API
> version
> >> is 1.24, please upgrade your client to a newer version
> >> ```
> >>
> >> It seems now that there is `docker-compose-plugin` package from the
> docker
> >> repos, which does not supply a `docker-compose` binary to the PATH.
> Instead
> >> now it is used via `docker compose`...
> >>
> >> So either patching all `docker-compose` calls to `docker compose`,
> adding
> >> `/usr/libexec/docker/cli-plugins/` to the search path, or creating a
> symlink
> >> for it.
> >>
> >> I will probably try to patch the `docker-compose` calls to `docker
> >> compose`.
> > Thank you. Can you ping me when I should re-try the tests?
> 
> The lab-cip-denx is online now, and hopefully stays that for a while.

Thank you for the update and for getting it online again.

Kind regards, Chris

Re: Siemens targets timing out?

[Pavel Machek]

[-- Attachment #1: Type: text/plain, Size: 457 bytes --]

Hi!

> > > I will probably try to patch the `docker-compose` calls to `docker
> > > compose`.
> > Thank you. Can you ping me when I should re-try the tests?
> 
> The lab-cip-denx is online now, and hopefully stays that for a while.

Thank you, it seems to work ok now.

Best regards,
								Pavel
-- 
DENX Software Engineering GmbH,        Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]

RE: CVE-2017-5715 on simatic-ipc227e -- was Re: [cip-dev] gitlab -stable-rc: mirroring not working?

[Chris Paterson]

Hello,

> From: nobuhiro1.iwamatsu@toshiba.co.jp <nobuhiro1.iwamatsu@toshiba.co.jp>
> Sent: Thursday, May 30, 2024 2:37 AM
> 
> Hi,
> 
> > > Perhaps this isn't a massive issue, but I thought I should report it
> anyway.
> > > For now I won't mark this as a "known issue".
> >
> > Hmm. That's Spectre v2. Can you get
> >
> > cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> 
> Please see
> https://lava.ciplatform.org/scheduler/job/1140402/definition#defline71 .
> 
> >
> > from both working and failing versions? Are we using latest version of
> > spectre-meltdown checker?
> 
> Probably 0.45.

Yep.
I've just submitted an MR to upgrade to v0.46, but I don’t think this will change our results.
https://github.com/Linaro/test-definitions/pull/509

Kind regards, Chris

> 
> I will check this as well.
> But it seems there is a problem with LAVA ☹
> 
> Best regards,
>   Nobuhiro
> 
> ----Original Message-----
> > From: cip-dev@lists.cip-project.org <cip-dev@lists.cip-project.org> On
> > Behalf Of Pavel Machek
> > Sent: Saturday, May 25, 2024 3:59 AM
> > To: Chris Paterson <Chris.Paterson2@renesas.com>;
> > jan.kiszka@siemens.com
> > Cc: cip-dev@lists.cip-project.org
> > Subject: CVE-2017-5715 on simatic-ipc227e -- was Re: [cip-dev] gitlab
> > -stable-rc: mirroring not working?
> >
> > Hi!
> >
> > > > I'd like to test 6.1.91-rc2 and friends, but gitlab still have -rc1:
> > > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-
> > > > /tree/linux-6.1.y
> > > >
> > > > Can someone take a look what is wrong?
> > > >
> > > > Plus, it would be cool to start testing 6.9-stable branch.
> > >
> > > Support is now added:
> > > https://gitlab.com/cip-project/cip-testing/linux-stable-rc-ci/-/pipeli
> > > nes?ref=linux-6.9.y
> > >
> > > The initial test results look okay, apart from one thing...
> > >
> > > It looks like we're seeing a new failure (VULN) for one of the
> > spectre-meltdown checker tests - CVE-2017-5715.
> > > We're only seeing this failure on the x86 simatic-ipc227e platform.
> > > Failed test case log:
> > > https://lava.ciplatform.org/scheduler/job/1138103#L998
> > >
> > > I checked v6.8.11-rc1 and this test case passes:
> > > https://lava.ciplatform.org/scheduler/job/1137807#L976
> > >
> > > Perhaps this isn't a massive issue, but I thought I should report it
> anyway.
> > > For now I won't mark this as a "known issue".
> >
> > Hmm. That's Spectre v2. Can you get
> >
> > cat /sys/devices/system/cpu/vulnerabilities/spectre_v2
> >
> > from both working and failing versions? Are we using latest version of
> > spectre-meltdown checker?
> >
> > Best regards,
> > 								Pavel
> > --
> > DENX Software Engineering GmbH,        Managing Director: Erika Unter
> > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany