All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael Wood <michael.g.wood@intel.com>
To: "Barros Pena, Belen" <belen.barros.pena@intel.com>,
	 "toaster@yoctoproject.org" <toaster@yoctoproject.org>
Subject: Re: FW: [Bug 8131] All builds page "Errors"/"Warnings" filters doesn't work
Date: Mon, 28 Sep 2015 18:13:58 +0100	[thread overview]
Message-ID: <56097556.2050301@intel.com> (raw)
In-Reply-To: <D22ED336.66333%belen.barros.pena@intel.com>

Updated the bug:

There are no simple fixes for this that I can see. The field which it used to filter on was removed in this commit:

commit 70c4eb8d3acaad267ee943ebfba793f9cc1c5ee6
Author: Alexandru DAMIAN <alexandru.damian@intel.com  <mailto:alexandru.damian@intel.com>>
Date:   Wed Jun 17 17:30:34 2015 +0100

     bitbake: toaster: refactor build model
    
     We remove the "timespent", "errors_no" and "warnings_no" fields
     in favor of computing the needed values at runtime. This prevents
     inconsistencies in the UI.
    
     Also removeing all references to BuildRequests from the interface -
     all build details now display in the build dashboard.
    
     Minor fixes related to data logging.
    
     (Bitbake rev: 44f37394ed3e4ca02f940be172fe4395b0ee0f7d)
    
     Signed-off-by: Alexandru DAMIAN <alexandru.damian@intel.com  <mailto:alexandru.damian@intel.com>>
     Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org  <mailto:richard.purdie@linuxfoundation.org>>

We will need a new mechanism to do the filtering, we will also be porting this table to ToasterTables so this can be fixed at that point.



Michael


On 28/09/15 11:28, Barros Pena, Belen wrote:
> I've just realised that this issue
>
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=8131
>
> has been moved to 2.1. I understand that we might not have time to fix it
> right now, but it is pretty bad to have stuff in the UI that breaks like
> this does.
>
> Are we 100% sure that we will not be able to fix this before the 2.0
> release? If that's the case, I will submit a patch to hide those filter
> buttons, to avoid exposing broken functionality to users.
>
> Thanks!
>
> Belén
>
>
>
> On 23/09/2015 16:43, "bugzilla-daemon@yoctoproject.org"
> <bugzilla-daemon@yoctoproject.org> wrote:
>
>> Stephen K Jolley <mailto:stephen.k.jolley@intel.com>changed
>> bug 8131 <https://bugzilla.yoctoproject.org/show_bug.cgi?id=8131>
>> WhatRemovedAddedPriorityMedium+ Medium Target Milestone1.9 M3 2.1 QA
>> Contactcristina-danielax.agurida@intel.com stanciux.mihail@intel.com
>> ________________________________________
>> You are receiving this mail because:
>> * You are on the CC list for the bug.
>>



  reply	other threads:[~2015-09-28 17:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-8131-212@https.bugzilla.yoctoproject.org/>
     [not found] ` <bug-8131-212-wu5DEJ0HAX@https.bugzilla.yoctoproject.org/>
2015-09-28 10:28   ` FW: [Bug 8131] All builds page "Errors"/"Warnings" filters doesn't work Barros Pena, Belen
2015-09-28 17:13     ` Michael Wood [this message]
2015-09-29  9:09       ` Barros Pena, Belen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56097556.2050301@intel.com \
    --to=michael.g.wood@intel.com \
    --cc=belen.barros.pena@intel.com \
    --cc=toaster@yoctoproject.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.