From: Ming Liu
do_bootdirectdisk and do_vmimg had been dropped by commit 929ba563:
[ image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types ]
Also need drop their references.
Signed-off-by: Ming Liu
---
The "if qemu_use_kvm" is not needed.
Signed-off-by: Robert Yang
---
meta/lib/oeqa/targetcontrol.py | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/meta/lib/oeqa/targetcontrol.py b/meta/lib/oeqa/targetcontrol.py
index 3255e3a5c63..11e6c820e85
The packages' test cases maybe skipped, check and save them.
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/lib/oeqa/runtime/cases/_ptest.py | 7 ++-
1 file changed, 6 insertions(+), 1 deletion(-)
diff --git a/meta/lib/oeqa/runtime/cases/_ptest.py
We can get the regression result by:
$ git show HEAD ptest_log/pass.fail.skip.*
Can we add ptest to default TEST_SUITES, please ?
// Robert
The following changes since commit a2ab288bd002ebb6e64d46e941fb122e1157ff49:
uninative: Update to 1.7 uninative release (2017-07-30 08:45:49 +0100)
are
Some test cases maybe skipped, let's parse it.
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/lib/oeqa/utils/logparser.py | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/meta/lib/oeqa/utils/logparser.py b/meta/lib/oeqa/utils/logparser.py
* Make it work with current oeqa
* Skip the test if ptest is not in DISTRO_FEATURES
* Skip the test if ptest-pkgs is not in IMAGE_FEATURES
* The logs are saved to:
testimage/ptest_log -> testimage/ptest_log.
* Will write a tool to make regression check
[YOCTO #11547]
Signed-off-by: Robert Yang
It works now.
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/lib/oeqa/runtime/cases/{_ptest.py => ptest.py} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename meta/lib/oeqa/runtime/cases/{_ptest.py => ptest.py} (100%)
diff --git
given that some significant changes have been made to i2c-tools since
version 3.1.2, is it worth adding a git-versioned recipe of that to oe-core,
and using DEFAULT_PREFERENCE to force people to select it if they want it?
in particular, the code base has been restructured, and a new utility,
Changes in V2:
1 Also drop the reference to image-vm.bbclass.
//Ming Liu
2017-07-31 10:56 GMT+02:00 :
> From: Ming Liu
>
> do_bootdirectdisk and do_vmimg had been dropped by commit 929ba563:
> [ image: Convert vmdk/vdi/qcow2 to strict
The author's initial intent was to use a git hook to automatically call
update-server-info, but the wrong hook type was chosen (post-update). A
post-commit one will do the job, hence allowing to drop the explicit call to
update-server-info.
Signed-off-by: Andrea Galbusera
---
Commit 4657bc9d165e51981e034e73e7b92552e873eef7 replaced the git pull logic with
the git fetch + git reset --hard combo, but resetting to HEAD does not really
pull in new commits from remote... Replace with resetting to the upstream branch
instead.
Signed-off-by: Andrea Galbusera
On Mon, 2017-07-31 at 12:35 +0300, Alexander Kanavin wrote:
> On 07/28/2017 05:50 PM, Burton, Ross wrote:
> >
> > And libid3tag:
> >
> > >
> > > compat.gperf:116:1: error: conflicting types for
> > > 'id3_compat_lookup' |
> > In file included from compat.gperf:37:0: |
> >
On 07/31/2017 01:41 PM, rpj...@crashcourse.ca wrote:
given that some significant changes have been made to i2c-tools since
version 3.1.2, is it worth adding a git-versioned recipe of that to
oe-core,
and using DEFAULT_PREFERENCE to force people to select it if they want it?
in particular,
On Sun, Jul 30, 2017 at 08:37:26PM +1000, Jonathan Liu wrote:
> Hi Ed,
>
> On 30 July 2017 at 20:02, Ed Bartosh wrote:
> > On Sat, Jul 29, 2017 at 12:45:27AM +1000, Jonathan Liu wrote:
> >> Zero may be interpreted as no MBR signature present and another
> >>
From: Ming Liu
do_bootdirectdisk and do_vmimg had been dropped by commit 929ba563:
[ image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types ]
Also drop the references to them and image-vm.
Signed-off-by: Ming Liu
It's very important to add IMAGE_CLASSES += "testimage" in local.conf firstly,
otherwise the var like TEST_LOG_DIR (defined in testimage.bbclass) will not be
in testdata.json.
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/classes/testimage.bbclass | 4 ++--
1
This makes the user easier to know how to make commit in buildhistory.
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/classes/buildhistory.bbclass | 2 ++
1 file changed, 2 insertions(+)
diff --git a/meta/classes/buildhistory.bbclass
The section might be None or '', so use "if section" for it.
Fixed:
File "/buildarea/lyang1/poky/meta/lib/oeqa/utils/logparser.py", line 113, in
log_as_files
prefix += section
TypeError: Can't convert 'NoneType' object to str implicitly
[YOCTO #11547]
Signed-off-by: Robert Yang
There might be wild strings when read from target (especially when
reading ptest results), replace the errors to avoid breaking the test.
Fixed: (Not always happen)
$ bitbake core-image-sato -ctestimage
[snip]
status, output = self.target.run('ptest-runner', 0)
File
The ptest log will be saved to buildhistory/ptest_log, we can easily get
the regression result between builds by:
$ git show HEAD ptest_log/pass.fail.skip.*
[YOCTO #11547]
Signed-off-by: Robert Yang
---
meta/classes/buildhistory.bbclass | 28
This should reduce the chance of generating 0x as the disk
system identifier.
Signed-off-by: Jonathan Liu
---
scripts/lib/wic/plugins/imager/direct.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/scripts/lib/wic/plugins/imager/direct.py
Quoting Richard Purdie :
On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
On 07/31/2017 01:41 PM, rpj...@crashcourse.ca wrote:
>
>
> given that some significant changes have been made to i2c-tools
> since
> version 3.1.2, is it worth adding a
On 07/28/2017 05:50 PM, Burton, Ross wrote:
And libid3tag:
| compat.gperf:116:1: error: conflicting types for 'id3_compat_lookup' |
In file included from compat.gperf:37:0: |
../libid3tag-0.15.1b/compat.h:36:26: note: previous declaration of
'id3_compat_lookup' was here | struct id3_compat
On 07/31/2017 12:43 PM, Richard Purdie wrote:
Right. Should we just stop fighting with this, and put a
RECIPE_NO_UPDATE_REASON into gperf? I'd rather not update gperf with
this change reverted.
It does feel like upstream screwed up and should really sort this out.
Do you know what upstream
On 07/31/2017 12:53 PM, Alexander Kanavin wrote:
The only thing I found was this email:
http://lists.gnu.org/archive/html/bug-gperf/2017-01/msg4.html
which was ignored by upstream.
However, both debian testing and fedora rawhide have gperf 3.1, so I'm
not sure how they made it work. I'm
Hi Ed,
On 31 July 2017 at 17:28, Ed Bartosh wrote:
> On Sun, Jul 30, 2017 at 08:37:26PM +1000, Jonathan Liu wrote:
>> Hi Ed,
>>
>> On 30 July 2017 at 20:02, Ed Bartosh wrote:
>> > On Sat, Jul 29, 2017 at 12:45:27AM +1000, Jonathan Liu
On Mon, Jul 31, 2017 at 06:04:47PM +1000, Jonathan Liu wrote:
> >
> > How about random.SystemRandom().randrange(1, 0x) ?
> >
>
> random.SystemRandom().randint(1, 0x) actually
>
This looks ok to me. Thanks.
--
Regards,
Ed
--
___
On 31 July 2017 at 17:58, Jonathan Liu wrote:
> Hi Ed,
>
> On 31 July 2017 at 17:28, Ed Bartosh wrote:
>> On Sun, Jul 30, 2017 at 08:37:26PM +1000, Jonathan Liu wrote:
>>> Hi Ed,
>>>
>>> On 30 July 2017 at 20:02, Ed Bartosh
On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
> On 07/31/2017 01:41 PM, rpj...@crashcourse.ca wrote:
> >
> >
> > given that some significant changes have been made to i2c-tools
> > since
> > version 3.1.2, is it worth adding a git-versioned recipe of that
> > to
> > oe-core,
>
Hi,
On Mon, Jul 31, 2017 at 03:50:17PM +0300, Maxin B. John wrote:
> Hi,
>
> On Mon, Jul 31, 2017 at 07:15:23AM -0400, rpj...@crashcourse.ca wrote:
> >
> >
> > well, here's a possible conundrum ... in that same package (i2c-tools),
> > there appears to be an *obvious* flaw in that the
v2 made it into master, can you send just the fix?
Ross
On 31 July 2017 at 15:56, Patrick Ohly wrote:
> Having common macros in OE-core that are needed by autotools based
> projects makes sense. For example, tpm2.0-tools in meta-measured
> depended on meta-oe only
This patch does not consider current multiconfig settings. I talked with Anibal
about this and he said this wouldn't be an issue after #11429, which he is
working on. Just checked that bug and is still in implementation, so I could
put 11429 as a dependency for 11612?
Regards,
Humberto
Neither Debian not Fedora rebuild dependencies, you'll see a lot of
"rebuild" changelog entries where API changes demanded it to happen.
Our builds take longer but you know the build always works. Their builds
may be broken without anyone noticing for a while.
Ross
On 31 July 2017 at 11:18,
On 31 July 2017 at 10:43, Richard Purdie wrote:
> It does feel like upstream screwed up and should really sort this out.
> Do you know what upstream plan to do (if anything)?
>
Upstream fixed a problem and whilst it was way to big a change for a point
Hi,
On Mon, Jul 31, 2017 at 07:15:23AM -0400, rpj...@crashcourse.ca wrote:
>
> Quoting Richard Purdie :
>
> >On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
> >>On 07/31/2017 01:41 PM, rpj...@crashcourse.ca wrote:
> >>>
> >>>
> >>> given that
Hi Armin,
The following changes in master are relevant to both morty and pyro:
commit 0a7ce0b971a208956cb895ba5a869ec8c5d94703
Author: Tom Rini
Date: Fri Jul 21 18:06:33 2017 -0400
image.bbclass: Correct chaining compression support
commit
El 7/29/2017 a las 8:48 AM, Burton, Ross escribió:
The first line of the python-3.5-manifest.inc:
# WARNING: This file is AUTO GENERATED: Manual edits will be lost next
time I regenerate the file.
You'll need to edit the script and then regenerate the manifest.
Auch, right.
I will send a
Signed-off-by: Ross Burton
---
meta/recipes-support/re2c/re2c/mkdir.patch | 28
meta/recipes-support/re2c/re2c_0.16.bb | 2 +-
2 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 meta/recipes-support/re2c/re2c/mkdir.patch
V2:
- removed the gnome-common dependency that was still in V1
- merged the .inc file into the .bb file and cleaned up the recipe
V3:
- LICENSE = "GPL-3.0-with-autoconf-exception"
Patrick Ohly (2):
autoconf-archive: move from meta-oe to OE-core
autoconf-archive: simplify and fix recipe
Having common macros in OE-core that are needed by autotools based
projects makes sense. For example, tpm2.0-tools in meta-measured
depended on meta-oe only because of autoconf-archive.
This is a verbatim copy of the autoconf-archive recipe in
meta-openembedded rev 1cbd1bc1, with just one change:
The COPYING file specifies pure GPLv3, not GPLv2 & GPLv3, with the
autoconf exception in COPYING.EXCEPTION. OE-core currently has
GPL-3.0-with-GCC-exception for this in meta/conf/licenses.conf, so
this is used here despite the deprecation note for that license
identifier in
Hi Robert,
A few minor comments below.
On Monday, 31 July 2017 11:50:09 AM CEST Robert Yang wrote:
> The ptest log will be saved to buildhistory/ptest_log, we can easily get
> the regression result between builds by:
> $ git show HEAD ptest_log/pass.fail.skip.*
>
> [YOCTO #11547]
>
>
> And there's no references to image_type_uboot.bbclass left, either, yes?
Yes, just double checked, there is no references to image_type_uboot.
//Ming Liu
2017-07-31 14:50 GMT+02:00 Tom Rini :
> On Mon, Jul 31, 2017 at 10:56:28AM +0200, liu.min...@gmail.com wrote:
>
> >
From: He Zhe
lspci and some other software require "pci" in MACHINE_FEATURES and PCI
is valid in the qemux86* context.
Signed-off-by: He Zhe
---
meta/conf/machine/qemux86-64.conf | 2 +-
meta/conf/machine/qemux86.conf| 2 +-
2 files changed, 2
On Monday, 31 July 2017 11:50:00 AM CEST Robert Yang wrote:
> We can get the regression result by:
> $ git show HEAD ptest_log/pass.fail.skip.*
>
> Can we add ptest to default TEST_SUITES, please ?
Is it possible to get an idea of the time impact if we did so?
Cheers,
Paul
--
Paul Eggleton
Current Dev Position: YP 2.4 M2 is in QA, patches are being merged for M3
Next Deadline: YP 2.4 M3 Cut off is Aug. 21, 2017
SWAT team rotation: Armin -> Saul on July 28, 2017.
SWAT team rotation: Saul -> Ross on Aug. 4, 2017.
https://wiki.yoctoproject.org/wiki/Yocto_Build_Failure_Swat_Team
On Mon, Jul 31, 2017 at 10:56:28AM +0200, liu.min...@gmail.com wrote:
> From: Ming Liu
>
> do_bootdirectdisk and do_vmimg had been dropped by commit 929ba563:
> [ image: Convert vmdk/vdi/qcow2 to strict CONVERSION_CMD types ]
>
> Also drop the references to
On 30 July 2017 at 01:17, Tom Rini wrote:
> > diff --git a/meta-poky/conf/local.conf.sample.extended
> b/meta-poky/conf/local.conf.sample.extended
> > index 0560de8..331fdd1 100644
> > --- a/meta-poky/conf/local.conf.sample.extended
> > +++
== Series Details ==
Series: move autoconf-archive into OE-core (rev2)
Revision: 2
URL : https://patchwork.openembedded.org/series/8001/
State : failure
== Summary ==
Thank you for submitting this patch series to OpenEmbedded Core. This is
an automated response. Several tests have been
On Monday, 31 July 2017 11:50:02 AM CEST Robert Yang wrote:
> * Will write a tool to make regression check
This commit doesn't do this and it's not completely covered by the rest of the
series. I think you could say perhaps more appropriately "This provides data
that could be used to detect
On Mon, Jul 31, 2017 at 7:55 AM, Burton, Ross wrote:
> Neither Debian not Fedora rebuild dependencies, you'll see a lot of
> "rebuild" changelog entries where API changes demanded it to happen.
>
> Our builds take longer but you know the build always works. Their builds
>
On Mon, Jul 31, 2017 at 5:50 AM, Maxin B. John wrote:
> Hi,
>
> On Mon, Jul 31, 2017 at 07:15:23AM -0400, rpj...@crashcourse.ca wrote:
>>
>> Quoting Richard Purdie :
>>
>> >On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
>>
On Mon, Jul 31, 2017 at 4:20 PM, Khem Raj wrote:
>
>
> On 7/31/17 12:12 PM, Otavio Salvador wrote:
>> Hello Ross,
>> Hello Khem,
>>
>> On Sat, Jul 29, 2017 at 3:28 PM, Burton, Ross wrote:
>>> Failed in the no-x11 builder at least so far:
>>>
>>> ERROR:
On 7/31/17 12:12 PM, Otavio Salvador wrote:
> Hello Ross,
> Hello Khem,
>
> On Sat, Jul 29, 2017 at 3:28 PM, Burton, Ross wrote:
>> Failed in the no-x11 builder at least so far:
>>
>> ERROR: go-dep-0.2.0-r0 do_package: QA Issue: go-dep: Files/directories were
>>
On Sun, 2017-07-23 at 16:51 -0700, wei.tee...@intel.com wrote:
> +
> +SUMMARY_initramfs-module-install-efi = "initramfs support for installation
> option"
> +RDEPENDS_initramfs-module-install-efi = "${PN}-base parted e2fsprogs-mke2fs
> dosfstools util-linux-blkid"
>
Hello Ross,
Hello Khem,
On Sat, Jul 29, 2017 at 3:28 PM, Burton, Ross wrote:
> Failed in the no-x11 builder at least so far:
>
> ERROR: go-dep-0.2.0-r0 do_package: QA Issue: go-dep: Files/directories were
> installed but not shipped in any package:
>
On Thu, 2017-07-27 at 18:54 -0700,
leonardo.sandoval.gonza...@linux.intel.com wrote:
> 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
>
On 7/31/17 12:40 PM, akuster808 wrote:
>
>
> On 07/31/2017 10:31 AM, Mark Hatle wrote:
>> On 7/31/17 12:16 PM, Armin Kuster wrote:
>>> Signed-off-by: Armin Kuster
>>> ---
>>> meta/conf/machine/include/arm/arch-armv8.inc | 25 +
>>> 1 file changed,
On Wed, 2017-07-12 at 12:29 -0700, wei.tee...@intel.com wrote:
> +SUMMARY_initramfs-module-setup-live = "initramfs support for setup
> live"
> +RDEPENDS_initramfs-module-setup-live = "${PN}-base udev-extraconf"
> +FILES_initramfs-module-setup-live = "/init.d/80-setup-live"
Same problem as with
== Series Details ==
Series: Update armv8 tune file
Revision: 1
URL : https://patchwork.openembedded.org/series/8041/
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 proposed
Signed-off-by: Armin Kuster
---
meta/conf/machine/include/arm/arch-armv8.inc | 25 +
1 file changed, 25 insertions(+)
diff --git a/meta/conf/machine/include/arm/arch-armv8.inc
b/meta/conf/machine/include/arm/arch-armv8.inc
index 5e832fa..dc1ba5e
This extends arch-armv8 support to enable armv8-a and crypto.
Add cortexa53 framework.
Boot tested on Odroid-c2 (cortexa53)
Armin Kuster (2):
armv8: update to use armv8-a tune
new tune: add base cortexa53 support
meta/conf/machine/include/arm/arch-armv8.inc | 25 +
On 07/31/2017 10:31 AM, Mark Hatle wrote:
On 7/31/17 12:16 PM, Armin Kuster wrote:
Signed-off-by: Armin Kuster
---
meta/conf/machine/include/arm/arch-armv8.inc | 25 +
1 file changed, 25 insertions(+)
diff --git
---
meta/conf/machine/include/tune-cortexa53.inc | 18 ++
1 file changed, 18 insertions(+)
create mode 100644 meta/conf/machine/include/tune-cortexa53.inc
diff --git a/meta/conf/machine/include/tune-cortexa53.inc
b/meta/conf/machine/include/tune-cortexa53.inc
new file mode
On Fri, Jul 28, 2017 at 04:47:40PM -0700, Andre McCurdy wrote:
> On Fri, Jul 28, 2017 at 1:26 PM, Denys Dmytriyenko wrote:
> > From: Denys Dmytriyenko
> >
> > Signed-off-by: Denys Dmytriyenko
> > ---
> > v1 - procude -> produce
> > v2 - produce ->
On 7/31/17 10:51 AM, Mark Hatle wrote:
> On 7/31/17 12:40 PM, akuster808 wrote:
>>
>>
>> On 07/31/2017 10:31 AM, Mark Hatle wrote:
>>> On 7/31/17 12:16 PM, Armin Kuster wrote:
Signed-off-by: Armin Kuster
---
meta/conf/machine/include/arm/arch-armv8.inc | 25
On 7/31/17 4:15 AM, rpj...@crashcourse.ca wrote:
>
> Quoting Richard Purdie :
>
>> On Mon, 2017-07-31 at 13:41 +0300, Alexander Kanavin wrote:
>>> On 07/31/2017 01:41 PM, rpj...@crashcourse.ca wrote:
>>> >
>>> >
>>> > given that some significant changes
On 7/31/17 12:16 PM, Armin Kuster wrote:
> Signed-off-by: Armin Kuster
> ---
> meta/conf/machine/include/arm/arch-armv8.inc | 25 +
> 1 file changed, 25 insertions(+)
>
> diff --git a/meta/conf/machine/include/arm/arch-armv8.inc
>
The COPYING file specifies pure GPLv3, not GPLv2 & GPLv3, with the
autoconf exception in COPYING.EXCEPTION. OE-core currently has
GPL-3.0-with-GCC-exception for this in meta/conf/licenses.conf, so
this is used here despite the deprecation note for that license
identifier in
On Tue, Jul 25, 2017 at 1:07 AM, Ming Liu wrote:
> Hi, Burton:
>
> I also agree with you, your suggestion is better.
>
> Hi, Khem:
>
> But is this a bug of binutils? Or musl libc? Since I had only observed this
> error with musl libc only, it did not occur with glibc.
>
On Mon, Jul 31, 2017 at 04:16:24PM -0400, drew.mose...@northern.tech wrote:
> From: Drew Moseley
>
> This class was removed with commit:
> OE-Core rev: 65f27122950a35a67ce39ae4cfe93d0dca6b0dab
>
> Signed-off-by: Drew Moseley
On 07/31/2017 09:38 PM, Paul Eggleton wrote:
On Monday, 31 July 2017 11:50:02 AM CEST Robert Yang wrote:
* Will write a tool to make regression check
This commit doesn't do this and it's not completely covered by the rest of the
series. I think you could say perhaps more appropriately "This
* Upstream filename added "v" before version:
- Add UPSTREAM_CHECK_REGEX
- Update SRC_URI to include the "v"
- Point ${S} to proper directory
* Patch for required headers no longer needed in current upstream
Signed-off-by: Tim Orling
---
On 07/31/2017 09:30 PM, Paul Eggleton wrote:
Hi Robert,
A few minor comments below.
On Monday, 31 July 2017 11:50:09 AM CEST Robert Yang wrote:
The ptest log will be saved to buildhistory/ptest_log, we can easily get
the regression result between builds by:
$ git show HEAD
Hi, Khem:
Just tried, but the error still could be observed with the patch
applied, for instance:
|
We have a variable YOCTO_ALTERNATE_EXE_PATH to point to
target sysroot, utilize this in mesa to use native version
of llvm-config to report values from target sysroot.
Its in a way similar to --sysroot option
Signed-off-by: Khem Raj
---
We have a variable YOCTO_ALTERNATE_EXE_PATH to point to
target sysroot, utilize this in mesa to use native version
of llvm-config to report values from target sysroot.
Its in a way similar to --sysroot option
strip out rpath since its absolute path and incorrect thusly
Signed-off-by: Khem Raj
Upgrade librsvg from 2.40.17 to 2.40.18.
Signed-off-by: Huang Qiyu
---
meta/recipes-gnome/librsvg/{librsvg_2.40.17.bb => librsvg_2.40.18.bb} | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
rename meta/recipes-gnome/librsvg/{librsvg_2.40.17.bb =>
78 matches
Mail list logo