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 13:38:17 +0000	[thread overview]
Message-ID: <1468417097.19768.49.camel@synopsys.com> (raw)

Hi Peter and Thomas,

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.

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.

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

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

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