Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Vlad Zakharov <Vladislav.Zakharov@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] buildroot autobuild we access
Date: Wed, 13 Jul 2016 14:02:14 +0000	[thread overview]
Message-ID: <1468418534.19768.60.camel@synopsys.com> (raw)
In-Reply-To: <20160713155237.1797c8a2@free-electrons.com>

Hi all,

On Wed, 2016-07-13 at 15:52 +0200, Thomas Petazzoni wrote:
> Hello,
> 
> On Wed, 13 Jul 2016 13:38:17 +0000, Vlad Zakharov wrote:
> 
> > 
> > Sometimes I use your web page with autobuild buildroot results:
> > http://autobuild.buildroot.net/
> > 
> > And I found the following behavior:?
> > When I want to view results limited to the ARC architecture, I click
> > at "arc" link in the "Arch" column. After that I get to a page with
> > results for ARC.?
> > 
> > But when I want to get older results (click at "Next results" at the
> > bottom of the web page) I get a page with next 50 results for all
> > architectures, not only for ARC.
> Correct.
> 
> > 
> > I looked at the browser's address bar and found the following:
> > 	1) When I click at "arc" a GET request with parameter
> > "arch=arc" is sent, 2) Then I click at "Next results" request with
> > "start=50" is sent, but "arch=arc" parameter gets missed. So I get
> > results for all architectures.
> > 
> > Thereafter?if I want to get results from 50 to 100 and older for ARC
> > I have to edit the address bar myself to send GET request with
> > "arch=arc&start=50" parameters.
> > 
> > I think it isn't very convenient that when we click at "Next results"
> > while viewing a page for specific arch we are getting results for all
> > archs. As for me we should get next 50 results for that specific arch.
> > 
> > To fix it we just have not to lose "arch" parameter when clicking at
> > "Next results" link.
> This is just a limitation of the pile of PHP crap that I wrote to run
> autobuild.buildroot.org. The code is at
> http://git.buildroot.org/buildroot-test/ (of course, once the Git
> repository will be back), so do not hesitate to send patches to improve
> things. Be ready for a dive into a pile of horrible code if you start
> looking at this PHP stuff.
> 
> Note that you can also use the magic "step" argument to get more than
> 50 results per-page (though it is limited to max 250 results per page
> IIRC). So, you can do:
> 
> 	http://autobuild.buildroot.net/?arch=arc&step=250&status=NOK
> 
> To get the latest 250 failures happening on ARC.
> 
> Best regards,
> 
> Thomas
Okay, thank you for your advices.

Unfortunately we still have to much failures for our ARC architecture, so we have a lot of urgent work.
Despite this I will try to improve that when I find some free time.

-- 
Best regards,
Vlad Zakharov <vzakhar@synopsys.com>

  reply	other threads:[~2016-07-13 14:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-13 13:38 [Buildroot] buildroot autobuild we access Vlad Zakharov
2016-07-13 13:52 ` Thomas Petazzoni
2016-07-13 14:02   ` Vlad Zakharov [this message]
2016-07-13 14:33     ` Thomas Petazzoni

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=1468418534.19768.60.camel@synopsys.com \
    --to=vladislav.zakharov@synopsys.com \
    --cc=buildroot@busybox.net \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox