oe-selftest for devtool failed

oe-selftest for devtool failed

[Frédéric Martinsons]

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

Hello,

in the course of building tests around this patch:
https://patchwork.yoctoproject.org/project/oe-core/patch/855931994ea68c0691d0a67ce2ccad947e77229f.1679904677.git.frederic.martinsons@gmail.com/

I tried to run oe-selftest with the current poky master
(e3afe166940686b05626c3298bc4369296b7d8a3) and I didn't manage to have
the test_devtool_modify and test_devtool_modify_git worked.

First, I was not aware of oe-selftest to be impacted by my previous build ,
I had issues some devtool but even if there was no more active devtool, the
tests failed with the following
error:

ERROR: Found duplicated BBFILE_COLLECTIONS 'workspacelayer', check
bblayers.conf or layer.conf to fix it.
Found duplicated BBFILE_COLLECTIONS 'workspacelayer', check bblayers.conf
or layer.conf to fix it.
Traceback (most recent call last):
  File
"/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/scripts/lib/devtool/__init__.py",
line 109, in setup_tinfoil
    tinfoil.prepare(config_only)
  File
"/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/bitbake/lib/bb/tinfoil.py",
line 417, in prepare
    self.run_actions(config_params)
  File
"/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/bitbake/lib/bb/tinfoil.py",
line 432, in run_actions
    raise TinfoilUIException(ret)
bb.tinfoil.TinfoilUIException: 1


After removing my $BDIR/workspace , the test got further but ends in
strange failure (for test_devtool_modify):

NOTE: recipe shadow-native-4.13-r0: task do_install: Failed
ERROR: Task
(virtual:native:/tmp/devtoolqa_7buhvon/core-copy/meta/recipes-extended/shadow/shadow_4.13.bb:do_install)
failed with exit code '1'
NOTE: recipe rsync-native-3.2.7-r0: task do_populate_sysroot: Succeeded
NOTE: recipe file-native-5.44-r0: task do_populate_sysroot: Succeeded
NOTE: recipe gmp-native-6.2.1-r0: task do_compile: Succeeded
NOTE: recipe pkgconfig-native-0.29.2+gitAUTOINC+d97db4fae4-r0: task
do_configure: Succeeded
NOTE: recipe cross-localedef-native-2.37-r0: task do_configure: Succeeded
NOTE: recipe libunistring-native-1.1-r0: task do_configure: Succeeded
NOTE: recipe bison-native-3.8.2-r0: task do_configure: Succeeded
NOTE: recipe linux-yocto-6.1.20+gitAUTOINC+a8881762b5_423e199669-r0: task
do_fetch: Succeeded
NOTE: Tasks Summary: Attempted 799 tasks of which 99 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:

virtual:native:/tmp/devtoolqa_7buhvon/core-copy/meta/recipes-extended/shadow/shadow_4.13.bb:
do_install
Summary: There was 1 WARNING message.
Summary: There was 1 ERROR message, returning a non-zero exit code.
----------------------------------------------------------------------
2023-03-28 07:16:21,876 - oe-selftest - INFO - Ran 1 test in 911.101s
2023-03-28 07:16:21,876 - oe-selftest - INFO - FAILED
2023-03-28 07:16:21,877 - oe-selftest - INFO -  (failures=1)
2023-03-28 07:16:29,802 - oe-selftest - INFO - RESULTS:
2023-03-28 07:16:29,803 - oe-selftest - INFO - RESULTS -
devtool.DevtoolModifyTests.test_devtool_modify: FAILED (905.11s)
2023-03-28 07:16:29,808 - oe-selftest - INFO - SUMMARY:
2023-03-28 07:16:29,808 - oe-selftest - INFO - oe-selftest () - Ran 1 test
in 911.105s
2023-03-28 07:16:29,808 - oe-selftest - INFO - oe-selftest - FAIL -
Required tests failed (successes=0, skipped=0, failures=1, errors=0)

Does this ring a bell to someone ? How can I manage to make these tests
succeed ?

[-- Attachment #2: Type: text/html, Size: 3878 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Alexander Kanavin]

oe-selftest is executed on the autobuilder all the time, so if it
fails this way we'd know.

Can you try making a pristine build from scratch and run oe-selftest
in it? You should set up sstate cache outside of the build directory,
so that selftest would reuse it.

Alex

On Tue, 28 Mar 2023 at 09:28, Frederic Martinsons
<frederic.martinsons@gmail.com> wrote:
>
> Hello,
>
> in the course of building tests around this patch: https://patchwork.yoctoproject.org/project/oe-core/patch/855931994ea68c0691d0a67ce2ccad947e77229f.1679904677.git.frederic.martinsons@gmail.com/
>
> I tried to run oe-selftest with the current poky master (e3afe166940686b05626c3298bc4369296b7d8a3) and I didn't manage to have the test_devtool_modify and test_devtool_modify_git worked.
>
> First, I was not aware of oe-selftest to be impacted by my previous build , I had issues some devtool but even if there was no more active devtool, the tests failed with the following
> error:
>
> ERROR: Found duplicated BBFILE_COLLECTIONS 'workspacelayer', check bblayers.conf or layer.conf to fix it.
> Found duplicated BBFILE_COLLECTIONS 'workspacelayer', check bblayers.conf or layer.conf to fix it.
> Traceback (most recent call last):
>   File "/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/scripts/lib/devtool/__init__.py", line 109, in setup_tinfoil
>     tinfoil.prepare(config_only)
>   File "/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/bitbake/lib/bb/tinfoil.py", line 417, in prepare
>     self.run_actions(config_params)
>   File "/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/bitbake/lib/bb/tinfoil.py", line 432, in run_actions
>     raise TinfoilUIException(ret)
> bb.tinfoil.TinfoilUIException: 1
>
>
> After removing my $BDIR/workspace , the test got further but ends in strange failure (for test_devtool_modify):
>
> NOTE: recipe shadow-native-4.13-r0: task do_install: Failed
> ERROR: Task (virtual:native:/tmp/devtoolqa_7buhvon/core-copy/meta/recipes-extended/shadow/shadow_4.13.bb:do_install) failed with exit code '1'
> NOTE: recipe rsync-native-3.2.7-r0: task do_populate_sysroot: Succeeded
> NOTE: recipe file-native-5.44-r0: task do_populate_sysroot: Succeeded
> NOTE: recipe gmp-native-6.2.1-r0: task do_compile: Succeeded
> NOTE: recipe pkgconfig-native-0.29.2+gitAUTOINC+d97db4fae4-r0: task do_configure: Succeeded
> NOTE: recipe cross-localedef-native-2.37-r0: task do_configure: Succeeded
> NOTE: recipe libunistring-native-1.1-r0: task do_configure: Succeeded
> NOTE: recipe bison-native-3.8.2-r0: task do_configure: Succeeded
> NOTE: recipe linux-yocto-6.1.20+gitAUTOINC+a8881762b5_423e199669-r0: task do_fetch: Succeeded
> NOTE: Tasks Summary: Attempted 799 tasks of which 99 didn't need to be rerun and 1 failed.
>
> Summary: 1 task failed:
>   virtual:native:/tmp/devtoolqa_7buhvon/core-copy/meta/recipes-extended/shadow/shadow_4.13.bb:do_install
> Summary: There was 1 WARNING message.
> Summary: There was 1 ERROR message, returning a non-zero exit code.
> ----------------------------------------------------------------------
> 2023-03-28 07:16:21,876 - oe-selftest - INFO - Ran 1 test in 911.101s
> 2023-03-28 07:16:21,876 - oe-selftest - INFO - FAILED
> 2023-03-28 07:16:21,877 - oe-selftest - INFO -  (failures=1)
> 2023-03-28 07:16:29,802 - oe-selftest - INFO - RESULTS:
> 2023-03-28 07:16:29,803 - oe-selftest - INFO - RESULTS - devtool.DevtoolModifyTests.test_devtool_modify: FAILED (905.11s)
> 2023-03-28 07:16:29,808 - oe-selftest - INFO - SUMMARY:
> 2023-03-28 07:16:29,808 - oe-selftest - INFO - oe-selftest () - Ran 1 test in 911.105s
> 2023-03-28 07:16:29,808 - oe-selftest - INFO - oe-selftest - FAIL - Required tests failed (successes=0, skipped=0, failures=1, errors=0)
>
> Does this ring a bell to someone ? How can I manage to make these tests succeed ?
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179206): https://lists.openembedded.org/g/openembedded-core/message/179206
> Mute This Topic: https://lists.openembedded.org/mt/97900549/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [OE-core] oe-selftest for devtool failed

[Richard Purdie]

On Tue, 2023-03-28 at 10:54 +0200, Alexander Kanavin wrote:
> oe-selftest is executed on the autobuilder all the time, so if it
> fails this way we'd know.
> 
> Can you try making a pristine build from scratch and run oe-selftest
> in it? You should set up sstate cache outside of the build directory,
> so that selftest would reuse it.

It is almost certainly some local setting or other difference which is
causing the issue. I'd like to know what it is though so we can try and
improve the test execution and avoid this.

Cheers,

Richard

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

[-- Attachment #1.1: Type: text/plain, Size: 907 bytes --]

I just finished a pristine build of core-image-sato on poky master,
and set up SSTATE_DIR in my local.conf.
Tests are now ok, I can start to write some now.

If anyone is interested , please find attached the full log of the two
first failures.

On Tue, 28 Mar 2023 at 14:28, Richard Purdie <
richard.purdie@linuxfoundation.org> wrote:

> On Tue, 2023-03-28 at 10:54 +0200, Alexander Kanavin wrote:
> > oe-selftest is executed on the autobuilder all the time, so if it
> > fails this way we'd know.
> >
> > Can you try making a pristine build from scratch and run oe-selftest
> > in it? You should set up sstate cache outside of the build directory,
> > so that selftest would reuse it.
>
> It is almost certainly some local setting or other difference which is
> causing the issue. I'd like to know what it is though so we can try and
> improve the test execution and avoid this.
>
> Cheers,
>
> Richard
>

[-- Attachment #1.2: Type: text/html, Size: 1327 bytes --]

[-- Attachment #2: oe-selftest_test_devtool_modify_git.log.gz --]
[-- Type: application/gzip, Size: 27108 bytes --]

[-- Attachment #3: oe-selftest_test_devtool_modify.log.gz --]
[-- Type: application/gzip, Size: 36090 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

[-- Attachment #1.1: Type: text/plain, Size: 2454 bytes --]

Ah sorry, I take it back, only test_devtool_modify passed, I still
have errors on test_devtool_modify_git:

NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at
../../../../../../../../../../../../tmp/devtoolqantpyns7p/configure
ERROR: psplash-0.1+git999-r0 do_configure:
ExecutionError('/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.3768172',
1, None, None)
ERROR: Logfile of failure stored in:
/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.3768172
NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
ERROR: Task
(/tmp/devtoolqak9io3385/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to be
rerun and 1 failed.

Summary: 1 task failed:
  /tmp/devtoolqak9io3385/core-copy/meta/recipes-core/psplash/psplash_git.bb:
do_configure
Summary: There were 2 ERROR messages, returning a non-zero exit code.

Full log of this run joined.

Note that my machine is a dedicated build machine (ubuntu 22.04, 32 Xeon
Silver, 126GB ram), I'll
try on my personnal computer if I manage to have enough disk size



On Tue, 28 Mar 2023 at 14:40, Frédéric Martinsons <
frederic.martinsons@gmail.com> wrote:

> I just finished a pristine build of core-image-sato on poky master,
> and set up SSTATE_DIR in my local.conf.
> Tests are now ok, I can start to write some now.
>
> If anyone is interested , please find attached the full log of the two
> first failures.
>
> On Tue, 28 Mar 2023 at 14:28, Richard Purdie <
> richard.purdie@linuxfoundation.org> wrote:
>
>> On Tue, 2023-03-28 at 10:54 +0200, Alexander Kanavin wrote:
>> > oe-selftest is executed on the autobuilder all the time, so if it
>> > fails this way we'd know.
>> >
>> > Can you try making a pristine build from scratch and run oe-selftest
>> > in it? You should set up sstate cache outside of the build directory,
>> > so that selftest would reuse it.
>>
>> It is almost certainly some local setting or other difference which is
>> causing the issue. I'd like to know what it is though so we can try and
>> improve the test execution and avoid this.
>>
>> Cheers,
>>
>> Richard
>>
>

[-- Attachment #1.2: Type: text/html, Size: 3261 bytes --]

[-- Attachment #2: oe-selftest_test_devtool_modify_git_2.log.gz --]
[-- Type: application/gzip, Size: 5020 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Richard Purdie]

On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
> I just finished a pristine build of core-image-sato on poky master,
> and set up SSTATE_DIR in my local.conf.
> Tests are now ok, I can start to write some now.
> 
> If anyone is interested , please find attached the full log of the
> two first failures.

Having the errors helps, thanks.

The short summary is these two lines:

libtirpc-native
| chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig': Invalid argument

shadow-native
| chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail': Invalid argument


I'm wondering if the fact the build is under /var might be triggering
something somehow...

Cheers,

Richard

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

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

Note that I managed to build libtirpc-native and shadow-native with bitbake
(and the same setup).

I currently try the build on another machine and under /home.

I'll tell you the results soon

Le mar. 28 mars 2023, 15:13, Richard Purdie <
richard.purdie@linuxfoundation.org> a écrit :

> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
> > I just finished a pristine build of core-image-sato on poky master,
> > and set up SSTATE_DIR in my local.conf.
> > Tests are now ok, I can start to write some now.
> >
> > If anyone is interested , please find attached the full log of the
> > two first failures.
>
> Having the errors helps, thanks.
>
> The short summary is these two lines:
>
> libtirpc-native
> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig':
> Invalid argument
>
> shadow-native
> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail':
> Invalid argument
>
>
> I'm wondering if the fact the build is under /var might be triggering
> something somehow...
>
> Cheers,
>
> Richard
>

[-- Attachment #2: Type: text/html, Size: 1975 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

[-- Attachment #1.1: Type: text/plain, Size: 4695 bytes --]

I rebuilt a poky master from scratch on another machine (Ubuntu 22.04 , 16
Xeon, 124 Gb RAM), it took
 2h30mn to finish (note that rust-llvm-native and llvm-native both took
around 1h each to be built).

I have two questions for my curiosity:
   - why rust things (cargo-native, librsvg)  are the last artifacts built
on core-image-sato ? it seems strange at first look
(but may be explained by packages embedded by this image, I didn't look on
what are the dependencies of this image)
   - my pristine BDIR took around 90 GB , maybe the page
https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
that we need 50 GB of free space needs to be reviewed (unless it was
written with another image than core-image-sato in mind) ?

Apart from that,  I have the exact same error on test_devtool_modify_git
that I had on the other machine under /var build dir:

NOTE: Running setscene task 210 of 213
(virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:
do_populate_sysroot_setscene)
NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task
do_populate_sysroot_setscene: Started
NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task
do_populate_sysroot_setscene: Succeeded
NOTE: Running task 896 of 918
(/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
do_prepare_recipe_sysroot)
NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Started
NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot:
Succeeded
NOTE: Running task 910 of 918
(/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
do_configure)
NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at
../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
ERROR: psplash-0.1+git999-r0 do_configure:
ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375',
1, None, None)
ERROR: Logfile of failure stored in:
/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
ERROR: Task
(/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
failed with exit code '1'
NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to be
rerun and 1 failed.

Full test log joined (I would like to join also the log of do_configure
step but it seems that the test do a cleanall of the recipe during its tear
down method)

I'm kind of stuck here since I cannot develop more oe-selftest tests if I
didn't even manage to make the existing ones succeed.
Can someone give me the setup of this autobuilder where Alexander talked
about ?

I could try to get as close as possible to the autobuilder setup if the
oe-selftest is ok there.

On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <
frederic.martinsons@gmail.com> wrote:

> Note that I managed to build libtirpc-native and shadow-native with
> bitbake (and the same setup).
>
> I currently try the build on another machine and under /home.
>
> I'll tell you the results soon
>
> Le mar. 28 mars 2023, 15:13, Richard Purdie <
> richard.purdie@linuxfoundation.org> a écrit :
>
>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
>> > I just finished a pristine build of core-image-sato on poky master,
>> > and set up SSTATE_DIR in my local.conf.
>> > Tests are now ok, I can start to write some now.
>> >
>> > If anyone is interested , please find attached the full log of the
>> > two first failures.
>>
>> Having the errors helps, thanks.
>>
>> The short summary is these two lines:
>>
>> libtirpc-native
>> | chown: changing ownership of
>> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig':
>> Invalid argument
>>
>> shadow-native
>> | chown: changing ownership of
>> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail':
>> Invalid argument
>>
>>
>> I'm wondering if the fact the build is under /var might be triggering
>> something somehow...
>>
>> Cheers,
>>
>> Richard
>>
>

[-- Attachment #1.2: Type: text/html, Size: 5779 bytes --]

[-- Attachment #2: oe-selftest_test_devtool_modify_git_new_machine_home.log.gz --]
[-- Type: application/gzip, Size: 5013 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Alexander Kanavin]

Would you be able to read the failing test, and replicate the steps it
does by hand? If we can narrow down the precise point where it fails,
that would already help.

Alex

On Tue, 28 Mar 2023 at 20:01, Frédéric Martinsons
<frederic.martinsons@gmail.com> wrote:
>
> I rebuilt a poky master from scratch on another machine (Ubuntu 22.04 , 16 Xeon, 124 Gb RAM), it took
>  2h30mn to finish (note that rust-llvm-native and llvm-native both took around 1h each to be built).
>
> I have two questions for my curiosity:
>    - why rust things (cargo-native, librsvg)  are the last artifacts built on core-image-sato ? it seems strange at first look
> (but may be explained by packages embedded by this image, I didn't look on what are the dependencies of this image)
>    - my pristine BDIR took around 90 GB , maybe the page https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
> that we need 50 GB of free space needs to be reviewed (unless it was written with another image than core-image-sato in mind) ?
>
> Apart from that,  I have the exact same error on test_devtool_modify_git that I had on the other machine under /var build dir:
>
> NOTE: Running setscene task 210 of 213 (virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_populate_sysroot_setscene)
> NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Started
> NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Succeeded
> NOTE: Running task 896 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_prepare_recipe_sysroot)
> NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Started
> NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Succeeded
> NOTE: Running task 910 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
> NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
> ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at ../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
> ERROR: psplash-0.1+git999-r0 do_configure: ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375', 1, None, None)
> ERROR: Logfile of failure stored in: /home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
> NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
> ERROR: Task (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure) failed with exit code '1'
> NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to be rerun and 1 failed.
>
> Full test log joined (I would like to join also the log of do_configure step but it seems that the test do a cleanall of the recipe during its tear down method)
>
> I'm kind of stuck here since I cannot develop more oe-selftest tests if I didn't even manage to make the existing ones succeed.
> Can someone give me the setup of this autobuilder where Alexander talked about ?
>
> I could try to get as close as possible to the autobuilder setup if the oe-selftest is ok there.
>
> On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <frederic.martinsons@gmail.com> wrote:
>>
>> Note that I managed to build libtirpc-native and shadow-native with bitbake (and the same setup).
>>
>> I currently try the build on another machine and under /home.
>>
>> I'll tell you the results soon
>>
>> Le mar. 28 mars 2023, 15:13, Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :
>>>
>>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
>>> > I just finished a pristine build of core-image-sato on poky master,
>>> > and set up SSTATE_DIR in my local.conf.
>>> > Tests are now ok, I can start to write some now.
>>> >
>>> > If anyone is interested , please find attached the full log of the
>>> > two first failures.
>>>
>>> Having the errors helps, thanks.
>>>
>>> The short summary is these two lines:
>>>
>>> libtirpc-native
>>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig': Invalid argument
>>>
>>> shadow-native
>>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail': Invalid argument
>>>
>>>
>>> I'm wondering if the fact the build is under /var might be triggering
>>> something somehow...
>>>
>>> Cheers,
>>>
>>> Richard

Re: [OE-core] oe-selftest for devtool failed

[Alexander Kanavin]

Btw, I'm beginning to suspect something isn't right about /tmp on your
build host. The test requires being able to write executable scripts
into that, and then run them. I just ran the
devtool.DevtoolModifyTests.test_devtool_modify_git here, and it
succeeded.

Alex

On Tue, 28 Mar 2023 at 20:14, Alexander Kanavin via
lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
wrote:
>
> Would you be able to read the failing test, and replicate the steps it
> does by hand? If we can narrow down the precise point where it fails,
> that would already help.
>
> Alex
>
> On Tue, 28 Mar 2023 at 20:01, Frédéric Martinsons
> <frederic.martinsons@gmail.com> wrote:
> >
> > I rebuilt a poky master from scratch on another machine (Ubuntu 22.04 , 16 Xeon, 124 Gb RAM), it took
> >  2h30mn to finish (note that rust-llvm-native and llvm-native both took around 1h each to be built).
> >
> > I have two questions for my curiosity:
> >    - why rust things (cargo-native, librsvg)  are the last artifacts built on core-image-sato ? it seems strange at first look
> > (but may be explained by packages embedded by this image, I didn't look on what are the dependencies of this image)
> >    - my pristine BDIR took around 90 GB , maybe the page https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
> > that we need 50 GB of free space needs to be reviewed (unless it was written with another image than core-image-sato in mind) ?
> >
> > Apart from that,  I have the exact same error on test_devtool_modify_git that I had on the other machine under /var build dir:
> >
> > NOTE: Running setscene task 210 of 213 (virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_populate_sysroot_setscene)
> > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Started
> > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Succeeded
> > NOTE: Running task 896 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_prepare_recipe_sysroot)
> > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Started
> > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Succeeded
> > NOTE: Running task 910 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
> > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
> > ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at ../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
> > ERROR: psplash-0.1+git999-r0 do_configure: ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375', 1, None, None)
> > ERROR: Logfile of failure stored in: /home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
> > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
> > ERROR: Task (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure) failed with exit code '1'
> > NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to be rerun and 1 failed.
> >
> > Full test log joined (I would like to join also the log of do_configure step but it seems that the test do a cleanall of the recipe during its tear down method)
> >
> > I'm kind of stuck here since I cannot develop more oe-selftest tests if I didn't even manage to make the existing ones succeed.
> > Can someone give me the setup of this autobuilder where Alexander talked about ?
> >
> > I could try to get as close as possible to the autobuilder setup if the oe-selftest is ok there.
> >
> > On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <frederic.martinsons@gmail.com> wrote:
> >>
> >> Note that I managed to build libtirpc-native and shadow-native with bitbake (and the same setup).
> >>
> >> I currently try the build on another machine and under /home.
> >>
> >> I'll tell you the results soon
> >>
> >> Le mar. 28 mars 2023, 15:13, Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :
> >>>
> >>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
> >>> > I just finished a pristine build of core-image-sato on poky master,
> >>> > and set up SSTATE_DIR in my local.conf.
> >>> > Tests are now ok, I can start to write some now.
> >>> >
> >>> > If anyone is interested , please find attached the full log of the
> >>> > two first failures.
> >>>
> >>> Having the errors helps, thanks.
> >>>
> >>> The short summary is these two lines:
> >>>
> >>> libtirpc-native
> >>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig': Invalid argument
> >>>
> >>> shadow-native
> >>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail': Invalid argument
> >>>
> >>>
> >>> I'm wondering if the fact the build is under /var might be triggering
> >>> something somehow...
> >>>
> >>> Cheers,
> >>>
> >>> Richard
>
> -=-=-=-=-=-=-=-=-=-=-=-
> Links: You receive all messages sent to this group.
> View/Reply Online (#179243): https://lists.openembedded.org/g/openembedded-core/message/179243
> Mute This Topic: https://lists.openembedded.org/mt/97900549/1686489
> Group Owner: openembedded-core+owner@lists.openembedded.org
> Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
> -=-=-=-=-=-=-=-=-=-=-=-
>

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

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

Oh my, your assumption is surely correct, my build host /tmp is mounted
with noexec so no chance to execute
anything there:

[ (8) ] jenkins@cibuilder2:~$ mount | grep "/tmp"
tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,inode64)

Tomorrow, I'll try with another machine (or talk to the admin of the build
hosts) with a /tmp capable of executing things.

But the requirement to have /tmp directory capable of executing scripts was
not mentioned in the oe-selftest
page (https://wiki.yoctoproject.org/wiki/Oe-selftest) or the quick start
one (https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html)

I would have thought that devtool, if it needs to execute some scripts,
will execute them in its working directory and not
in /tmp of build hosts.... Is this something really expected ?


On Tue, 28 Mar 2023 at 20:28, Alexander Kanavin <alex.kanavin@gmail.com>
wrote:

> Btw, I'm beginning to suspect something isn't right about /tmp on your
> build host. The test requires being able to write executable scripts
> into that, and then run them. I just ran the
> devtool.DevtoolModifyTests.test_devtool_modify_git here, and it
> succeeded.
>
> Alex
>
> On Tue, 28 Mar 2023 at 20:14, Alexander Kanavin via
> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> wrote:
> >
> > Would you be able to read the failing test, and replicate the steps it
> > does by hand? If we can narrow down the precise point where it fails,
> > that would already help.
> >
> > Alex
> >
> > On Tue, 28 Mar 2023 at 20:01, Frédéric Martinsons
> > <frederic.martinsons@gmail.com> wrote:
> > >
> > > I rebuilt a poky master from scratch on another machine (Ubuntu 22.04
> , 16 Xeon, 124 Gb RAM), it took
> > >  2h30mn to finish (note that rust-llvm-native and llvm-native both
> took around 1h each to be built).
> > >
> > > I have two questions for my curiosity:
> > >    - why rust things (cargo-native, librsvg)  are the last artifacts
> built on core-image-sato ? it seems strange at first look
> > > (but may be explained by packages embedded by this image, I didn't
> look on what are the dependencies of this image)
> > >    - my pristine BDIR took around 90 GB , maybe the page
> https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
> > > that we need 50 GB of free space needs to be reviewed (unless it was
> written with another image than core-image-sato in mind) ?
> > >
> > > Apart from that,  I have the exact same error on
> test_devtool_modify_git that I had on the other machine under /var build
> dir:
> > >
> > > NOTE: Running setscene task 210 of 213
> (virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:
> do_populate_sysroot_setscene)
> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task
> do_populate_sysroot_setscene: Started
> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task
> do_populate_sysroot_setscene: Succeeded
> > > NOTE: Running task 896 of 918
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
> do_prepare_recipe_sysroot)
> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot:
> Started
> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot:
> Succeeded
> > > NOTE: Running task 910 of 918
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
> do_configure)
> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
> > > ERROR: psplash-0.1+git999-r0 do_configure: no configure script found
> at ../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
> > > ERROR: psplash-0.1+git999-r0 do_configure:
> ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375',
> 1, None, None)
> > > ERROR: Logfile of failure stored in:
> /home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
> > > ERROR: Task
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
> failed with exit code '1'
> > > NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to
> be rerun and 1 failed.
> > >
> > > Full test log joined (I would like to join also the log of
> do_configure step but it seems that the test do a cleanall of the recipe
> during its tear down method)
> > >
> > > I'm kind of stuck here since I cannot develop more oe-selftest tests
> if I didn't even manage to make the existing ones succeed.
> > > Can someone give me the setup of this autobuilder where Alexander
> talked about ?
> > >
> > > I could try to get as close as possible to the autobuilder setup if
> the oe-selftest is ok there.
> > >
> > > On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <
> frederic.martinsons@gmail.com> wrote:
> > >>
> > >> Note that I managed to build libtirpc-native and shadow-native with
> bitbake (and the same setup).
> > >>
> > >> I currently try the build on another machine and under /home.
> > >>
> > >> I'll tell you the results soon
> > >>
> > >> Le mar. 28 mars 2023, 15:13, Richard Purdie <
> richard.purdie@linuxfoundation.org> a écrit :
> > >>>
> > >>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
> > >>> > I just finished a pristine build of core-image-sato on poky master,
> > >>> > and set up SSTATE_DIR in my local.conf.
> > >>> > Tests are now ok, I can start to write some now.
> > >>> >
> > >>> > If anyone is interested , please find attached the full log of the
> > >>> > two first failures.
> > >>>
> > >>> Having the errors helps, thanks.
> > >>>
> > >>> The short summary is these two lines:
> > >>>
> > >>> libtirpc-native
> > >>> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig':
> Invalid argument
> > >>>
> > >>> shadow-native
> > >>> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail':
> Invalid argument
> > >>>
> > >>>
> > >>> I'm wondering if the fact the build is under /var might be triggering
> > >>> something somehow...
> > >>>
> > >>> Cheers,
> > >>>
> > >>> Richard
> >
> > -=-=-=-=-=-=-=-=-=-=-=-
> > Links: You receive all messages sent to this group.
> > View/Reply Online (#179243):
> https://lists.openembedded.org/g/openembedded-core/message/179243
> > Mute This Topic: https://lists.openembedded.org/mt/97900549/1686489
> > Group Owner: openembedded-core+owner@lists.openembedded.org
> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [
> alex.kanavin@gmail.com]
> > -=-=-=-=-=-=-=-=-=-=-=-
> >
>

[-- Attachment #2: Type: text/html, Size: 9560 bytes --]

Re: [OE-core] oe-selftest for devtool failed

[Alexander Kanavin]

Not devtool's fault. The selftest is written so that devtool is
instructed to use /tmp/... to extract sources, and not a workspace in
a build: 'devtool modify -x /tmp/...'.

Having /tmp with noexec is not common, that's why it isn't mentioned.
If the admin is not cooperative, you can hack the selftest definition
to use some other place.

Alex

On Tue, 28 Mar 2023 at 21:02, Frédéric Martinsons
<frederic.martinsons@gmail.com> wrote:
>
> Oh my, your assumption is surely correct, my build host /tmp is mounted with noexec so no chance to execute
> anything there:
>
> [ (8) ] jenkins@cibuilder2:~$ mount | grep "/tmp"
> tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,inode64)
>
> Tomorrow, I'll try with another machine (or talk to the admin of the build hosts) with a /tmp capable of executing things.
>
> But the requirement to have /tmp directory capable of executing scripts was not mentioned in the oe-selftest
> page (https://wiki.yoctoproject.org/wiki/Oe-selftest) or the quick start one (https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html)
>
> I would have thought that devtool, if it needs to execute some scripts, will execute them in its working directory and not
> in /tmp of build hosts.... Is this something really expected ?
>
>
> On Tue, 28 Mar 2023 at 20:28, Alexander Kanavin <alex.kanavin@gmail.com> wrote:
>>
>> Btw, I'm beginning to suspect something isn't right about /tmp on your
>> build host. The test requires being able to write executable scripts
>> into that, and then run them. I just ran the
>> devtool.DevtoolModifyTests.test_devtool_modify_git here, and it
>> succeeded.
>>
>> Alex
>>
>> On Tue, 28 Mar 2023 at 20:14, Alexander Kanavin via
>> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
>> wrote:
>> >
>> > Would you be able to read the failing test, and replicate the steps it
>> > does by hand? If we can narrow down the precise point where it fails,
>> > that would already help.
>> >
>> > Alex
>> >
>> > On Tue, 28 Mar 2023 at 20:01, Frédéric Martinsons
>> > <frederic.martinsons@gmail.com> wrote:
>> > >
>> > > I rebuilt a poky master from scratch on another machine (Ubuntu 22.04 , 16 Xeon, 124 Gb RAM), it took
>> > >  2h30mn to finish (note that rust-llvm-native and llvm-native both took around 1h each to be built).
>> > >
>> > > I have two questions for my curiosity:
>> > >    - why rust things (cargo-native, librsvg)  are the last artifacts built on core-image-sato ? it seems strange at first look
>> > > (but may be explained by packages embedded by this image, I didn't look on what are the dependencies of this image)
>> > >    - my pristine BDIR took around 90 GB , maybe the page https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
>> > > that we need 50 GB of free space needs to be reviewed (unless it was written with another image than core-image-sato in mind) ?
>> > >
>> > > Apart from that,  I have the exact same error on test_devtool_modify_git that I had on the other machine under /var build dir:
>> > >
>> > > NOTE: Running setscene task 210 of 213 (virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:do_populate_sysroot_setscene)
>> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Started
>> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0: task do_populate_sysroot_setscene: Succeeded
>> > > NOTE: Running task 896 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_prepare_recipe_sysroot)
>> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Started
>> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot: Succeeded
>> > > NOTE: Running task 910 of 918 (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
>> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
>> > > ERROR: psplash-0.1+git999-r0 do_configure: no configure script found at ../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
>> > > ERROR: psplash-0.1+git999-r0 do_configure: ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375', 1, None, None)
>> > > ERROR: Logfile of failure stored in: /home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
>> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
>> > > ERROR: Task (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure) failed with exit code '1'
>> > > NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need to be rerun and 1 failed.
>> > >
>> > > Full test log joined (I would like to join also the log of do_configure step but it seems that the test do a cleanall of the recipe during its tear down method)
>> > >
>> > > I'm kind of stuck here since I cannot develop more oe-selftest tests if I didn't even manage to make the existing ones succeed.
>> > > Can someone give me the setup of this autobuilder where Alexander talked about ?
>> > >
>> > > I could try to get as close as possible to the autobuilder setup if the oe-selftest is ok there.
>> > >
>> > > On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <frederic.martinsons@gmail.com> wrote:
>> > >>
>> > >> Note that I managed to build libtirpc-native and shadow-native with bitbake (and the same setup).
>> > >>
>> > >> I currently try the build on another machine and under /home.
>> > >>
>> > >> I'll tell you the results soon
>> > >>
>> > >> Le mar. 28 mars 2023, 15:13, Richard Purdie <richard.purdie@linuxfoundation.org> a écrit :
>> > >>>
>> > >>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
>> > >>> > I just finished a pristine build of core-image-sato on poky master,
>> > >>> > and set up SSTATE_DIR in my local.conf.
>> > >>> > Tests are now ok, I can start to write some now.
>> > >>> >
>> > >>> > If anyone is interested , please find attached the full log of the
>> > >>> > two first failures.
>> > >>>
>> > >>> Having the errors helps, thanks.
>> > >>>
>> > >>> The short summary is these two lines:
>> > >>>
>> > >>> libtirpc-native
>> > >>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig': Invalid argument
>> > >>>
>> > >>> shadow-native
>> > >>> | chown: changing ownership of '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail': Invalid argument
>> > >>>
>> > >>>
>> > >>> I'm wondering if the fact the build is under /var might be triggering
>> > >>> something somehow...
>> > >>>
>> > >>> Cheers,
>> > >>>
>> > >>> Richard
>> >
>> > -=-=-=-=-=-=-=-=-=-=-=-
>> > Links: You receive all messages sent to this group.
>> > View/Reply Online (#179243): https://lists.openembedded.org/g/openembedded-core/message/179243
>> > Mute This Topic: https://lists.openembedded.org/mt/97900549/1686489
>> > Group Owner: openembedded-core+owner@lists.openembedded.org
>> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub [alex.kanavin@gmail.com]
>> > -=-=-=-=-=-=-=-=-=-=-=-
>> >

Re: [OE-core] oe-selftest for devtool failed

[Frédéric Martinsons]

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

Thanks, after having "fixed" /tmp, I managed to play
test_devtool_modify_git successfully.

Le mar. 28 mars 2023, 22:04, Alexander Kanavin <alex.kanavin@gmail.com> a
écrit :

> Not devtool's fault. The selftest is written so that devtool is
> instructed to use /tmp/... to extract sources, and not a workspace in
> a build: 'devtool modify -x /tmp/...'.
>
> Having /tmp with noexec is not common, that's why it isn't mentioned.
> If the admin is not cooperative, you can hack the selftest definition
> to use some other place.
>
> Alex
>
> On Tue, 28 Mar 2023 at 21:02, Frédéric Martinsons
> <frederic.martinsons@gmail.com> wrote:
> >
> > Oh my, your assumption is surely correct, my build host /tmp is mounted
> with noexec so no chance to execute
> > anything there:
> >
> > [ (8) ] jenkins@cibuilder2:~$ mount | grep "/tmp"
> > tmpfs on /tmp type tmpfs (rw,nosuid,nodev,noexec,noatime,inode64)
> >
> > Tomorrow, I'll try with another machine (or talk to the admin of the
> build hosts) with a /tmp capable of executing things.
> >
> > But the requirement to have /tmp directory capable of executing scripts
> was not mentioned in the oe-selftest
> > page (https://wiki.yoctoproject.org/wiki/Oe-selftest) or the quick
> start one (https://docs.yoctoproject.org/brief-yoctoprojectqs/index.html)
> >
> > I would have thought that devtool, if it needs to execute some scripts,
> will execute them in its working directory and not
> > in /tmp of build hosts.... Is this something really expected ?
> >
> >
> > On Tue, 28 Mar 2023 at 20:28, Alexander Kanavin <alex.kanavin@gmail.com>
> wrote:
> >>
> >> Btw, I'm beginning to suspect something isn't right about /tmp on your
> >> build host. The test requires being able to write executable scripts
> >> into that, and then run them. I just ran the
> >> devtool.DevtoolModifyTests.test_devtool_modify_git here, and it
> >> succeeded.
> >>
> >> Alex
> >>
> >> On Tue, 28 Mar 2023 at 20:14, Alexander Kanavin via
> >> lists.openembedded.org <alex.kanavin=gmail.com@lists.openembedded.org>
> >> wrote:
> >> >
> >> > Would you be able to read the failing test, and replicate the steps it
> >> > does by hand? If we can narrow down the precise point where it fails,
> >> > that would already help.
> >> >
> >> > Alex
> >> >
> >> > On Tue, 28 Mar 2023 at 20:01, Frédéric Martinsons
> >> > <frederic.martinsons@gmail.com> wrote:
> >> > >
> >> > > I rebuilt a poky master from scratch on another machine (Ubuntu
> 22.04 , 16 Xeon, 124 Gb RAM), it took
> >> > >  2h30mn to finish (note that rust-llvm-native and llvm-native both
> took around 1h each to be built).
> >> > >
> >> > > I have two questions for my curiosity:
> >> > >    - why rust things (cargo-native, librsvg)  are the last
> artifacts built on core-image-sato ? it seems strange at first look
> >> > > (but may be explained by packages embedded by this image, I didn't
> look on what are the dependencies of this image)
> >> > >    - my pristine BDIR took around 90 GB , maybe the page
> https://docs.yoctoproject.org/dev/brief-yoctoprojectqs/index.html stating
> >> > > that we need 50 GB of free space needs to be reviewed (unless it
> was written with another image than core-image-sato in mind) ?
> >> > >
> >> > > Apart from that,  I have the exact same error on
> test_devtool_modify_git that I had on the other machine under /var build
> dir:
> >> > >
> >> > > NOTE: Running setscene task 210 of 213
> (virtual:native:/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-devtools/gnu-config/gnu-config_git.bb:
> do_populate_sysroot_setscene)
> >> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0:
> task do_populate_sysroot_setscene: Started
> >> > > NOTE: recipe gnu-config-native-20230216+gitAUTOINC+63acb96f92-r0:
> task do_populate_sysroot_setscene: Succeeded
> >> > > NOTE: Running task 896 of 918
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
> do_prepare_recipe_sysroot)
> >> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot:
> Started
> >> > > NOTE: recipe psplash-0.1+git999-r0: task do_prepare_recipe_sysroot:
> Succeeded
> >> > > NOTE: Running task 910 of 918
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:
> do_configure)
> >> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Started
> >> > > ERROR: psplash-0.1+git999-r0 do_configure: no configure script
> found at ../../../../../../../../../../../tmp/devtoolqamf2smwsy/configure
> >> > > ERROR: psplash-0.1+git999-r0 do_configure:
> ExecutionError('/home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/run.do_configure.1967375',
> 1, None, None)
> >> > > ERROR: Logfile of failure stored in:
> /home/jenkins/yocto-poky-master/poky/build-st/tmp/work/core2-64-poky-linux/psplash/0.1+git999-r0/temp/log.do_configure.1967375
> >> > > NOTE: recipe psplash-0.1+git999-r0: task do_configure: Failed
> >> > > ERROR: Task
> (/tmp/devtoolqacvbsfqx2/core-copy/meta/recipes-core/psplash/psplash_git.bb:do_configure)
> failed with exit code '1'
> >> > > NOTE: Tasks Summary: Attempted 910 tasks of which 904 didn't need
> to be rerun and 1 failed.
> >> > >
> >> > > Full test log joined (I would like to join also the log of
> do_configure step but it seems that the test do a cleanall of the recipe
> during its tear down method)
> >> > >
> >> > > I'm kind of stuck here since I cannot develop more oe-selftest
> tests if I didn't even manage to make the existing ones succeed.
> >> > > Can someone give me the setup of this autobuilder where Alexander
> talked about ?
> >> > >
> >> > > I could try to get as close as possible to the autobuilder setup if
> the oe-selftest is ok there.
> >> > >
> >> > > On Tue, 28 Mar 2023 at 17:36, Frédéric Martinsons <
> frederic.martinsons@gmail.com> wrote:
> >> > >>
> >> > >> Note that I managed to build libtirpc-native and shadow-native
> with bitbake (and the same setup).
> >> > >>
> >> > >> I currently try the build on another machine and under /home.
> >> > >>
> >> > >> I'll tell you the results soon
> >> > >>
> >> > >> Le mar. 28 mars 2023, 15:13, Richard Purdie <
> richard.purdie@linuxfoundation.org> a écrit :
> >> > >>>
> >> > >>> On Tue, 2023-03-28 at 14:40 +0200, Frédéric Martinsons wrote:
> >> > >>> > I just finished a pristine build of core-image-sato on poky
> master,
> >> > >>> > and set up SSTATE_DIR in my local.conf.
> >> > >>> > Tests are now ok, I can start to write some now.
> >> > >>> >
> >> > >>> > If anyone is interested , please find attached the full log of
> the
> >> > >>> > two first failures.
> >> > >>>
> >> > >>> Having the errors helps, thanks.
> >> > >>>
> >> > >>> The short summary is these two lines:
> >> > >>>
> >> > >>> libtirpc-native
> >> > >>> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/libtirpc-native/1.3.3-r0/recipe-sysroot-native/etc/netconfig':
> Invalid argument
> >> > >>>
> >> > >>> shadow-native
> >> > >>> | chown: changing ownership of
> '/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/image/var/lib/jenkins/YOCTO_POKY_MASTER_TEST/poky/build-st/tmp/work/x86_64-linux/shadow-native/4.13-r0/recipe-sysroot-native/var/spool/mail':
> Invalid argument
> >> > >>>
> >> > >>>
> >> > >>> I'm wondering if the fact the build is under /var might be
> triggering
> >> > >>> something somehow...
> >> > >>>
> >> > >>> Cheers,
> >> > >>>
> >> > >>> Richard
> >> >
> >> > -=-=-=-=-=-=-=-=-=-=-=-
> >> > Links: You receive all messages sent to this group.
> >> > View/Reply Online (#179243):
> https://lists.openembedded.org/g/openembedded-core/message/179243
> >> > Mute This Topic: https://lists.openembedded.org/mt/97900549/1686489
> >> > Group Owner: openembedded-core+owner@lists.openembedded.org
> >> > Unsubscribe: https://lists.openembedded.org/g/openembedded-core/unsub
> [alex.kanavin@gmail.com]
> >> > -=-=-=-=-=-=-=-=-=-=-=-
> >> >
>

[-- Attachment #2: Type: text/html, Size: 11574 bytes --]