Skip to contentSkip to conversation

glibc: ptest: Add lib32-glibc-tests PROVIDES

PATCH In review pgowda 5 participants 9 messages May 2, 2022 – May 13, 2022

lore
Share & tools
lore

pgowda

author
#0 lore raw

PATCH 1/1 glibc: ptest: Add lib32-glibc-tests PROVIDES

While running lib32-glibc-tests, it fails with the following error as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests and is not able to recognize the multilibs.

ERROR: Nothing PROVIDES 'lib32-glibc-tests'

---
 meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/glibc/glibc-tests_2.35.bb +1 -1
index 414f8660de..2515e98bb3 100644
@@ -18,7 +18,7 @@ python __anonymous() {
        d.setVar("PROVIDES", "${PN} ${PN}-ptest")
        d.setVar("RPROVIDES", "${PN} ${PN}-ptest")
 
-       d.setVar("BBCLASSEXTEND", "")
+#       d.setVar("BBCLASSEXTEND", "")
        d.setVar("RRECOMMENDS", "")
        d.setVar("SYSTEMD_SERVICE:nscd", "")
        d.setVar("SYSTEMD_PACKAGES", "")
Signature · 1 line
2.35.1
#1 lore raw

Hi Pgowda,

Pgowda <[email protected]> escreveu no dia segunda, 2/05/2022 à(s) 09:09:

Quoted 17 lines

While running lib32-glibc-tests, it fails with the following error as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests and is not able to recognize the multilibs.

ERROR: Nothing PROVIDES 'lib32-glibc-tests'

---
 meta/recipes-core/glibc/glibc-tests_2.35.bb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
meta/recipes-core/glibc/glibc-tests_2.35.bb +0 -0
index 414f8660de..2515e98bb3 100644

meta/recipes-core/glibc/glibc-tests_2.35.bb python __anonymous() { · line 22

Quoted 6 lines
meta/recipes-core/glibc/glibc-tests_2.35.bb +1 -1
@@ -18,7 +18,7 @@ python __anonymous() {
        d.setVar("PROVIDES", "${PN} ${PN}-ptest")
        d.setVar("RPROVIDES", "${PN} ${PN}-ptest")
 
-       d.setVar("BBCLASSEXTEND", "")
+#       d.setVar("BBCLASSEXTEND", "")
 

Why commenting? this line can be removed and the git will take care of storing the change for future reference.

Jose

Quoted 18 lines
meta/recipes-core/glibc/glibc-tests_2.35.bb +0 -0
        d.setVar("RRECOMMENDS", "")
        d.setVar("SYSTEMD_SERVICE:nscd", "")
        d.setVar("SYSTEMD_PACKAGES", "")

--
2.35.1

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group. View/Reply Online (#165161):
https://lists.openembedded.org/g/openembedded-core/message/165161
Mute This Topic: https://lists.openembedded.org/mt/90831085/5052612
Group Owner: [email protected]
Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [ [email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 3 lines
Best regards,

José Quaresma
#2 lore raw
In reply to pgowda

Hi Pgowda,

Il giorno Mon, 2 May 2022 01:08:51 -0700
"Pgowda" <[email protected]> ha scritto:

Quoted 7 lines

While running lib32-glibc-tests, it fails with the following error as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests and is not able to recognize the multilibs.

ERROR: Nothing PROVIDES 'lib32-glibc-tests'

It seems like this patch is triggering some build error:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100/steps/19/logs/stdio

Signature · 3 lines
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
author
#3 lore raw

Hi Luca,

Thanks for providing the build error details with the patch. I did a run of the provided test after applying the patch and found that it runs successfully.
Please find the details of the log that were run successfully.

============================================================================================

2022-05-05 00:28:57,451 - oe-selftest - INFO - RESULTS -
gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx: PASSED (1137.41s)
2022-05-05 00:28:57,451 - oe-selftest - INFO - RESULTS -
glibc.GlibcSelfTestSystemEmulated.test_glibc: PASSED (41315.04s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project: PASSED (53.59s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_can_compile_c_program: PASSED (0.35s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support: PASSED
(0.01s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
runqemu.QemuTest.test_qemu_can_shutdown: PASSED (30.84s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
gcc.GccLibSspSelfTestSystemEmulated.test_libssp: SKIPPED (4.00s)
2022-05-05 00:28:59,823 - oe-selftest - INFO - SUMMARY:
2022-05-05 00:28:59,824 - oe-selftest - INFO - oe-selftest () - Ran 15
tests in 49960.164s
2022-05-05 00:28:59,824 - oe-selftest - INFO - oe-selftest - OK - All

required tests passed (successes=14, skipped=1, failures=0, errors=0)
============================================================================================

I did a run of the following command in latest Poky sources after applying the patch:-
oe-selftest -a -t machine -t toolchain-system

pgowda@ala-lpggp3:/pgowda/check$ uname -a
Linux 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

The following error was seen in the log provided which triggered the failure. However, I could not see the issue when I ran the Oe-selftest.

Exception: Failed to setup NFS mount on target ('mount: mounting 192.168.7.13:/home/pokybuild/yocto-worker/qemux86-64/build/build-st-1441279/tmp/work on /home/pokybuild/yocto-worker/qemux86-64/build/build-st-1441279/tmp/work
failed: Input/output error')

Can you please provide me with the details of the environment to check and reproduce the issue?

Thanks
Pgowda

Quoted 24 lines · Luca Ceresoli

Hi Pgowda,

Il giorno Mon, 2 May 2022 01:08:51 -0700
"Pgowda" <[email protected]> ha scritto:

Quoted 7 lines

While running lib32-glibc-tests, it fails with the following error as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests and is not able to recognize the multilibs.

ERROR: Nothing PROVIDES 'lib32-glibc-tests'

It seems like this patch is triggering some build error:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100/steps/19/logs/stdio

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

author
#4 lore raw

Hi Luca,

I have checked it again at my end and it seems to be working fine. The error is related to "setup NFS mount on target" and does not seem to be related to the patch.
Can the patch be included again while running oe-selftest and checked?

Thanks,
Pgowda

Quoted 78 lines · pgowda cve

Hi Luca,

Thanks for providing the build error details with the patch. I did a run of the provided test after applying the patch and found that it runs successfully.
Please find the details of the log that were run successfully.

============================================================================================

2022-05-05 00:28:57,451 - oe-selftest - INFO - RESULTS -
gcc.GxxCrossSelfTestSystemEmulated.test_cross_gxx: PASSED (1137.41s)
2022-05-05 00:28:57,451 - oe-selftest - INFO - RESULTS -
glibc.GlibcSelfTestSystemEmulated.test_glibc: PASSED (41315.04s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_can_build_cpio_project: PASSED (53.59s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_can_compile_c_program: PASSED (0.35s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
meta_ide.MetaIDE.test_meta_ide_had_installed_meta_ide_support: PASSED
(0.01s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
runqemu.QemuTest.test_qemu_can_shutdown: PASSED (30.84s)
2022-05-05 00:28:57,452 - oe-selftest - INFO - RESULTS -
gcc.GccLibSspSelfTestSystemEmulated.test_libssp: SKIPPED (4.00s)
2022-05-05 00:28:59,823 - oe-selftest - INFO - SUMMARY:
2022-05-05 00:28:59,824 - oe-selftest - INFO - oe-selftest () - Ran 15
tests in 49960.164s
2022-05-05 00:28:59,824 - oe-selftest - INFO - oe-selftest - OK - All

required tests passed (successes=14, skipped=1, failures=0, errors=0)
============================================================================================

I did a run of the following command in latest Poky sources after applying the patch:-
oe-selftest -a -t machine -t toolchain-system

pgowda@ala-lpggp3:/pgowda/check$ uname -a
Linux 5.4.0-107-generic #121~18.04.1-Ubuntu SMP Thu Mar 24 17:21:33
UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

The following error was seen in the log provided which triggered the failure. However, I could not see the issue when I ran the Oe-selftest.

Exception: Failed to setup NFS mount on target ('mount: mounting 192.168.7.13:/home/pokybuild/yocto-worker/qemux86-64/build/build-st-1441279/tmp/work on /home/pokybuild/yocto-worker/qemux86-64/build/build-st-1441279/tmp/work
failed: Input/output error')

Can you please provide me with the details of the environment to check and reproduce the issue?

Thanks
Pgowda

Quoted 24 lines · Luca Ceresoli

Hi Pgowda,

Il giorno Mon, 2 May 2022 01:08:51 -0700
"Pgowda" <[email protected]> ha scritto:

Quoted 7 lines

While running lib32-glibc-tests, it fails with the following error as the recipe is not PROVIDED. BBCLASSEXTEND is cleaned in glibc-tests and is not able to recognize the multilibs.

ERROR: Nothing PROVIDES 'lib32-glibc-tests'

It seems like this patch is triggering some build error:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100/steps/19/logs/stdio

--
Luca Ceresoli, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

#5 lore raw
Quoted 6 lines · Pgowda

Hi Luca,

I have checked it again at my end and it seems to be working fine. The error is related to "setup NFS mount on target" and does not seem to be related to the patch.
Can the patch be included again while running oe-selftest and checked?

No, it doesn't need to be checked again, it is breaking oe-selftest when used to test target machine glibc.

The change in in the glibc ptest recipe and the failure is in "glibc.GlibcSelfTestSystemEmulated.test_glibc" i.e. in the glibc tests so there is a clear connection between these two things.

We need to work out why it breaks it and fix that. Running it again doesn't help us at all.

What you really need is a way to replicate the failure. How did you test this locally?

Cheers,

Richard

author
#6 lore raw

Hi Richard,

Thanks for the confirmation.

Quoted 2 lines

What you really need is a way to replicate the failure. How did you test this locally?

I ran the complete Oe-selftest suite with the latest poky sources after applying the patch:-
oe-selftest -a -t machine -t toolchain-system

Can you please let me know if I have to export any specific environment to replicate the failure?

Thanks,
Pgowda

Quoted 27 lines · On Fri, May 13, 2022 at 6:15 PM <[email protected]> wrote:
Quoted 6 lines · Pgowda

Hi Luca,

I have checked it again at my end and it seems to be working fine. The error is related to "setup NFS mount on target" and does not seem to be related to the patch.
Can the patch be included again while running oe-selftest and checked?

No, it doesn't need to be checked again, it is breaking oe-selftest when used to test target machine glibc.

The change in in the glibc ptest recipe and the failure is in "glibc.GlibcSelfTestSystemEmulated.test_glibc" i.e. in the glibc tests so there is a clear connection between these two things.

We need to work out why it breaks it and fix that. Running it again doesn't help us at all.

What you really need is a way to replicate the failure. How did you test this locally?

Cheers,

Richard

#7 lore raw
Quoted 4 lines · Pgowda

Hi Richard,

Thanks for the confirmation.

Quoted 8 lines
Quoted 2 lines

What you really need is a way to replicate the failure. How did you test this locally?

I ran the complete Oe-selftest suite with the latest poky sources after applying the patch:-
oe-selftest -a -t machine -t toolchain-system

Can you please let me know if I have to export any specific environment to replicate the failure?

Please explain what changes you made to you local.conf if any.

The only one that stands out to me in:

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100

is :

INHERIT += 'testimage'
but perhaps that's done automatically for:
oe-selftest -a -t machine -t toolchain-system

Also, what host distro did you use?
The failure happened on an alma distro: worker = alma8-ty-2https://almalinux.org/

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100

but that may also be incidental rather than required to see the error.

../Randy

Quoted 39 lines

Thanks,
Pgowda

Quoted 34 lines · On Fri, May 13, 2022 at 6:15 PM<[email protected]> wrote:
Quoted 6 lines · Pgowda

Hi Luca,

I have checked it again at my end and it seems to be working fine. The error is related to "setup NFS mount on target" and does not seem to be related to the patch.
Can the patch be included again while running oe-selftest and checked?

No, it doesn't need to be checked again, it is breaking oe-selftest when used to test target machine glibc.

The change in in the glibc ptest recipe and the failure is in "glibc.GlibcSelfTestSystemEmulated.test_glibc" i.e. in the glibc tests so there is a clear connection between these two things.

We need to work out why it breaks it and fix that. Running it again doesn't help us at all.

What you really need is a way to replicate the failure. How did you test this locally?

Cheers,

Richard

-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#165559):https://lists.openembedded.org/g/openembedded-core/message/165559 Mute This Topic:https://lists.openembedded.org/mt/90831085/3616765
Group Owner:[email protected] Unsubscribe:https://lists.openembedded.org/g/openembedded-core/unsub [[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-

Signature · 2 lines
# Randy MacLeod
# Wind River Linux
#8 lore raw
Quoted 28 lines · Randy MacLeod

On 2022-05-13 08:56, Pgowda wrote:

Quoted 8 lines

Hi Richard,

Thanks for the confirmation.

Quoted 3 lines

What you really need is a way to replicate the failure. How did you
test this locally?

Quoted 6 lines

I ran the complete Oe-selftest suite with the latest poky sources after applying the patch:-
oe-selftest -a -t machine -t toolchain-system

Can you please let me know if I have to export any specific environment to replicate the failure?

Please explain what changes you made to you local.conf if any.
The only one that stands out to me in:
https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100
is :
 INHERIT += 'testimage'
but perhaps that's done automatically for:
 oe-selftest -a -t machine -t toolchain-system Also, what host distro did you use?
The failure happened on an alma distro: worker = alma8-ty-2
https://almalinux.org/

Quoted 6 lines

https://autobuilder.yoctoproject.org/typhoon/#/builders/73/builds/5100

but that may also be incidental rather than required to see the error.

Also, going back to the original patch being tested here, why is it needed? What are you doing to reproduce that failure?

I'm guessing you have to have enabled multilibs? Do we expect that to work with the glibc tests?

Cheers,

Richard