Skip to contentSkip to conversation

Testing results for 4.19-cip-rt

cip-dev Pavel Machek 3 participants 6 messages Oct 2, 2019

lore
Share & tools
lore
#0 lore raw

Hi!

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

Thanks,
Pavel

Signature · 9 lines
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191002/94f5ec81/attachment.sig>
#1 lore raw
Quoted 10 lines · Pavel Machek

Hi!

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

Job #4665: Finished
Device Type: r8a774a1-hihope-rzg2m-ex
Device: r8a774a1-hihope-rzg2m-ex-01
Test: healthcheck

Chris can probably explain.

I see only the Renesas lab used here, right? Are we missing something for the IPC227E and de0-nano-soc to be used as well?

Jan

Signature · 2 lines
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
#2 lore raw

Hello Jan,

Quoted 20 lines

From: Jan Kiszka <[email protected]>
Sent: 02 October 2019 09:30

Quoted 10 lines · Pavel Machek

Hi!

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

Job #4665: Finished
Device Type: r8a774a1-hihope-rzg2m-ex
Device: r8a774a1-hihope-rzg2m-ex-01
Test: healthcheck

Quoted 4 lines

Chris can probably explain.

I see only the Renesas lab used here, right? Are we missing something for the IPC227E and de0-nano-soc to be used as well?

Correct. I was waiting on Kernel configurations in order to start testing the boards in the Mentor lab. These have now been submitted[0] to the cip-kernel-config repository, so hopefully we'll get tests up and running soon.

[0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/merge_requests/11

Kind regards, Chris

Quoted 6 lines

Jan

--
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux

#3 lore raw
Quoted 24 lines · Chris Paterson

Hello Jan,

Quoted 22 lines

From: Jan Kiszka <[email protected]>
Sent: 02 October 2019 09:30

Quoted 10 lines · Pavel Machek

Hi!

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

Job #4665: Finished

    Device Type: r8a774a1-hihope-rzg2m-ex
    Device: r8a774a1-hihope-rzg2m-ex-01
    Test: healthcheck

Chris can probably explain.

Quoted 8 lines
Quoted 2 lines

I see only the Renesas lab used here, right? Are we missing something for the IPC227E and de0-nano-soc to be used as well?

Correct. I was waiting on Kernel configurations in order to start testing the boards in the Mentor lab. These have now been submitted[0] to the cip-kernel-config repository, so hopefully we'll get tests up and running soon.

[0] https://gitlab.com/cip-project/cip-kernel/cip-kernel-config/merge_requests/11

Ah, cool!

Thanks,
Jan

Signature · 2 lines
Siemens AG, Corporate Technology, CT RDA IOT SES-DE
Corporate Competence Center Embedded Linux
#4 lore raw
In reply to Pavel Machek

Hello Pavel,

Quoted 5 lines

From: Pavel Machek <[email protected]>
Sent: 02 October 2019 09:23

Hi!

Quoted 7 lines

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

It looks like test join #4665[0] failed due to internet connectivity issues in the lab.

I've re-run the job and it passes[1], so you should be okay.
I've also re-run the GitLab CI test job[2], so GitLab will show the pipeline as a success[3].

[0] https://lava.ciplatform.org/scheduler/job/4665
[1] https://lava.ciplatform.org/scheduler/job/4716
[2] https://gitlab.com/cip-project/cip-kernel/linux-cip/-/jobs/309590344
[3] https://gitlab.com/cip-project/cip-kernel/linux-cip/pipelines/85866813

Kind regards, Chris

Quoted 6 lines

Thanks,
????? ??????? ??????? ??????? ??????? ??????? ??????? ??????? ??????? Pavel --
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

#5 lore raw

Hi!

Quoted 10 lines
Quoted 10 lines

From: Pavel Machek <[email protected]>
Sent: 02 October 2019 09:23

Hi!

I pushed -cip-rt version to kernel.org, which got me automatic test on gitlab:

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

Quoted 7 lines
Quoted 2 lines

...compile okay, but run_tests failed; unfortunately I don't quite understand what went wrong with the test. Can someone help?

It looks like test join #4665[0] failed due to internet connectivity issues in the lab.

I've re-run the job and it passes[1], so you should be okay.
I've also re-run the GitLab CI test job[2], so GitLab will show the pipeline as a success[3].

Thanks!

This time tests succeeded, but build is indicating problems, in case you wanted to investigate:

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

Anyway, it seems code is okay, so I'll proceed and create -cip-rt release.

Best regards,
Pavel

Signature · 9 lines
DENX Software Engineering GmbH,      Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 181 bytes
Desc: Digital signature
URL: <http://lists.cip-project.org/pipermail/cip-dev/attachments/20191002/c799d60b/attachment.sig>