aboutsummaryrefslogtreecommitdiffstats
path: root/dashboard/app/templates.html
Commit message (Collapse)AuthorAgeFilesLines
* dashboard/app: move templates to dirTaras Madan2024-07-051-651/+0
|
* dashboard/app: sort discussions as textDmitry Vyukov2024-07-041-1/+1
| | | | | The current time sorting produces some random order (text is not time). Let's sort as text, it should produce at least some order (e.g. group PATCH together).
* dashboard/app: make coverage menu and page optionalTaras Madan2024-07-041-0/+2
|
* dashboard/app/templates.html: fix menuTaras Madan2024-07-031-1/+1
|
* dashboard: refactor job status linksAleksandr Nogikh2024-06-261-5/+7
| | | | | Print OK only for non-failed and non-crashed jobs. Print links to independent assets independently.
* dashboard/app: add coverage histogramTaras Madan2024-06-201-1/+3
|
* dashboard/app: add bugs found per month graphDmitry Vyukov2024-05-311-0/+2
| | | | Useful to estimate overall syzbot performance.
* dashboard: collect and display repro logsAleksandr Nogikh2024-05-271-1/+4
| | | | | This will help us understand how exactly how we have arrived at the reproducer.
* dashboard/app: add per-manager bug linksDmitry Vyukov2024-05-271-0/+5
|
* dashboard/app: don't print discussion info where there are noneDmitry Vyukov2024-04-261-3/+3
| | | | | | | Currently we print somewhat verbose "💬 0 [3d18h]" when there are no discussions, the date repeats the reporting date. It' makes it hard to visually see when there are conversations and when there are none. Print nothing when there are no discussions.
* dashboard: serve per-manager pagesAleksandr Nogikh2023-12-131-1/+1
| | | | Display last 500 successful builds for every manager.
* dashboard: display failed bug repro attemptsAleksandr Nogikh2023-08-311-0/+24
|
* dashboard: differentiate job invalidation and job restartAleksandr Nogikh2023-08-241-2/+3
| | | | | | | In some cases restarting the failed bisection does not make sense, because we know that the result will be the same. Let admins choose between invalidating the job and restarting it.
* dashboard: display backport listsAleksandr Nogikh2023-08-231-0/+4
| | | | | | | Add a per-namespace page that contains: 1) The list of commits to backport from the trees fuzzed in that namespace. 2) The list of commits to backport into the namespace.
* dashboard: let admins retry jobs from job listsAleksandr Nogikh2023-08-101-0/+1
| | | | | | | Currently we only display the link for latest fix/cause bisections on the bug page. Also display it inside the collapsible job lists.
* dashboard/app: mark fix candidate jobs in job listsAleksandr Nogikh2023-08-071-1/+1
| | | | Distinguish them from normal fix bisections.
* dashboard: display fix candidate info on the bug pageAleksandr Nogikh2023-07-261-6/+16
|
* dashboard: add a link to the assets tutorialAleksandr Nogikh2023-07-251-1/+1
|
* dashboard: display job error link independently of job logAleksandr Nogikh2023-07-171-1/+2
| | | | | Job log can sched more light on what was exactly happening. It's not really correct to omit it.
* dashboard: show per-bisect type job lists for adminsAleksandr Nogikh2023-07-171-1/+1
| | | | | Currently we only show running/pending/recent jobs. Let admins also see the list of the latest cause/fix bisections.
* dashboard: add fake admin namespace to ns dropdownSpace Meyer2023-06-121-0/+3
| | | | | | | | The dropdown is the only UI element that lets users exit the admin page, so removing it from the admin page is not advisable. However since the admin page is not a real namespace, the dropdown will display the name of the first namespace, when visiting the admin page. This confuses new users.
* dashboard: allow admins to retry individual bisectionsSpace Meyer2023-06-121-0/+4
| | | | | | | | | | Changes to our rootfs, compilers or bisection logic regularly cause regressions in our bisection accuracy. Retrying them currently entails fiddling with the GCP datastore directly or mass deleting all failed bisections. This change will allow us to retry specific bisections with a single click.
* dashboard: display bug origin tree testing resultsAleksandr Nogikh2023-05-121-0/+41
| | | | | Display them as a collapsible block on the bug info page. Use colors to distinguish results.
* dashboard: support filtering over multiple labelsAleksandr Nogikh2023-05-101-5/+6
| | | | | | For each label, allow only one value to be specified. At the same time, allow multiple different labels (subsystem, origin, prio, etc) be specified together.
* dashboard: recognize tree origin testing jobsAleksandr Nogikh2023-04-281-1/+3
| | | | | | For now let's just keep them in the patch testing requests list and give them a different name. Later we'll group the information in a much more explicit way.
* dashboard: support bug labelsAleksandr Nogikh2023-04-271-5/+5
| | | | | | | | | | | | | | | | Let bug labels come in three flavours: 1) Bug labels with multiple values (e.g. `subsystems`). 2) Bug labels with only one value (e.g. `prio`). 3) Flags. Let users configure bug labels via email by issuing the following commands: #syz set subsystems: abc, def #syz set no-reminders #syz unset no-reminders Also let users set tags for invididual bugs in reported bug lists: #syz set <1> some-tag
* dashboard: display discussions info on the main pageAleksandr Nogikh2023-04-111-1/+14
|
* dashboard: display collapsible info sections on the bug pageAleksandr Nogikh2023-04-071-3/+2
| | | | | Instead of showing tons of extra information to the user, only show the collapsed titles with counts and let user toggle the sections they need.
* dashboard: collect and display bug-related discussionsAleksandr Nogikh2023-04-061-0/+25
| | | | | | | | | Collect the information about the discussions under bug reports and patches that target the reported bugs. For now only Lore discussions are supported. Display the discussion list on the bug info page.
* dashboard/app: move manager to the end of crashes tableDmitry Vyukov2023-04-031-2/+2
| | | | | | | Manager name does not tell much to end users. They are also long and all prefixed with ci[2]-upstream-, this takes lots of space in the table. Move it to the end of the table.
* dashboard: display the bisect error logAleksandr Nogikh2023-03-071-1/+1
| | | | | In some cases we don't have the bisection log, but only the error log. Adjust the template.
* dashboard: filter by no subsystemsAleksandr Nogikh2023-02-221-0/+3
| | | | | Count the number of bugs without any subsystem and let users filter bugs by this criteria.
* dashboard: add a feedback buttonAleksandr Nogikh2023-02-211-0/+6
|
* dashboard: move subsystems list link to the leftAleksandr Nogikh2023-02-211-4/+4
|
* dashboard: display the subsystem listAleksandr Nogikh2023-02-171-0/+4
| | | | Take the counts from the cache, include links to the filtered bug views.
* dashboard: cache per-subsystem statsAleksandr Nogikh2023-02-171-3/+3
| | | | For each subsystem, collect the number of open, fixed and invalid bugs.
* dashboard: display the list of applied filtersAleksandr Nogikh2023-02-141-0/+17
| | | | | | | Currently it's non obvious whether and what filters are applied to a bug list. Display the list to the user and enable them to drop individual filters.
* dashboard: display subsystems in bug listsAleksandr Nogikh2023-01-271-1/+6
| | | | | To generate filtering URLs, use the ability of context.Context to carry on variable values.
* dashboard: display strace log linksAleksandr Nogikh2023-01-031-1/+1
| | | | | Currently we only underline the difference in emails, do it also in the web version.
* dashboard: display assets in the crash tableAleksandr Nogikh2023-01-031-0/+4
|
* dashboard: add link to the repos pageAleksandr Nogikh2022-12-211-2/+2
| | | | | The `Instances` header currently leads to nowhere. Let's add there a link to the tested repos.
* dashboard: indicate retest repro jobsAleksandr Nogikh2022-12-011-1/+1
| | | | Currently the User field is empty, which makes things confusing.
* dashboard: display running and pending jobs on the admin pageAleksandr Nogikh2022-12-011-1/+1
| | | | | | | This reflects the situation more adequately than just the recent jobs. There are times when failed jobs are retried or manually restarted and the current page just does not show such jobs.
* dashboard: remove accidental whitespace from C Repro cellLee Jones2022-10-261-1/+1
| | | | | | | | | | | Commit 2f3b44ea4 ("dashboard: visualize stale repros") inadvertently added a single space in the "<td class=repro>" tag. This will break tooling which relies on HTML scraping and pattern matching. This patch ensures the formatting is kept consistent whilst honouring the author's true intentions. Fixes: 2f3b44ea4 ("dashboard: visualize stale repros") Signed-off-by: Lee Jones <joneslee@google.com>
* dashboard: visualize stale reprosAleksandr Nogikh2022-08-261-2/+3
| | | | | When rendering a crash list, strike stale repros with a line (like the <s></s> tag does).
* dashboard: show console output for successful patch testsAleksandr Nogikh2022-06-201-2/+4
| | | | Right now it's sent by email, but still not displayed on the web page.
* dashboard: move fix pending bugs away from the main pageAleksandr Nogikh2022-05-301-8/+8
| | | | | They might confuse the users who search the page. Show them in the "Fixed" tab instead.
* dashboard/app: linkify bisection commitsDmitry Vyukov2022-05-121-2/+2
| | | | Very handy to assess if it's the right/wrong commit.
* dashboard/app: open graph pagesDmitry Vyukov2022-05-051-2/+0
| | | | Show graph pages to users who have access to the bugs themselves.
* dashboard/app: show kernel config for the current manager buildDmitry Vyukov2022-05-031-1/+4
| | | | | | | It's useful to be able to look at the current config for a particular manager. Currently it's doable but somewhat ugly (find a recently reported crash and look at its config). Show kernel config for each manager directly.
generated by ggit (джигит) mrf-deployment (git 2.46.0) at 2026-03-22 19:41:29 +0000