On 5/15/19 12:11 PM, Randy MacLeod wrote:
On 5/14/19 10:22 PM, Randy MacLeod wrote:
...
It's tempting to just bump the timeout to 300 seconds
since anything that fails with that timeout really should
be fixed. The right thing is to pass the timeout from ptest-runner
down to valgrind's vg_r
On 5/14/19 7:08 AM, Richard Purdie wrote:
On Mon, 2019-05-13 at 23:57 -0400, Randy MacLeod wrote:
About half the ptests will fail if the executables deployed
as part of the ptest package are stripped. Currently
there is no easy way to only strip the main valgrind
package so leave it and the p
On 5/14/19 10:22 PM, Randy MacLeod wrote:
...
It's tempting to just bump the timeout to 300 seconds
since anything that fails with that timeout really should
be fixed. The right thing is to pass the timeout from ptest-runner
down to valgrind's vg_regtest script. If we have people who set
timeo
On 5/14/19 5:46 PM, richard.pur...@linuxfoundation.org wrote:
On Tue, 2019-05-14 at 17:42 -0400, Randy MacLeod wrote:
On 5/14/19 5:32 PM, richard.pur...@linuxfoundation.org wrote:
Actually, my test was flawed. I just retested and this time it
worked.
What I tested with was:
RDEPENDS_${PN}-ptes
On Tue, 2019-05-14 at 17:42 -0400, Randy MacLeod wrote:
> > We also have a problem that its overflowing the 4GB limit on some
> > image
> > sizes with the debug info included :/
>
> There's an enhancement to track that:
>https://bugzilla.yoctoproject.org/show_bug.cgi?id=13025
> Kevin owns it a
On Tue, 2019-05-14 at 17:42 -0400, Randy MacLeod wrote:
> On 5/14/19 5:32 PM, richard.pur...@linuxfoundation.org wrote:
> > Actually, my test was flawed. I just retested and this time it
> > worked.
> > What I tested with was:
> >
> > RDEPENDS_${PN}-ptest += " sed perl perl-module-file-glob ${PN}
On 5/14/19 5:32 PM, richard.pur...@linuxfoundation.org wrote:
Actually, my test was flawed. I just retested and this time it worked.
What I tested with was:
RDEPENDS_${PN}-ptest += " sed perl perl-module-file-glob ${PN} ${PN}-dbg"
INSANE_SKIP_${PN}-ptest = "debug-deps"
Ah nice. Thanks.
Can
On Tue, 2019-05-14 at 13:54 -0400, Randy MacLeod wrote:
> On 5/14/19 10:08 AM, Richard Purdie wrote:
> > On Mon, 2019-05-13 at 23:57 -0400, Randy MacLeod wrote:
> > > About half the ptests will fail if the executables deployed
> > > as part of the ptest package are stripped. Currently
> > > there i
On 5/14/19 10:08 AM, Richard Purdie wrote:
On Mon, 2019-05-13 at 23:57 -0400, Randy MacLeod wrote:
About half the ptests will fail if the executables deployed
as part of the ptest package are stripped. Currently
there is no easy way to only strip the main valgrind
package so leave it and the pte
On Mon, 13 May 2019 at 20:57, Randy MacLeod wrote:
> About half the ptests will fail if the executables deployed
> as part of the ptest package are stripped. Currently
> there is no easy way to only strip the main valgrind
> package so leave it and the ptests *all* unstripped.
What's the disk usa
On Mon, 2019-05-13 at 23:57 -0400, Randy MacLeod wrote:
> About half the ptests will fail if the executables deployed
> as part of the ptest package are stripped. Currently
> there is no easy way to only strip the main valgrind
> package so leave it and the ptests *all* unstripped.
>
> There is an
About half the ptests will fail if the executables deployed
as part of the ptest package are stripped. Currently
there is no easy way to only strip the main valgrind
package so leave it and the ptests *all* unstripped.
There is an enhancement filed to enable wildcard stripping:
https://bugzilla
12 matches
Mail list logo
