Hi Richard,
Sorry for the confusion.
Yes, public autobuilder had already covered all automated runtime qemu tests.
We do not plan to run any automated runtime qemu tests.
For automated selftest, we plan to run a subset of selftest tests for a list of
qemu architecture (qemu-shutdown &
Hello,
we need to add a raw partition Type=0xda . How can I do that, because "part
-fstype " has no raw or other value.
Mit freundlichen Grüßen / Best regards
Johann Obermayr
--
___
yocto mailing list
yocto@yoctoproject.org
Hi Richard,
Agreed to you inputs!
I had created a new QA process wiki page to compile all inputs.
https://wiki.yoctoproject.org/wiki/New_QA_process
> Do we need to add something to the results to indicate which results are from
> "who"? (i.e. from > the public autobuilder, Intel QA, WR QA,
Hi Richard,
>-Original Message-
>From: richard.pur...@linuxfoundation.org
>Sent: Wednesday, 3 April, 2019 5:20 PM
>To: Jain, Sangeeta ; Poky Build User
>; yocto@yoctoproject.org;
>sjolley.yp...@gmail.com; Yi Zhao
>Cc: ota...@ossystems.com.br; Chan, Aaron Chun Yew
>;
Hello,
now i build a wic image. This has bootia32.efi included.
How can I add bootx64.efi & legacy bios boot ?
Because the image must boot on different x64 machines.
One machine has only efi 64 bit boot support.
Another (older) has only legacy boot support.
After create a image I have copy
On Wed, Apr 3, 2019 at 4:07 PM Paul Eggleton
wrote:
>
> On Thursday, 4 April 2019 5:46:04 AM NZDT Khem Raj wrote:
> > On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote:
> > >
> > > On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote:
> > > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote:
> >
On Thursday, 4 April 2019 5:46:04 AM NZDT Khem Raj wrote:
> On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote:
> >
> > On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote:
> > > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote:
> > > > > The kernel does not have "upgrade foo to the latest
On Wed, Apr 3, 2019 at 9:59 AM Khem Raj wrote:
>
> On Tue, Apr 2, 2019 at 4:51 AM Lluis Campos
> wrote:
> >
> > Hi all,
> >
> > This is my very first question in the Yocto mailing list. Very exited!
> > Please let me know if I should use other list for this.
> >
> >
> > I am building an image
On Tue, Apr 2, 2019 at 4:51 AM Lluis Campos wrote:
>
> Hi all,
>
> This is my very first question in the Yocto mailing list. Very exited!
> Please let me know if I should use other list for this.
>
>
> I am building an image using musl libc instead of gnu libc. I am not
> using yocto-tiny distro,
On Wed, Apr 3, 2019 at 7:41 AM Tom Rini wrote:
>
> On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote:
> > On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote:
> > > > The kernel does not have "upgrade foo to the latest upstream version"
> > > > commits.
> > > >
> > > > With the Automatic
On Wed, Apr 03, 2019 at 11:30:39AM +0100, Burton, Ross wrote:
> On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote:
> > > The kernel does not have "upgrade foo to the latest upstream version"
> > > commits.
> > >
> > > With the Automatic Upgrade Helper this is a semi-automatic task, and
> > > most of
On 02/04/2019 14:51, Lluis Campos wrote:
Hi Paul,
On 02.04.2019 14:49, Paul Barker wrote:
On 02/04/2019 12:45, Lluis Campos wrote:
Hi all,
This is my very first question in the Yocto mailing list. Very
exited! Please let me know if I should use other list for this.
I am building an
As Indicated by Richard Purdie, in order to shutdown the machine we have
to explicitly enable the PIIX4 poweroff driver for the
qemumips/qemumips64 after the kernel commit dd129c6374e9 ("MIPS: Malta:
Use PIIX4 poweroff driver to power down") is merged.
Signed-off-by: Kevin Hao
---
On 4/3/19 3:38 AM, Alexander Kanavin wrote:
> Just to make clear, the AUH workflow does require the maintainer to
> sign off and edit a commit message via 'git commit -s --reset-author
> --amend' for every commit,
Not sure if this a requirement anymore. Most of my packages got updated
by other
Just to make clear, the AUH workflow does require the maintainer to
sign off and edit a commit message via 'git commit -s --reset-author
--amend' for every commit, so AUH does not get in the way of useful
commit messages.
Alex
On Wed, 3 Apr 2019 at 12:31, Burton, Ross wrote:
>
> On Tue, 2 Apr
On Tue, 2 Apr 2019 at 20:46, Tom Rini wrote:
> > The kernel does not have "upgrade foo to the latest upstream version"
> > commits.
> >
> > With the Automatic Upgrade Helper this is a semi-automatic task, and
> > most of the time there is no specific motivation other than upgrading
> > to the
On Wed, Apr 03, 2019 at 04:55:14PM +0800, mingli...@windriver.com wrote:
> From: Mingli Yu
>
> samhain fails on both aarch64 and mips64 targets with:
> | samhain[3013]: FATAL: x_dnmalloc.c: 2790: hashval < AMOUNTHASH
>
> Though there is already a patch
Hi Armin,
For 2.6.2.rc3, QA team shall try to run the execution by referring to the
manual testcases from master.
Thanks,
Yeoh Ee Peng
-Original Message-
From: akuster808 [mailto:akuster...@gmail.com]
Sent: Wednesday, April 3, 2019 5:50 PM
To: Jain, Sangeeta ; Poky Build User
;
Hi all,
I'm setting up a layer that will compile our applications and libraries.
All the applications are based on cmake and they share modules. Before
using yocto I kept the modules in /cmake (under version control)
alongside applications and libraries. With yocto I wrote a recipe that
checkout
On 4/3/19 1:55 AM, mingli...@windriver.com wrote:
> From: Mingli Yu
>
> samhain fails on both aarch64 and mips64 targets with:
> | samhain[3013]: FATAL: x_dnmalloc.c: 2790: hashval < AMOUNTHASH
>
> Though there is already a patch samhain-mips64-aarch64-dnmalloc-hash-fix.patch
> to fix this
Hello,
On 4/3/19 1:06 AM, Jain, Sangeeta wrote:
> Intel and WR YP QA is now working on QA execution for YP build 2.6.2 RC3. We
> are planning to execute following tests for this cycle:
>
> OEQA-Manual tests for following modules:
> 1.SDK
> 2.Eclipse-plugin
> 3.Kernel
> 4.Toaster
On Tue, Apr 02, 2019 at 03:46:14PM -0400, Tom Rini wrote:
> On Tue, Apr 02, 2019 at 09:51:21AM +0300, Adrian Bunk wrote:
> > On Mon, Apr 01, 2019 at 04:20:41PM -0700, akuster808 wrote:
> > >
> > >
> > > On 4/1/19 4:02 PM, Richard Purdie wrote:
> > > > On Mon, 2019-04-01 at 15:33 -0700,
Hi,
This is good information and helps a lot, thanks! I had a question
below.
On Wed, 2019-04-03 at 08:06 +, Jain, Sangeeta wrote:
> Intel and WR YP QA is now working on QA execution for YP build 2.6.2
> RC3. We are planning to execute following tests for this cycle:
>
> OEQA-Manual tests
From: Mingli Yu
samhain fails on both aarch64 and mips64 targets with:
| samhain[3013]: FATAL: x_dnmalloc.c: 2790: hashval < AMOUNTHASH
Though there is already a patch samhain-mips64-aarch64-dnmalloc-hash-fix.patch
to fix this issue, the logic is incomplete and
pass -DCONFIG_ARCH_MIPS64=1 and
Intel and WR YP QA is now working on QA execution for YP build 2.6.2 RC3. We
are planning to execute following tests for this cycle:
OEQA-Manual tests for following modules:
1. SDK
2. Eclipse-plugin
3. Kernel
4. Toaster
5. Bitbake (oe-core)
6. Build-appliance
7.
Hi Richard,
For oe-selftest -r runqemu,meta_ide, configuration we are using is only
changing the machine type.
For adding "who" identifier in resulttool command, we can take it up as an
enhancement.
Thanks & Regards,
Sangeeta Jain
>-Original Message-
>From:
26 matches
Mail list logo
