Drop 0001-Cus428Midi-Explicitly-cast-constant-to-char-type.patch,
because the new release has an equivalent fix (and that's actually the
only change in the new release).
Signed-off-by: Tanu Kaskinen
---
...idi-Explicitly-cast-constant-to-char-type.patch | 75 --
.../{alsa-too
Changelog: https://xiph.org/flac/changelog.html
The license checksum changes are due to simple copyright year updates.
Signed-off-by: Tanu Kaskinen
---
.../recipes-multimedia/flac/{flac_1.3.1.bb => flac_1.3.2.bb} | 12 ++--
1 file changed, 6 insertions(+), 6 deletions(-)
rename meta/re
On Fri, 20 Jan 2017, Mike Looijmans wrote:
> On 19-01-17 21:58, Robert P. J. Day wrote:
> >
> > following up on the whining i did a while back to finish off a few
> > perl recipes for OE, i have just a few left to resolve, and this is
> > one of them. i managed to get several dozen perl recipes
On Thu, 2017-01-19 at 16:46 -0600, Aníbal Limón wrote:
> SRC_URI_prepend = "http://wiki.qemu-project.org/download/${BP}.tar.bz2";
> -SRC_URI[md5sum] = "08d4d06d1cb598efecd796137f4844ab"
> -SRC_URI[sha256sum] =
> "326e739506ba690daf69fc17bd3913a6c313d9928d743bd8eddb82f403f81e53"
> +SRC_URI[md5sum]
On 01/20/2017 01:35 PM, Patrick Ohly wrote:
On Thu, 2017-01-19 at 16:46 -0600, Aníbal Limón wrote:
SRC_URI_prepend = "http://wiki.qemu-project.org/download/${BP}.tar.bz2";
-SRC_URI[md5sum] = "08d4d06d1cb598efecd796137f4844ab"
-SRC_URI[sha256sum] =
"326e739506ba690daf69fc17bd3913a6c313d9928d743
On Thu, 19 Jan 2017, Burton, Ross wrote:
>
> On 19 January 2017 at 20:58, Robert P. J. Day wrote:
> beyond this, i'm not sure how to use an OE patch to adjust this
> source the right way, given that dozens and dozens of other modules
> cross-compiled just fine.
>
> tho
The test fetches bitbake variables and then changes the configuration, so
it fails if the user's MACHINE isn't qemux86. I've changed this locally
and now its failing differently:
First extra element 18:
./etc/systemd/system/sysinit.target.wants/opkg-configure.service
Looks like you want to lock
the earlier note from ross i had totally forgotten about ...
On Tue, 20 Dec 2016, Burton, Ross wrote:
> FWIW I had a quick look at this. I'm certainly no perl guru and can
> barely understand it, but it does *so much* wrong that if you really
> need this then it would be easier to just rewrit
Hi
Can we backport the following commit to morty?
http://cgit.openembedded.org/openembedded-core/commit/?id=cb4f5ecf32006192baaf41218a3d7b43ca1c2951
It fixes pkgconfig to no longer report an old version.
Currently this breaks firefox in meta-browser morty branch.
Thanks
Max
--
gettext and glib-2.0 tools are required during build.
Signed-off-by: Jussi Kukkonen
---
This should fix the build issues epiphany is having with the RSS
patchset.
meta/recipes-gnome/epiphany/epiphany_3.22.3.bb | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/recipe
Signed-off-by: Andreas Müller
---
.../alsa-lib/0001-ucm-parser-needs-limits.h.patch | 33 ++
.../alsa/{alsa-lib_1.1.2.bb => alsa-lib_1.1.3.bb} | 5 ++--
2 files changed, 36 insertions(+), 2 deletions(-)
create mode 100644
meta/recipes-multimedia/alsa/alsa-lib/0001-ucm-par
Hi Jason,
On Thu, Jan 19, 2017 at 03:24:00PM -0600, Jason Wessel wrote:
>
> The issue here is that in a multilib build the ${base_libdir} is resolving to
> /lib64 which completely breaks some tools that fully expect /lib/modules to
> be a fixed location regardless if the target is 32/64 or some
On 20 January 2017 at 13:29, Maxin B. John wrote:
> > The issue here is that in a multilib build the ${base_libdir} is
> resolving to /lib64 which completely breaks some tools that fully expect
> /lib/modules to be a fixed location regardless if the target is 32/64 or
> something else.
> >
>
> I
On Sun, Jan 15, 2017 at 7:41 PM, Juro Bystricky
wrote:
> Presently there is no check to verify the existence of configuration
> files as listed in BBMULTICONFIG.
> For example, BBMULTICONFIG = "foobar" in local.conf does not trigger
> an error or even a warning when there is no conf/multiconfig/fo
On Thu, 2017-01-19 at 18:23 +0100, Patrick Ohly wrote:
> Perhaps someone with more knowledge about flex can provide some
> guidance?
>
> Fathi, is that something that you or upstream have come across?
After looking into this some more I've come to the conclusion that this
looks like a bug in flex
From: Fathi Boudra
qemu support for UEFI in OE-core depends on OVMF, which needs the iasl
tools provided by this recipe. There's also an iasl recipe in
meta-luv, but than can and will be replaced by this one, thus reducing
overall maintenance work.
Copied from meta-openembedded rev fa65be9ba (cu
There seems to be a consensus that supporting UEFI in OE-core for qemu
would be valuable, and there have been some (stalled) attempts to add
it. For reference, see:
[OE-core] [PATCH V3 0/3] Add UEFI firmware for qemux86*
[OE-core] Add ovmf-native to make qemu-native/runqemu support boot UEFI
From: meta-luv
This is an unmodified copy of
github.com/01org/luv-yocto/meta-luv/recipes-core/ovmf revision
4be4329.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch
| 48 +-
meta/recipes-c
When enabled via PACCKAGECONFIG = "secureboot" (off by default because
of the extra work and license change), the recipe compiles OVMF twice,
once without Secure Boot, once with. This is the same approach as in
https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec
The results are "ovmf.q
Fixes a build issue when nasm was not build already because of
something else.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/ovmf/ovmf_git.bb
b/meta/recipes-core/ovmf/ovmf_git.bb
index e722db5..13b583b
When used with '-drive if=pflash', qemu will store UEFI variables
inside the firmware image file. That is unexpected for a file located in
the sysroot, which should be read-only, while it is normal for image
files in the deploy/images directory. Therefore that directory is a
better place for use wi
The Fedora srpm [1] seems to have no problems with parallel
compilation, so let's also use that for the target. The native
tools however indeed have dependency problems:
| test_Ecc_CParser (CheckPythonSyntax.Tests) ... gcc -o ../bin/EfiRom
-L/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/u
In the simplest case, "runqemu qemux86 qcow2 ovmf" for an
EFI-enabled image in the qcow2 format will locate the ovmf.qcow2
firmware file deployed by the ovmf recipe in the image deploy
directory, override the graphics hardware with "-vga std" because that
is all that OVMF supports, and boot with U
The magic detection of the rootfs parameter only worked for image
recipes which embedd the "image" string in the middle, as in
"core-image-minimal".
Sometimes it is more natural to call an image "something-image". To
get such an image detected by runqemu, "-image" at the end of a
parameter must al
When booting a qemu virtual machine with ovmf.secboot, it comes up
with no keys installed and thus Secure Boot disabled. To lock down
the machine like a typical PC, one has to enroll the same keys
that PC vendors normally install, i.e. the ones from Microsoft.
This can be done manually (see
https:
This patch was added to meta-luv for kernel testing purposes and
probably is not relevant for OE-core.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch | 110
+
meta/recipes
'arg' isn't defined, the right name there is 'p'.
This fixes a rather obscure error message when that code path
ends up being taken:
$ runqemu some/existing-file-name
runqemu - ERROR - name 'arg' is not defined
runqemu - ERROR - Try 'runqemu help' on how to use it
Signed-off-by: Patrick Ohly
--
Without this patch, linking fails with a missing implementation of
yy_scan_string. This looks like a regression in flex, because 2.6.0 generated
different code that called PrParser_scan_string
resp. DtParser_scan_string.
Working around that in acpica until this is better understood or fixed
in fle
On 20 January 2017 at 13:36, Andreas Müller
wrote:
> | ERROR: ParseError at
> /home/superandy/oe-core/sources/openembedded-core/
> meta/conf/bitbake.conf:704:
> Could not include required file conf/multiconfig/${BB_CURRENT_MC}.conf
>
The patch creates the file that it requires:
meta/conf/bitba
On 01/20/2017 07:30 AM, Burton, Ross wrote:
On 20 January 2017 at 13:29, Maxin B. John mailto:maxin.j...@intel.com>> wrote:
> The issue here is that in a multilib build the ${base_libdir} is
resolving to /lib64 which completely breaks some tools that fully expect
/lib/modules to be a fixe
On 20 January 2017 at 13:48, Jason Wessel
wrote:
> WARNING: linux-yocto-4.8.12+gitAUTOINC+3edb4de355_9bcb4ea3fa-r0
> do_package: QA Issue: linux-yocto: Files/directories were installed but not
> shipped in any package:
> /lib64
> /lib/modules/4.8.17-yocto-standard/modules.builtin
> /lib64/f
On Fri, Jan 20, 2017 at 2:42 PM, Burton, Ross wrote:
>
> On 20 January 2017 at 13:36, Andreas Müller
> wrote:
>>
>> | ERROR: ParseError at
>>
>> /home/superandy/oe-core/sources/openembedded-core/meta/conf/bitbake.conf:704:
>> Could not include required file conf/multiconfig/${BB_CURRENT_MC}.conf
== Series Details ==
Series: UEFI + Secure Boot + qemu (rev4)
Revision: 4
URL : https://patchwork.openembedded.org/series/4506/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the
On 01/20/2017 07:52 AM, Burton, Ross wrote:
On 20 January 2017 at 13:48, Jason Wessel mailto:jason.wes...@windriver.com>> wrote:
WARNING: linux-yocto-4.8.12+gitAUTOINC+3edb4de355_9bcb4ea3fa-r0 do_package:
QA Issue: linux-yocto: Files/directories were installed but not shipped in any
packa
On Fri, 2017-01-20 at 13:53 +, Patchwork wrote:
> * Issue A patch file has been added, but does not have a
> Signed-off-by tag [test_signed_off_by_presence]
> Suggested fixSign off the added patch file
> (meta/recipes-extended/acpica/acpitests/aapits-linux.patch)
>
> * Iss
On 20 January 2017 at 14:07, Patrick Ohly wrote:
> This is intentional: I'm not the original author and didn't want to mess
> too much with the recipe. Should I add Upstream-Status in a separate
> commit?
>
Sneak it in, it's just a minor change.
Ross
--
'arg' isn't defined, the right name there is 'p'.
This fixes a rather obscure error message when that code path
ends up being taken:
$ runqemu some/existing-file-name
runqemu - ERROR - name 'arg' is not defined
runqemu - ERROR - Try 'runqemu help' on how to use it
Signed-off-by: Patrick Ohly
--
Without this patch, linking fails with a missing implementation of
yy_scan_string. This looks like a regression in flex, because 2.6.0 generated
different code that called PrParser_scan_string
resp. DtParser_scan_string.
Working around that in acpica until this is better understood or fixed
in fle
The Fedora srpm [1] seems to have no problems with parallel
compilation, so let's also use that for the target. The native
tools however indeed have dependency problems:
| test_Ecc_CParser (CheckPythonSyntax.Tests) ... gcc -o ../bin/EfiRom
-L/fast/build/ostro/x86/tmp-glibc/sysroots/x86_64-linux/u
When enabled via PACCKAGECONFIG = "secureboot" (off by default because
of the extra work and license change), the recipe compiles OVMF twice,
once without Secure Boot, once with. This is the same approach as in
https://src.fedoraproject.org/cgit/rpms/edk2.git/tree/edk2.spec
The results are "ovmf.q
Fixes a build issue when nasm was not build already because of
something else.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf_git.bb | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/recipes-core/ovmf/ovmf_git.bb
b/meta/recipes-core/ovmf/ovmf_git.bb
index e722db5..13b583b
When used with '-drive if=pflash', qemu will store UEFI variables
inside the firmware image file. That is unexpected for a file located in
the sysroot, which should be read-only, while it is normal for image
files in the deploy/images directory. Therefore that directory is a
better place for use wi
There seems to be a consensus that supporting UEFI in OE-core for qemu
would be valuable, and there have been some (stalled) attempts to add
it. For reference, see:
[OE-core] [PATCH V3 0/3] Add UEFI firmware for qemux86*
[OE-core] Add ovmf-native to make qemu-native/runqemu support boot UEFI
In the simplest case, "runqemu qemux86 qcow2 ovmf" for an
EFI-enabled image in the qcow2 format will locate the ovmf.qcow2
firmware file deployed by the ovmf recipe in the image deploy
directory, override the graphics hardware with "-vga std" because that
is all that OVMF supports, and boot with U
From: Fathi Boudra
qemu support for UEFI in OE-core depends on OVMF, which needs the iasl
tools provided by this recipe. There's also an iasl recipe in
meta-luv, but than can and will be replaced by this one, thus reducing
overall maintenance work.
Copied from meta-openembedded rev fa65be9ba (cu
This patch was added to meta-luv for kernel testing purposes and
probably is not relevant for OE-core.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-OvmfPkg-Enable-BGRT-in-OVMF.patch | 110
+
meta/recipes
The magic detection of the rootfs parameter only worked for image
recipes which embedd the "image" string in the middle, as in
"core-image-minimal".
Sometimes it is more natural to call an image "something-image". To
get such an image detected by runqemu, "-image" at the end of a
parameter must al
When booting a qemu virtual machine with ovmf.secboot, it comes up
with no keys installed and thus Secure Boot disabled. To lock down
the machine like a typical PC, one has to enroll the same keys
that PC vendors normally install, i.e. the ones from Microsoft.
This can be done manually (see
https:
From: meta-luv
This is an unmodified copy of
github.com/01org/luv-yocto/meta-luv/recipes-core/ovmf revision
4be4329.
Signed-off-by: Patrick Ohly
---
meta/recipes-core/ovmf/ovmf/0001-BaseTools-Force-tools-variables-to-host-toolchain.patch
| 48 +-
meta/recipes-c
== Series Details ==
Series: UEFI + Secure Boot + qemu (rev5)
Revision: 5
URL : https://patchwork.openembedded.org/series/4506/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been executed on the
Currently the recipe depends on the mulitlib libcs all being built
but the dependencies don't account for this. Fix the DEPENDS so
that the requires pieces are all built first rather than relying on
luck.
Signed-off-by: Richard Purdie
---
meta/recipes-core/meta/meta-environment.bb | 4
1 fi
This code is already used in two places and we need it in others so
turn it into its own function.
Signed-off-by: Richard Purdie
---
meta/classes/utils.bbclass | 20 ++--
1 file changed, 10 insertions(+), 10 deletions(-)
diff --git a/meta/classes/utils.bbclass b/meta/classes/uti
On Fri, Jan 20, 2017 at 3:52 AM, Robert P. J. Day
wrote:
>
> the earlier note from ross i had totally forgotten about ...
>
> On Tue, 20 Dec 2016, Burton, Ross wrote:
>
> > FWIW I had a quick look at this. I'm certainly no perl guru and can
> > barely understand it, but it does *so much* wrong
On Fri, 2017-01-20 at 15:12 +0100, Patrick Ohly wrote:
> Without this patch, linking fails with a missing implementation of
> yy_scan_string. This looks like a regression in flex, because 2.6.0 generated
> different code that called PrParser_scan_string
> resp. DtParser_scan_string.
>
> Working ar
On 01/20/2017 04:34 AM, Max Krummenacher wrote:
Hi
Can we backport the following commit to morty?
got it.
Thanks,
Armin
http://cgit.openembedded.org/openembedded-core/commit/?id=cb4f5ecf32006192baaf41218a3d7b43ca1c2951
It fixes pkgconfig to no longer report an old version.
Currently this b
Hi,
Some comments inline below (with oe-list this time),
Regards,
2017-01-20 17:23 GMT+01:00 Yannick GICQUEL :
> 2017-01-19 20:02 GMT+01:00 Andre McCurdy :
>> On Thu, Jan 19, 2017 at 7:01 AM, Yannick Gicquel
>> wrote:
>>> ccache directories are limited to 1G by default.
>>
>> 1G has been the de
This patchset is related to OEQA Framework for details read the RFC send to the
Openembedded architecture ML.
http://lists.openembedded.org/pipermail/openembedded-architecture/2016-December/000351.html
Also adds the migration of the runtime testing leaving only selftest remains
to migrate.
The t
From: Mariano Lopez
misc: Functions for transform object to other types.
path: Functions for path handling.
test: Functions for operations related to test cases and suites.
[YOCTO #10232]
Signed-off-by: Mariano Lopez
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/core/utils/__init__.py | 0
The OETestDepends decorator could be used over test cases to
define some dependency between them.
At loading time sorting the tests to grauntee that a test case
executes before also raise an exception if found a circular
dependency between test cases.
At before test case run reviews if the depend
loader: Implements OETestLoader handling OETestDecorator
and filtering support when load tests. The OETestLoader is
responsible to set custom methods, attrs of the OEQA
frameowork.
[YOCTO #10231]
[YOCTO #10317]
[YOCTO #10353]
decorator: Add base class OETestDecorator to provide a common
way to de
case: Defines OETestCase base class that provides custom
methods/attrs defined by the framework.
Every OETestCase instance contains a reference to the test
data (d), the test context (tc) and the logger.
Also implements _oe{SetUp,TearDown}Class for make special
handling of OEQA
From: Mariano Lopez
These two decorators stores certain TAG or ID for the test case
also provides support for filtering in loading step.
[YOCTO #10236]
Signed-off-by: Mariano Lopez
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/core/decorator/oeid.py | 23 +++
meta/lib/oe
From: Mariano Lopez
This test suite covers the current functionality for the OEQA
framework.
For run certain test suite,
$ cd meta/lib/oeqa/core/tests
$ ./test_data.py
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/tests/__init__.py | 0
meta
From: Mariano Lopez
The OETimeout provides support for specify certain timeout
in seconds for a test case, if the timeout is reach the SIGALRM
is sent and an exception is raised to notify the timeout.
[YOCTO #10235]
Signed-off-by: Mariano Lopez
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/c
The new oe-test script will be use to run test components with
one single script.
The oe-test script search for test components inside meta/lib/oeqa,
the test components needs to implement OETestContextExecutor inside
context module in order to be supported by oe-test.
[YOCTO #10230]
Signed-off-
The OETestDataDepends decorator skips a test case if a variable
isn't into test data (d).
The skipIfDataVar decorator skips a test case if a variable
has certain value.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/decorator/data.py | 36 ++
The OETestContextExecutor class supports to use oe-test for run core
test component also is a base class for the other test components
(runtime, sdk, selftest).
Te principal functionality is to support cmdline parsing and execution
of OETestContext, the test components could extend the common opti
This function will generates testdata.json by image type.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/rootfs-postcommands.bbclass | 18 ++
1 file changed, 18 insertions(+)
diff --git a/meta/classes/rootfs-postcommands.bbclass
b/meta/classes/rootfs-postcommands.
The export2json function export the variables contained in
the data store to JSON format, the main usage for now will be
to provide test data to QA framework.
Signed-off-by: Aníbal Limón
---
meta/lib/oe/data.py | 28
1 file changed, 28 insertions(+)
diff --git a/met
Serves as an first input of how to the OEQA framework works.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/cases/__init__.py | 0
meta/lib/oeqa/core/cases/example/data.json | 1 +
meta/lib/oeqa/core/cases/example/test_basic.py | 20 +
The README has an introduction and explains how to run the test suite
and creates a new Test component.
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/README | 38 ++
1 file changed, 38 insertions(+)
create mode 100644 meta/l
This function will generates testdata.json per SDK type.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/populate_sdk_base.bbclass | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/meta/classes/populate_sdk_base.bbclass
b/meta/classes/populate_sdk_base.bbc
From: Mariano Lopez
The bitbake logger changes the way debug is logged and adds
different levels within debug, this is passed as argument
to the function and breaks compatibility with vanilla loggers.
This implements a way to handle this adding a new function for
debug, that will dispatch the co
Those files are used by runtime and sdk test cases, so move to
base directory of oeqa module.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/{runtime => }/files/test.c | 0
meta/lib/oeqa/{runtime => }/files/test.cpp | 0
meta/lib/oeqa/{runtime => }/
Adds case and context modules for SDK based on oetest.py old code.
Enables SDK Test component usage with oe-test, the SDK Test component
adds command line options for specify sdk installed dir, sdk environment
and target/hosts maniftest.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by:
Don't use bitbake references inside utils modules, in order todo
that changes getVar calls for arguments in the __init__ method like
dl_dir for all the classes and testlogdir, builddatetime in
SDKBUildProject.
Also don't export proxies inside _download_archive method, a good
practice is to setup t
Summary of the changes:
- Remove auto extend_path using pkgutil at __init__, is not needed.
- Change base class to OESDKTestCase.
- Add td_vars attr to set dependencies of certain variables in test
data.
- Change skips from module level to class level because Test context
(tc)
now isn't at modul
It doesn't make sense to have files related to sdk module into runtime
module.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/{runtime => sdk}/files/testsdkmakefile | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/lib/oeqa/{runtime =>
The TEST_LOG_DIR was used for store sdk_target_log this log
contains the output of the run of build commands now that information
could be found also on log.do_testsdk under WORKDIR.
The log will continue to store into SDK_DIR instead of TEST_LOG_DIR.
Signed-off-by: Aníbal Limón
---
meta/classe
For match with the new structure of the OEQA framework.
In the new framework Test component base directory in this case
sdk module will contain case and context implementations.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/sdk/{ => cases}/__init__.
The extensible sdk context and case modules extends the sdk ones,
this means that the tests from sdk are run also the sdkext tests.
Enables support in context for use oe-test esdk command for run
the test suites, the same options of sdk are required for run esdk tests.
Removes old related to case
For match with the new structure of the OEQA framework.
In the new framework Test component base directory in this case
sdk module will contain case and context implementations.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/sdkext/__init__.py | 3 ---
meta/lib/oeqa
The new buildproject module will contain only BuildProject class
a helper class for build source code.
The remaining classes TargetBuildProject and SDKBuildProject was
move to runtime and sdk respectively.
[YOCTO #10599]
Signed-off-by: Aníbal Limón
Signed-off-by: Mariano Lopez
---
meta/lib/oe
The functionality provided is the same with imporvements on code
reuse and better interfaces.
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 75 +++-
1 file changed, 60 insertions(+), 15 deletions(-)
diff --git a/meta/classes/testsdk.bbcla
Signed-off-by: Aníbal Limón
---
meta/classes/testsdk.bbclass | 98
1 file changed, 45 insertions(+), 53 deletions(-)
diff --git a/meta/classes/testsdk.bbclass b/meta/classes/testsdk.bbclass
index 176dafd..69689a1 100644
--- a/meta/classes/testsdk.bbcl
Common files was move to oeqa/files from oeqa/runtime/files
because the same files are used across Runtime,SDK,eSDK tests.
Signed-off-by: Aníbal Limón
---
meta/classes/testexport.bbclass | 5 +
meta/lib/oeqa/oetest.py | 1 +
meta/lib/oeqa/runtime/gcc.py| 4 ++--
meta/lib/oeqa/run
Summary,
- Changes base case class to OESDKExtTest.
- Changes decorator classes to new ones.
- Chnages variable names sdktestdir -> sdk_dir.
- Added missing license to MIT.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/sdk/cases/buildgalculator.py | 2 +-
meta/lib/oeqa/sdk/cases/gcc.py
The new oeqa core framework will modify the structure of the runtime
folder the new runtime folder will have python code inside to support
runtime test cases.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/{runtime => runtime_cases}/_ptest.py | 0
meta/lib/oeqa/{runtime => runtime_c
TargetBuildProject was refactored to avoid bitbake dependency so
the instance don't allow to pass data store anymore.
classes/testimage: Export proxies before run tests
The TargetBuildProject based tests download archives from network.
Signed-off-by: Aníbal Limón
---
meta/classes/testimage.bbc
From: Mariano Lopez
This adds OERuntimeTestCase, OERuntimeTestContext, and OERuntimeTestLoader
to be used for runtime testing.
As expected there are some changes in runtime context:
- Adds the target to be used for runtime testing, the default
is a SSH connection to the device under test runnin
From: Mariano Lopez
With this commit now it is possible to add targets with SSH for testing.
Most of it was imported for existing code, with improvements in log
handling.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/target/__init__.py | 33 +
meta/lib/oeqa/core/targ
From: Mariano Lopez
This new decorator will be used to skip the test
if the image under test doesn't have the required
packages installed.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/runtime/decorator/package.py | 53 ++
1 file changed, 53 inserti
From: Mariano Lopez
This adds a new decorator to check if image under tests has
certain DISTRO_FEATURE or IMAGE_FEATURE.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/decorator/data.py | 28
1 file changed, 28 insertions(+)
diff --git a/meta/
From: Mariano Lopez
This add the option to select what tests to run in the
[.[.]] format.
Currently it just support modules
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/context.py | 6 ++
1 file changed, 6 insertions(+)
diff --git a/meta/lib/oeqa/core/context.py b/meta/lib/oeqa/co
From: Mariano Lopez
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/runtime/utils/targetbuildproject.py | 29 +--
1 file changed, 16 insertions(+), 13 deletions(-)
diff --git a/meta/lib/oeqa/runtime/utils/targetbuildproject.py
b/meta/lib/oeqa/runtime/utils/targetbuildprojec
From: Mariano Lopez
As part of the refactor we require to move the files used
in runtime testing to the new directory. This also adds
the path to the runtime test context.
[YOCTO #10234]
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/runtime/context.py | 2 ++
From: Mariano Lopez
skipIfNotDataVar will skip a test if a variable doesn't have certain value.
skipIfNotInDataVar will skip a test if a value is not in a certain variable.
Signed-off-by: Mariano Lopez
---
meta/lib/oeqa/core/decorator/data.py | 36 +++-
1 file
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/runtime/context.py | 56 ++--
1 file changed, 36 insertions(+), 20 deletions(-)
diff --git a/meta/lib/oeqa/runtime/context.py b/meta/lib/oeqa/runtime/context.py
index e692bc0..ec378bb 100644
--- a/meta/lib/oeqa/run
To avoid getVar calls inside a utils module, also moves
get_host_dumper import inside testexport isn't needed.
[YOCTO #10231]
Signed-off-by: Aníbal Limón
---
meta/classes/testexport.bbclass | 1 -
meta/classes/testimage.bbclass | 5 +++--
meta/lib/oeqa/runtime/context.py | 18 +
This commit will prepare context to use qemu and not just
simpleremote.
Signed-off-by: Aníbal Limón
---
meta/lib/oeqa/runtime/context.py | 18 +-
1 file changed, 13 insertions(+), 5 deletions(-)
diff --git a/meta/lib/oeqa/runtime/context.py b/meta/lib/oeqa/runtime/context.py
ind
1 - 100 of 142 matches
Mail list logo
