From: Leonardo Sandoval
Run in parallel the (oe)selftests using GNU/Parallel: for each test
defined, a job will be launched and at any time at maximum of jobs
will be executing (defaults to 4).
1. Run all modules
parallel-oe-selftest.sh
2. Run certain modules and print results in order (se
From: Leonardo Sandoval
Parallelize oe-selftest execution using GNU/Parallel: for each test
defined, a job will be launched and at any time at maximun of jobs will
be executing (defaults to 4).
1. Run all modules
parallel-oe-selftest.sh
2. Run certaing modules and print results in order (s
From: Leonardo Sandoval
The main idea is to isolate the oe-selftest execution so neither the current
build directory, configuration nor environment is use when executing the
selftests.
The approach uses 'oe-selftest' as a wrapper scripts with once all isolation
setup is done, it calls 'scripts/l
From: Leonardo Sandoval
Some test cases (eSDK.oeSDK*, runtime_test/*) does not match
with current regex, fix it accept all.
[YOCTO #12385]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/core/loader.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/core/l
From: Leonardo Sandoval
Some test cases (i.e. eSDK.oeSDKExtSelfTest*) does not match with current regex,
fix it to accept these (and previous ones).
Without it, the following runtime exception is observed when executing eSDK
selftest (oe-selftest -r eSDK)
Traceback (most recent call last):
From: Leonardo Sandoval
These variables provide additional information (image related) targeted
for QA image verification. Now, target /etc/build looks like:
root@qemux86:~# cat /etc/build
---
Build Configuration: |
---
DISTRO = poky
From: Leonardo Sandoval
The main idea is to isolate the oe-selftest execution so neither the current
build dir nor the configuration data is touch/polluted. This approach uses
a wrapper script (which is the one presented on this commit) which creates
a unique directory and inside it copies all sc
From: Leonardo Sandoval
Parallelize oe-selftest execution using GNU/Parallel: for each test
defined, a job will be launched and at any time at maximun of jobs will
be executing (defaults to 4). Extra parameters can be given to
parallel cmd after double dashes ('--'). Some cmd line examples:
1. R
From: Leonardo Sandoval
All CVE patches and the glibc one removed because these are already integrated
into 2.10.1.
Signed-off-by: Leonardo Sandoval
---
v2: removed the glibc-2.25.patch, already into 2.10.1. At v1, I hit [YOCTO
#10450]
where devtool upgrade complain in just one hunk, even
From: Leonardo Sandoval
The below is a profiling experiment, running oe-selftest -r (the proposed
implementation, see patch description for more info):
Procedure:
With patch 1/1, multiple oe-selftest jobs can be launched in
parallel. One tool that launch jobs in parallel is GNU Parallel [1], al
From: Leonardo Sandoval
The main idea is to isolate the oe-selftest execution so neither the current
build dir nor the configuration data is touch/polluted. This approach uses
a wrapper script (which is the one presented on this commit) which creates
a unique directory and inside it does a shallo
From: Leonardo Sandoval
Besides revision change, this version includes the project M4 macros path into
EXTRA_AUTORECONF which avoid the following compilation issue:
In file included from ../../../texinfo-6.5/gnulib/lib/mbrtowc.c:21:0:
./wchar.h:571:6: error: #if with no expression
#
From: Leonardo Sandoval
All CVE patches removed because these are already integrated in 2.10.1.
Signed-off-by: Leonardo Sandoval
---
.../qemu/qemu/CVE-2017-13672.patch | 504 -
.../qemu/qemu/CVE-2017-13673.patch | 53 ---
.../qemu/qemu/CVE-2
From: Leonardo Sandoval
The CVE-2017-14064 patch is already at 2.4.2 as explained on
project's commit, so removing from the recipe & repo.
commit 83735ba29a0bfdaffa8e9c2a1dc025c3b0b63153
Author: hsbt
Date: Wed Apr 12 00:21:18 2017 +
Merge json-2.0.4.
* http
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
.../perl/libxml-namespacesupport-perl_1.12.9.bb| 35 ++
.../perl/libxml-namespacesupport-perl_1.12.bb | 23 --
2 files changed, 35 insertions(+), 23 deletions(-)
create mode 100644
meta/recip
From: Leonardo Sandoval
The git-perltools package created with perl 5.26.1 does not contain
the .packlist file thus there is no need to sed on this file.
More general, the buildhistory-diff tool shows the following changes on
the related package, clearly indicating that .packlist is not there a
From: Leonardo Sandoval
Patch Name # Status at 5.26.1
file://Configure-multilib.patch# Already merged in 5.26.1, so removed it
file://perl-configpm-switch.patch # Applies as it is
file://native-nopacklist.patch # Rebased it to 5.26.1
file://native-perlinc.patch#
From: Leonardo Sandoval
Highlights:
* Patches rebased to 5.26.1 and just one removed
* Several configs values taken from upstream script uconfig[64].sh were
introduced in
config.sh, avoiding pre-processor issues.
* Several libraries paths now included a './' as prefix, because
From: Leonardo Sandoval
The CVE-2017-14064 patch is already at 2.4.2 as explained on
project's commit, so removing from the recipe & repo.
commit 83735ba29a0bfdaffa8e9c2a1dc025c3b0b63153
Author: hsbt
Date: Wed Apr 12 00:21:18 2017 +
Merge json-2.0.4.
* http
From: Leonardo Sandoval
The git-perltools package created with perl 5.26.1 does not contain
the .packlist file thus there is no need to sed on this file.
More general, the buildhistory-diff tool shows the following changes on
the related package, clearly indicating that .packlist is not there a
From: Leonardo Sandoval
Patch Name # Status at 5.26.1
file://Configure-multilib.patch# Already merged in 5.26.1, so removed it
file://perl-configpm-switch.patch # Applies as it is
file://native-nopacklist.patch # Rebased it to 5.26.1
file://native-perlinc.patch#
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
.../perl/libxml-namespacesupport-perl_1.12.9.bb| 35 ++
.../perl/libxml-namespacesupport-perl_1.12.bb | 23 --
2 files changed, 35 insertions(+), 23 deletions(-)
create mode 100644
meta/recip
From: Leonardo Sandoval
Highlights:
* Patches rebased to 5.26.1 and just one removed
* Several configs values taken from upstream script uconfig[64].sh were
introduced in
config.sh, avoiding pre-processor issues.
* Several libraries paths now included a './' as prefix, because
From: Leonardo Sandoval
The CVE-2017-14064 patch is already at 2.4.2 as explained on
project's commit, so removing from the recipe & repo.
commit 83735ba29a0bfdaffa8e9c2a1dc025c3b0b63153
Author: hsbt
Date: Wed Apr 12 00:21:18 2017 +
Merge json-2.0.4.
* http
From: Leonardo Sandoval
Highlights:
* Patches rebased to 5.26.1 and just one removed
* Several configs values taken from upstream script uconfig[64].sh were
introduced in
config.sh, avoiding pre-processor issues.
* Several libraries paths now included a './' as prefix, because
From: Leonardo Sandoval
Patch Name # Status at 5.26.1
file://Configure-multilib.patch# Already merged in 5.26.1, so removed it
file://perl-configpm-switch.patch # Applies as it is
file://native-nopacklist.patch # Rebased it to 5.26.1
file://native-perlinc.patch#
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
...2.bb => libxml-namespacesupport-perl_1.12.9.bb} | 24 --
1 file changed, 18 insertions(+), 6 deletions(-)
rename meta/recipes-extended/perl/{libxml-namespacesupport-perl_1.12.bb =>
libxml-namespacesupport-perl
From: Leonardo Sandoval
The high-level method tempfile.TemporaryDirectory give us no way to
ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible
issues
on removal is neccesary because it contains gpg sockets that are automatically
removed
by the system once the process t
From: Leonardo Sandoval
Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing
occurs in parallel
so (unfortunately) the signing must be done serially. Once the upstream problem
is fixed,
this patch must be reverted, otherwise we loose all the intrinsic parallelism
from
bitb
From: Leonardo Sandoval
Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing
occurs in parallel
so (unfortunately) the signing must be done serially. Once the upstream problem
is fixed,
this patch must be reverted, otherwise we loose all the intrinsic parallelism
from
bitb
From: Leonardo Sandoval
The high-level method tempfile.TemporaryDirectory give us no way to
ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible
issues
on removal is neccesary because it contains gpg sockets that are automatically
removed
by the system once the process t
From: Leonardo Sandoval
The high-level method tempfile.TemporaryDirectory give us no way to ignore
erros on
removal thus use tempfile.mkdtemp instead. Ignoring possible issues on removal
is neccesary because it contains gpg sockets that are automatically removed by
the system once the process te
From: Leonardo Sandoval
Newer versions of gpg (at least 2.1.5 and 2.2.1) have issues when signing
occurs in parallel
so (unfortunately) the signing must be done serially. Once the upstream problem
is fixed,
this patch must be reverted, otherwise we loose all the intrinsic parallelism
from
bitb
From: Leonardo Sandoval
There are cases where the 'while loop' waiting for login prompt fails
and the bootlog variable does not get populated, thus use the the new
qemurunner member (self.msg) which stores all output coming from the qemu
process.
[YOCTO #12113]
Signed-off-by: Leonardo Sandoval
From: Leonardo Sandoval
The high-level method tempfile.TemporaryDirectory give us no way to
ignore erros on removal thus use tempfile.mkdtemp instead. Ignoring possible
issues
on removal is neccesary because it contains gpg sockets that are automatically
removed
by the system once the process t
From: Leonardo Sandoval
Redirecting stderr to stdout helps debugging issues, i.e instead of just
getting the return code, get also the error log from the pkg manger
This commit is in the way to figure out the root cause of [YOCTO #12012],
where dpkg-deb fails with a 2 return code and according to
From: Leonardo Sandoval
Current implementation does not handle possible exceptions coming from child
processes, the latter responsible for creating packages. With the aim to have
more
control, use pipes to communicate exceptions and stop package creation in case
of failure.
Helps to debug [YOCT
From: Leonardo Sandoval
Waffle's REQUIRED_DISTRO_FEATURES statement looks into DEPENDS and if
virtual/libgl is present, it includes opengl as distro feature. However,
in a multilib environment, recipes provides virtual/${MLPREFIX}libgl,
thus waffle recipe needs to include the prefix. Also PACKAGE
From: Leonardo Sandoval
This allows the yocto-bsp script to pick the 4.12 kernel version when
creating a custom BSP.
[YOCTO #11995]
Signed-off-by: Leonardo Sandoval
---
.../arm/recipes-kernel/linux/kernel-list.noinstall | 4 +-
.../linux/linux-yocto-tiny_4.12.bbappend | 37
From: Leonardo Sandoval
Otherwise, on a multilib environment we get the following bitbake errors
while building 'world'
ERROR: Nothing PROVIDES 'virtual/lib32-libgl' (but
virtual:multilib:lib32:/meta/recipes-graphics/waffle/waffle_1.5.2.bb DEPENDS on
or otherwise requires it). Close matche
From: Juan M Cruz Alcaraz
The eSDK installation requires the meta-skeleton layer.
The build system might use the meta-skeleton recipes as layout
to create custom recipes. An example is the recipetool script
that uses the meta-skeleton kernel recipe when creating a custom
kernel recipe.
[YOCTO #1
From: Leonardo Sandoval
Otherwise, we get timeouts, leading to errors:
pip._vendor.requests.exceptions.ConnectTimeout:
HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded
with url: /pypi/pip/json (Caused by
ConnectTimeoutError(, 'Connection to pypi.python.org timed
From: Leonardo Sandoval
Besides providing the NATIVELSBSTRING, include distro info when creating
the (json) error report. This information provides better info than the
standard 'universal*' string for uninative builds.
[YOCTO #11824]
Signed-off-by: Leonardo Sandoval
---
meta/classes/report-e
From: Leonardo Sandoval
Commit d58b1d196 moved from chunk to serial signing, but neither of both
approaches
allowed the user to select the chunks size. This patch allows the user to select
a chunk size through RPM_GPG_SIGN_CHUNK defaulting to BB_NUMBER_THREADS,
considered
a good default. Indire
From: Leonardo Sandoval
gpg signing in file batches (which was default to 100) is a memory expensive
computation, causing trouble in some host machines (even on production AB
as seen on the bugzilla ID). Also, in terms of performance, there is no real
gain when rpm signing is done in batches. Con
From: Leonardo Sandoval
Otherwise, we get timeouts, leading to errors:
pip._vendor.requests.exceptions.ConnectTimeout:
HTTPSConnectionPool(host='pypi.python.org', port=443): Max retries exceeded
with url: /pypi/pip/json (Caused by
ConnectTimeoutError(, 'Connection to pypi.python.org timed
From: Leonardo Sandoval
Otherwise, the following bitbake error is observed
root@qemux86-64:~/openembedded-core/build# bitbake -e
NOTE: Starting bitbake server...
ERROR: Unable to start bitbake server
ERROR: Last 10 lines of server log
/home/root/openembedded-core/build/bitbake-c
From: Leonardo Sandoval
For perfomance reasons, limit the number of signature comparisons when
stamps differ. The limit set is hardcoded to 20.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 39 ++---
1 file changed, 2
From: Leonardo Sandoval
Using a python function instead of launching a subprocess fasten the
diffsigs computation.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/met
From: Leonardo Sandoval
For perfomance reasons, limit the number of signature comparisons when
stamps differ. The limit set is hardcoded to 20.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 40 +++--
1 file changed, 2
From: Leonardo Sandoval
Using a python function instead of launching a subprocess fasten the
diffsigs computation.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/met
From: Leonardo Sandoval
For perfomance reasons, limit the number of signature comparisons when
stamps differ. The limit set is hardcoded to 20.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 41 +++--
1 file changed, 2
From: Leonardo Sandoval
This commit generalizes the work done in [1] and [2], both fixing
issues on several areas (the former with -c patch and gnome-terminal and
the latter with -c menuconfig and several terminals, including
gnome-terminal and tmux). The main idea is to get the PID
from the new
From: Leonardo Sandoval
This reverts commit d2ebee7c3a0c8ab9a09ebad12a2fda51f8d10954.
---
meta/classes/cml1.bbclass | 22 +-
1 file changed, 1 insertion(+), 21 deletions(-)
diff --git a/meta/classes/cml1.bbclass b/meta/classes/cml1.bbclass
index 0bab22efed..eb8e7907f6 100644
From: Leonardo Sandoval
For perfomance reasons, limit the number of signature comparisons when
stamps differ. The limit set is hardcoded to 20.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 6 ++
1 file changed, 6 insertions(+)
diff --g
From: Leonardo Sandoval
Using a python function instead of launching a subprocess fasten the
diffsigs computation.
[YOCTO #11651]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/cases/sstatetests.py | 10 +++---
1 file changed, 7 insertions(+), 3 deletions(-)
diff --git a/met
From: Leonardo Sandoval
A new command line argument (-R, which is the oposite of current -r) that allows
to run all test cases except the ones indicated through the command line.
Some command line examples:
* Run all except the distro test case:
$ oe-selftest -R distrodata
* Run all except the
From: Leonardo Sandoval
There are at least two terminals types (gnome and tmux) that when
launched to show the kernel's menuconfig, we lost track of the corresponding
process ID, thus there is no way to see when they finish, yielding identical
timestamps before and after menuconfig thus compile's
From: Leonardo Sandoval
Though the script bitbake-layers (from the bitbake project), this plugin
creates a simple layer with a example recipe, the latter with a single task
(do_build). Layer's license and priority is MIT and 6, respectively. Example
recipe and layer's priority can be specified th
From: Leonardo Sandoval
The following changes since commit a4f2bf37b7eac888f37f11cd4d4606436909c507:
mpc8315e-rdb: add wic.bmap to IMAGE_FSTYPES (2017-07-17 15:14:27 +0100)
are available in the git repository at:
git://git.yoctoproject.org/poky-contrib lsandov1/python3-config-multilib
h
From: Leonardo Sandoval
The python config script is installed /usr/bin thus conflicting when
installing python and its multilib version. To avoid the latter, move
the script into the dev package.
[YOCTO #11513]
Signed-off-by: Leonardo Sandoval
---
meta/recipes-devtools/python/python-3.5-manif
From: Leonardo Sandoval
Kernel recipes provides 'virtual/kernel' so remove the native part.
Signed-off-by: Leonardo Sandoval
---
meta/classes/image_types.bbclass | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/classes/image_types.bbclass b/meta/classes/image_types.bbcl
From: Leonardo Sandoval
According to the bitbake documentation, the "d" global datastore should be
used instead of "e.data" because the latter is deprecated.
Signed-off-by: Leonardo Sandoval
---
meta/classes/base.bbclass | 36 ++--
1 file changed, 18 insertions(
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
meta/recipes-core/ovmf/ovmf_git.bb | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git a/meta/recipes-core/ovmf/ovmf_git.bb
b/meta/recipes-core/ovmf/ovmf_git.bb
index 28f0cde1d9..d3f84246da 100644
--- a/meta/recip
From: Leonardo Sandoval
In case the proposed md5 tag to be appended is already present,
do not append it.
Signed-off-by: Leonardo Sandoval
---
scripts/lib/devtool/standard.py | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/scripts/lib/devtool/standard.py b/scripts/li
From: Leonardo Sandoval
Takes a tar archive created by 'devtool export' and export it (untar) to
workspace. By default, the whole tar archive is imported, thus there is no
way to limit what is imported.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10510
[YOCTO #10510]
Signed-off-by: Leona
From: Leonardo Sandoval
By default, exports the whole workspace (all recipes) including the source code.
User can also limit what is exported with --included/--excluded flags. As
a result of this operation, a tar archive containing only workspace metadata
and its corresponding source code is crea
From: Leonardo Sandoval
These two plugins can be used to share the devtool workspace between users.
The following changes since commit c3058ec4a4f2f4c57116816a5bede1e61a5a4cc4:
meta/conf/layer.conf: bump layer version for LSB changes (2017-06-28 15:52:19
+0100)
are available in the git repo
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
scripts/lib/devtool/__init__.py | 37 +
1 file changed, 37 insertions(+)
diff --git a/scripts/lib/devtool/__init__.py b/scripts/lib/devtool/__init__.py
index 29c4c05071..7f4f817a8e 100644
--- a/scr
From: Leonardo Sandoval
These two plugins can be used to share the devtool workspace between users.
The following changes since commit ef506f58da3a95fba2696df749b2b81f9c118847:
cve-check-tool: backport a patch to make CVE checking work (2017-05-18
14:01:48 +0100)
are available in the git re
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
scripts/lib/devtool/__init__.py | 37 +
1 file changed, 37 insertions(+)
diff --git a/scripts/lib/devtool/__init__.py b/scripts/lib/devtool/__init__.py
index d646b0cf63..95307e63fa 100644
--- a/scr
From: Leonardo Sandoval
Takes a tar archive created by 'devtool export' and export it (untar) to
workspace. By default, the whole tar archive is imported, thus there is no
way to limit what is imported.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10510
[YOCTO #10510]
Signed-off-by: Leona
From: Leonardo Sandoval
By default, exports the whole workspace (all recipes) including the source code.
User can also limit what is exported with --included/--excluded flags. As
a result of this operation, a tar archive containing only workspace metadata
and its corresponding source code is crea
From: Leonardo Sandoval
Error data is now placed on the result.error variable, thus
change relevant test cases to query the latter (instead of
stdout). Also a bit of refactor with a new file created on
with single function used by the selftest modules.
[YOCTO #9693]
Signed-off-by: Leonardo Sand
From: Leonardo Sandoval
Do not mix the stderr into stdout, allowing test cases to query
the specific output.
[YOCTO #9693]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/utils/commands.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/utils/commands.py b
From: Leonardo Sandoval
The class nopackages deletes tasks needed by the archiver, so in case
the latter is globally inherited, do not inherit nopackages. Without
this patch, the following error occurs:
ERROR: Task do_deploy_archives in
.../meta/recipes-kernel/kmod/depmodwrapper-cross_1.0.b
From: Leonardo Sandoval
Users constantly running oe-selftest find annoying to disable buildhistory
before running
'oe-selftest' then enabling after it. To lessen the buildhistory restriction,
allow buildhistory
unless 'version-going-backwards' is present on ERROR_QA bitbake variable.
[YOCTO #1
From: Leonardo Sandoval
Catching a possible exception when importing the git module,
allows us to skip test if the latter is missing on the host.
Also, import oe.buildhistory_analysis inside fuctions
because this module also needs git to work correctly.
[YOCTO #11620]
Signed-off-by: Leonardo Sa
From: Leonardo Sandoval
These two plugins can be used to share the devtool workspace between users.
Changes from v1 (mostly suggested by Paul E.)
Export:
* metatada file created and included on tar, containing workspace data (to
be consume by
the import plugin)
* tar archive contai
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/utils/ftools.py | 22 ++
1 file changed, 22 insertions(+)
diff --git a/meta/lib/oeqa/utils/ftools.py b/meta/lib/oeqa/utils/ftools.py
index a7233d4ca6..8bf2547d68 100644
--- a/meta/lib/oeqa/utils/ftoo
From: Leonardo Sandoval
Takes a tar archive created by 'devtool export' and export it (untar) to
workspace. By default, the whole tar archive is imported, thus there is no
way to limit what is imported.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10510
[YOCTO #10510]
Signed-off-by: Leona
From: Leonardo Sandoval
By default, exports the whole workspace (all recipes) including the source code.
User can also limit what is exported with --included/--excluded flags. As
a result of this operation, a tar archive containing only workspace metadata
and its corresponding source code is crea
From: Leonardo Sandoval
Empty descriptions lines are set with a space following by a dot and
the multiline ones require a leading space. Also, for non-empty lines,
there is no need for formating with textwrap, so remove the logic for
the latter. The documentation for multiline description was tak
From: Leonardo Sandoval
Takes a tar archive created by 'devtool export' and export it (untar) to
workspace. By default, the whole tar archive is imported, thus there is no
way to limit what is imported.
https://bugzilla.yoctoproject.org/show_bug.cgi?id=10510
[YOCTO #10510]
Signed-off-by: Leona
From: Leonardo Sandoval
These two plugins can be used to share the devtool workspace between uses.
On the import plugin, the are some limitations with the proposed patche:
* It cannot not limit what is being imported, thus all exported
workspace is imported for the moment.
* It is not s
From: Leonardo Sandoval
By default, exports the whole workspace (all recipes) including the source code.
User can also limit what is exported with --included/--excluded flags. As
a result of this operation, a tar archive containing only workspace metadata
and its corresponding source code is crea
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
.../nfs-utils/{nfs-utils_1.3.4.bb => nfs-utils_2.1.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-connectivity/nfs-utils/{nfs-utils_1.3.4.bb =>
nfs-utils_2.1.1.bb} (97%)
diff --git
From: Leonardo Sandoval
Signed-off-by: Leonardo Sandoval
---
meta/recipes-devtools/ruby/{ruby_2.4.0.bb => ruby_2.4.1.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-devtools/ruby/{ruby_2.4.0.bb => ruby_2.4.1.bb} (89%)
diff --git a/meta/recipes-devtools/ruby/r
From: Leonardo Sandoval
Empty descriptions are set with a space following by a dot. For the non-empty
ones,
there is no need for formating the description with textwrap, so remove the
logic
for the latter.
[YOCTO #10677]
Signed-off-by: Leonardo Sandoval
---
meta/classes/package_ipk.bbclass
From: Leonardo Sandoval
As described in [1], "Empty lines in field values are usually escaped by
representing
them by a space followed by a dot." so default to the latter.
[1] https://www.debian.org/doc/debian-policy/ch-controlfields.html
Signed-off-by: Leonardo Sandoval
---
meta/classes/pac
From: Leonardo Sandoval
As explained in [1], the module function imp.reload has been deprecated for
importlib.reload, so use the latter instead.
[1] https://docs.python.org/3/library/imp.html#imp.reload
Signed-off-by: Leonardo Sandoval
---
scripts/oe-selftest | 4 ++--
1 file changed, 2 inser
From: Leonardo Sandoval
Split the configuration values (common and specific) so it is easier to read
what goes into the config file. Also the specific configurations are
set in every loop so these do not append on each iteration.
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/runt
From: Leonardo Sandoval
It was found a case (see the bugzilla entry) where two runners were running at
the same
second, creating identical test result folders, so one of them (the second
runner)
was not able to create the folder because the other has already created it,
raising the following ex
From: Leonardo Sandoval
The unit test requires x11 as distro feature, otherwise it will fail
while building the test requirements.
[YOCTO #10903]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/recipetool.py | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/lib/oeqa/selft
From: Leonardo Sandoval
WIC test case requires wic-tools which in turn depends on intltool-native and
gettext-native. However, if NLS is disable, the gettext-minimal-native is used
instead
of gettext-native causing a failure on intltool-native as seen below:
checking for msgfmt... no
checki
From: Leonardo Sandoval
To generalize the unit test for other kernel providers, use virtual/kernel
instead
of linux-yocto, allowing to run the selftest on non-poky distros, i.e.
poky-tiny.
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/devtool.py | 23 ---
1
From: Leonardo Sandoval
This change allows quering for variables with the format A_B, i.e.
PREFERRED_PROVIDER_virtual/kernel instead of just A.
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/utils/commands.py | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/meta/lib/oeqa
From: Leonardo Sandoval
The recipe being tested (devtoo-test-patch-gz) by devtool has dependencies (at
least libxres and virtual/libx11) that cannot be built with poky-tiny distro so
skip the test for this particular policy.
[YOCTO #10891]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/se
From: Leonardo Sandoval
Replace the glibc recipe for zlib on unit tests, otherwise tests are restricted
to glibc distros (poky).
[YOCTO #10890]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/pkgdata.py | 28 +---
1 file changed, 13 insertions(+), 15 deleti
From: Leonardo Sandoval
Replace the glibc recipe for zlib on unit tests, otherwise tests are restricted
to glibc distros (poky).
[YOCTO #10890]
Signed-off-by: Leonardo Sandoval
---
meta/lib/oeqa/selftest/pkgdata.py | 28 +---
1 file changed, 13 insertions(+), 15 deleti
1 - 100 of 248 matches
Mail list logo
