i915-infra issueshttps://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues2020-01-30T09:40:22Zhttps://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/95queue preview: display spinner while loading data2020-01-30T09:40:22ZArkadiusz Hilerqueue preview: display spinner while loading dataShard queue (https://intel-gfx-ci.01.org/queue/index.html) with 20+ entries takes about 10s to load for me.
This is the case as it need to do multiple trips to patchwork to get details on the tested series.
We should display a spinner ...Shard queue (https://intel-gfx-ci.01.org/queue/index.html) with 20+ entries takes about 10s to load for me.
This is the case as it need to do multiple trips to patchwork to get details on the tested series.
We should display a spinner and replace it with either results or error message in case of failures when the fetching is done.
Bonus points:
a) adding spinners for BAT queues, they do only single request which is pretty quick so this is not that important
b) populating and reordering (sorting) shards queue as we get more data, so people see how the data is fetch real timehttps://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/86vis.js: Long build "desc" overflows the field2020-01-02T11:38:27ZArkadiusz Hilervis.js: Long build "desc" overflows the field**Cc:** @kumarm
**Issue:** When build description is too long vis.js renders it in combined alt (since !71) view anyway, overflowing the cell.
<details>
<summary>Picture</summary>
![image](/uploads/b97a785deb4450dc8a349e2eaafc9d45/image...**Cc:** @kumarm
**Issue:** When build description is too long vis.js renders it in combined alt (since !71) view anyway, overflowing the cell.
<details>
<summary>Picture</summary>
![image](/uploads/b97a785deb4450dc8a349e2eaafc9d45/image.png)
</details>
**Impact:** Currently the desc are only for postmerge BAT results, for which we have ~20 runs. This gives us enough space so that even longer commit titles fit. The impact is currently negligible, but if we start adding descriptions to shards or post-merge builds it will be visible.https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/69site/index.md: Mention that we take merge-requests for kconfig2019-12-05T10:29:03ZArkadiusz Hilersite/index.md: Mention that we take merge-requests for kconfigArkadiusz HilerArkadiusz Hilerhttps://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/64igt-vis: create a generic result page that displays a test's results using js2019-12-30T06:26:39ZMartin Roukalaigt-vis: create a generic result page that displays a test's results using jsTo reduce our disk space usage, speed up results generation, and reduce transfer times we could create a generic igt-result.html page that would use javascript to load the specified results.json file to display the results for the wanted...To reduce our disk space usage, speed up results generation, and reduce transfer times we could create a generic igt-result.html page that would use javascript to load the specified results.json file to display the results for the wanted test.
Before: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7040/fi-tgl-u/igt@gem_exec_suspend@basic-s3.html
After: https://intel-gfx-ci.01.org/igt-result.html?results=/tree/drm-tip/CI_DRM_7040/fi-tgl-u/results0.json.bz2&test=igt@gem_exec_suspend@basic-s3https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/47vis.js: make cells narrower2020-01-25T15:29:45ZTomi Sarvelavis.js: make cells narrowerAs there is very little extra information within the cells health grid cells, they could be narrower and thus fit more information to the width of the screen.
For comparison, vis.js had approximately 25% narrower cells. It doesn't need ...As there is very little extra information within the cells health grid cells, they could be narrower and thus fit more information to the width of the screen.
For comparison, vis.js had approximately 25% narrower cells. It doesn't need to go that far, but little off would be nice.
Also, there was some discussion with Petri if the 'D' within the cells was necessary or not. @adrinael ?https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/43vis: Figure out good UX for caching the test filter2020-02-06T17:22:32ZArkadiusz Hilervis: Figure out good UX for caching the test filterThe new vis (!33) comes with a text field in the navbar that is used for filtering grids on test names and by default cached that.
The UX it presented though is too confusing (value stays there forever, no button to clear it, not easy ...The new vis (!33) comes with a text field in the navbar that is used for filtering grids on test names and by default cached that.
The UX it presented though is too confusing (value stays there forever, no button to clear it, not easy to spot), especially for people coming without the implementation knowledge so the caching got disabled as of b0980dc3.
TODO:
* [ ] Add a (x) to reset the value
* [ ] Make persistence optional (checkbox?)
* [ ] make filter more visible (either by putting red "filter" in the front or by blinking it?)https://gitlab.freedesktop.org/gfx-ci/i915-infra/-/issues/32vis: Make new tests more visible2020-02-06T09:33:27ZArkadiusz Hilervis: Make new tests more visibleCurrently, to find the new tests in the visualization you have to go to "shards all" view and then search in the page for new tests names.
With #11 we will already start using data from [cibuglog](/gfx-ci/cibuglog) for the visualization...Currently, to find the new tests in the visualization you have to go to "shards all" view and then search in the page for new tests names.
With #11 we will already start using data from [cibuglog](/gfx-ci/cibuglog) for the visualization of the results.
We can do similar thing with information about new tests (cibuglog already has logic for finding them, [example](https://lists.freedesktop.org/archives/igt-dev/2019-February/009605.html)).
With that included in the .json we could have the new tests on the combined views and/or we could highlight them somehow.