public inbox for bunsen@sourceware.org
 help / color / mirror / Atom feed
From: "halamour at redhat dot com" <sourceware-bugzilla@sourceware.org>
To: bunsen@sourceware.org
Subject: [Bug bunsen/31651] New: Improve the r-grid-testcase tool
Date: Wed, 17 Apr 2024 19:54:54 +0000	[thread overview]
Message-ID: <bug-31651-12167@http.sourceware.org/bugzilla/> (raw)

https://sourceware.org/bugzilla/show_bug.cgi?id=31651

            Bug ID: 31651
           Summary: Improve the r-grid-testcase tool
           Product: bunsen
           Version: unspecified
            Status: NEW
          Severity: normal
          Priority: P2
         Component: bunsen
          Assignee: bunsen at sourceware dot org
          Reporter: halamour at redhat dot com
  Target Milestone: ---

The r-grid-testcase tool introduced in PR31364 can be improved in various ways,
including design and navigational changes.

- One oddity with the tool currently is that sometimes changing the
vertical/horizontal limits in the filter form does not change the number of
rows/columns as expected. For example in the following link to a view of the
tool, changing the "Vertical Proximity Filter" from 21 to 20 reduces the number
of rows from 4 to 3, but then reducing it any further (up until limit=9), the
number of rows remains at 3. I believe this is reflection of how the proximity
search on the cluster search.

https://builder.sourceware.org/r_grid_testcase/?trid=b606f3a3d7f23035fefed3296455be038be76ef1&expfile=gdb.arch%2Famd64-init-x87-values.exp&subtest=gdb.arch%2Famd64-init-x87-values.exp%3A+check_x87_regs_around_init%3A+check+initial+value+of+%24fstat&vertical=source.gitdescribe&v_limit=21&horizontal=uname-m&h_limit=5

- In the filter form, one of the vertical-limit or horizontal-limit boxes is
updated then submitted, it resets to the previous value briefly, before
refreshing the page and replacing the old value with the new value. This is
related to the use of window.onbeforeunload = function(). This is required to
ensure the filter form reflects the current state of the grid, as otherwise
when navigating back and forth between pages sometimes the filter value will
not match the current grid cell and instead show an older value. I have not yet
found a different way of dealing with this.

- Extending the tool so taht it works on other test suite types  (automake,
glibc, etc). This will involve making modifications to both r-grid-testcase and
r-httpd-browse.

- Adding tests for the tool, specifically r-grid-testcase.

- Resolving the mypy errors that have surfaced due to this tool.

- Better help text on the web view to explain how the cells are populated and
where this information is found

- Other potential feature additions, such as potentially adding a ‘regression’
grid view to the tool

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2024-04-17 19:54 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=bug-31651-12167@http.sourceware.org/bugzilla/ \
    --to=sourceware-bugzilla@sourceware.org \
    --cc=bunsen@sourceware.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).