On 11/02/2015 18:35, "Bob Cochran" wrote:
>On 01/05/2015 06:59 AM, Barros Pena, Belen wrote:
>> On 28/12/2014 00:18, "William Mills" wrote:
>>
>>>
>>> On 12/27/2014 10:40 AM, Mills, William wrote:
OK, you are not going to believe me but I swear this really happened
...
>>
>> We do bel
On 11 February 2015 at 21:39, Joe MacDonald
wrote:
> > What's more likely happening I suspect is that you are on a newer
> > branch/revision of OE-Core/Poky than the meta-selinux maintainers have
> tested.
> > I can't speak to the maintenance schedule for meta-selinux but maybe
> others
> > with
The Error Reporting Service was rewritten and the URLs are different.
Signed-off-by: Ross Burton
---
.../buildbot/status/web/templates/grid_macros.html |2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
a/lib/python2.7/site-packages/buildbot-0.8.8-py2.7.egg/b
[[meta-selinux][PATCH] Add explicit dependency on layers with recipes we
bbappend.] On 15.02.12 (Thu 04:39) Philip Tricca wrote:
> This is a stop-gap to get meaningful error messages to folks till we get
> per-layer bbappends implemented.
>
> Signed-off-by: Philip Tricca
Merged. Thanks Phil.
I thought I'd better follow this up with a semi-separate thread for
anyone who is using meta-selinux and isn't really interested in the
direct follow-ups when I just indicate a patch has been merged.
This went into master and it captures, I think, the implicit
dependencies in the layer right now.
Hi Ross,
On Thu, Feb 12, 2015 at 12:19 PM, Burton, Ross wrote:
>
> On 11 February 2015 at 21:39, Joe MacDonald
> wrote:
>>
>> > What's more likely happening I suspect is that you are on a newer
>> > branch/revision of OE-Core/Poky than the meta-selinux maintainers have
>> > tested.
>> > I can't
On Wed, 2015-02-11 at 16:29 +, Paul Eggleton wrote:
> (Adding yocto@yoctoproject.org to CC since that is where meta-selinux patches
> tend to go at least)
>
> On Wednesday 11 February 2015 10:53:03 dpquigl wrote:
> > I'm working on OpenXT and it makes use of the meta-selinux repo hosted
> > b
Yesterday, I built a large image using Poky/Yocto 870323cac1e
Today I updated my Poky repo to 231d4a9d3
When I rebuilt the same image, bitbake kicked off more than
5200 tasks, building virtually every package from scratch.
How can I tell why this happened? I don't have buildhistory
enabled, but
On 12 February 2015 at 21:25, Gary Thomas wrote:
> Yesterday, I built a large image using Poky/Yocto 870323cac1e
> Today I updated my Poky repo to 231d4a9d3
>
> When I rebuilt the same image, bitbake kicked off more than
> 5200 tasks, building virtually every package from scratch.
>
> How can I t
On 2015-02-12 14:33, Burton, Ross wrote:
On 12 February 2015 at 21:25, Gary Thomas mailto:g...@mlbassoc.com>> wrote:
Yesterday, I built a large image using Poky/Yocto 870323cac1e
Today I updated my Poky repo to 231d4a9d3
When I rebuilt the same image, bitbake kicked off more than
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero > /dev/null &
#cyclictest -a 0 -p 99 -m -n -l 10 -q
I ran this command as shown by Toyoka at the 2014 Linuxcon Japan
[http://events.linuxfoundation.org/sites/events/files/slides/toyooka_LCJ2014_v1
On Thu, Feb 12, 2015 at 02:25:32PM -0700, Gary Thomas wrote:
> Yesterday, I built a large image using Poky/Yocto 870323cac1e
> Today I updated my Poky repo to 231d4a9d3
>
> When I rebuilt the same image, bitbake kicked off more than
> 5200 tasks, building virtually every package from scratch.
>
>
On 02/12/2015 05:05 PM, Stephen Flowers wrote:
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero > /dev/null &
When I suggested filesystem activity I was suggesting getting a kernel
filesystem and a physical I/O device to be active.
The load above i
On 2015-02-12 7:20 PM, William Mills wrote:
On 02/12/2015 05:05 PM, Stephen Flowers wrote:
So I ran cyclictest with an idle system and loaded with multiple
instances of cat /dev/zero > /dev/null &
When I suggested filesystem activity I was suggesting getting a kernel
filesystem and a physi
14 matches
Mail list logo