mesa_jenkins issueshttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues2023-11-08T20:44:48Zhttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/29debian_installer: Auto-detect drive to install too2023-11-08T20:44:48Zclayton craftdebian_installer: Auto-detect drive to install too*Created by: dcbaker*
It would be terrific if the installer could just detect that it was mounted /dev/sda, so it should use /dev/sdb as the install target, or that the device doesn't have an extra /dev/sd*, but does have a mmcblk devic...*Created by: dcbaker*
It would be terrific if the installer could just detect that it was mounted /dev/sda, so it should use /dev/sdb as the install target, or that the device doesn't have an extra /dev/sd*, but does have a mmcblk device, so install to that.Installer: Make drive selection more robusthttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/18debian_installer: error out if there are not at least two drives connected2020-03-16T21:28:38Zclayton craftdebian_installer: error out if there are not at least two drives connected*Created by: dcbaker*
Don't allow the installer to install over itself.
*Created by: dcbaker*
Don't allow the installer to install over itself.
Installer: Make drive selection more robusthttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/54dEQP-VK.spirv_assembly.instruction.graphics.16bit_storage.uniform_float_32_to...2023-11-08T22:56:16ZLionel LandwerlindEQP-VK.spirv_assembly.instruction.graphics.16bit_storage.uniform_float_32_to_16.uniform_matrix_float_rtz_frag flakyness fixed on DG2We fixed `dEQP-VK.spirv_assembly.instruction.graphics.16bit_storage.uniform_float_32_to_16.uniform_matrix_float_rtz_frag` flakyness on DG2 in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22314
I'm just not sure how to chang...We fixed `dEQP-VK.spirv_assembly.instruction.graphics.16bit_storage.uniform_float_32_to_16.uniform_matrix_float_rtz_frag` flakyness on DG2 in https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/22314
I'm just not sure how to change the CI files to reflect that.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/52CI permission request2022-09-08T16:08:37ZJosé Roberto de SouzaCI permission requestHi
I'm a new member of Intel's Mesa team.
I don't have permission to push a branch to https://gitlab.freedesktop.org/Mesa_CI/repos/mesa to get a CI run.
What is the produced to request access?
ThanksHi
I'm a new member of Intel's Mesa team.
I don't have permission to push a branch to https://gitlab.freedesktop.org/Mesa_CI/repos/mesa to get a CI run.
What is the produced to request access?
Thankshttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/51Proton2021-09-11T18:37:54ZEmilian CretuProtonhttps://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/50Add crucible + vkcts to jljusten job2021-03-01T18:29:25ZJordan JustenAdd crucible + vkcts to jljusten jobCurrently it only tests GL.Currently it only tests GL.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/49Extra fbo-clear-formats stencil tests in gen9_iris_blacklist.conf2020-12-11T18:49:03ZNanley CheryExtra fbo-clear-formats stencil tests in gen9_iris_blacklist.confNow that https://gitlab.freedesktop.org/mesa/mesa/-/issues/3287 is resolved, we should be able to remove
```
piglit.spec.ext_packed_depth_stencil.fbo-clear-formats stencil
piglit.spec.arb_depth_buffer_float.fbo-clear-formats stencil
```Now that https://gitlab.freedesktop.org/mesa/mesa/-/issues/3287 is resolved, we should be able to remove
```
piglit.spec.ext_packed_depth_stencil.fbo-clear-formats stencil
piglit.spec.arb_depth_buffer_float.fbo-clear-formats stencil
```https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/47CI sends emails with the wrong link to reports2020-08-03T18:17:05ZRohan GargCI sends emails with the wrong link to reportsThe emails I get from CI seem to contain the incorrect URL :
```
Check console output at http://otc-mesa-ci.jf.intel.com/job/shadeslayer/3/ to view the results.
```
Could you please make jenkins report the right urls? Thanks!The emails I get from CI seem to contain the incorrect URL :
```
Check console output at http://otc-mesa-ci.jf.intel.com/job/shadeslayer/3/ to view the results.
```
Could you please make jenkins report the right urls? Thanks!https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/46Audit the mesa build configs to make sure none sets `-D platforms=drm,surface...2020-08-10T20:36:38ZEric Engestromeric@engestrom.chAudit the mesa build configs to make sure none sets `-D platforms=drm,surfaceless` (or only does so on old builds)Since mesa/mesa!3161 a few days ago, the `-D platforms` options `drm` & `surfaceless` are no longer necessary. They are still accepted but are no-ops that only generate a warning message. `surfaceless` is now always available, and `drm` ...Since mesa/mesa!3161 a few days ago, the `-D platforms` options `drm` & `surfaceless` are no longer necessary. They are still accepted but are no-ops that only generate a warning message. `surfaceless` is now always available, and `drm` is automatically enabled based on the `system_has_kms_drm` whitelist.
The following behaviour of the CI is needed:
- up to 20.2 (inclusive) and up to master at mesa/mesa@e00adef34a5ce485e2c9216a268ca05e89a5fc98, these two `-D platforms` values must be set when needed
- starting at that commit in master, and in 20.2+, there is no need to specify these in `-D platforms`
- in 20.3+, and in master starting mid/late august, if they are still passed it will be an error
https://gitlab.freedesktop.org/mesa/mesa/-/merge_requests/5844 will be gated on this issue being closed.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/45Enable Igalia remote repository2020-03-31T17:15:19ZJuan A. SuárezEnable Igalia remote repositoryCommit b5e38cfc256631bc2ea4 disabled Igalia remote repository, so we can't now test for regressions when pushing to our personal `<user>/jenkins` directory.
Can it be re-enabled again?Commit b5e38cfc256631bc2ea4 disabled Igalia remote repository, so we can't now test for regressions when pushing to our personal `<user>/jenkins` directory.
Can it be re-enabled again?https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/44intel-ci: icelake: pick kernel patch for gpu error state reporting2020-03-28T06:08:17ZD Scott Phillipsintel-ci: icelake: pick kernel patch for gpu error state reportingPlease pick this patch onto the current kernel used in the intel ci's icelake machines:
https://github.com/d-scott-phillips/linux/commit/3b512ab97758e3a11485012ed64645e2cbdbc46f
This will get request information back in gpu hang reports.Please pick this patch onto the current kernel used in the intel ci's icelake machines:
https://github.com/d-scott-phillips/linux/commit/3b512ab97758e3a11485012ed64645e2cbdbc46f
This will get request information back in gpu hang reports.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/42Re-enable Eric Anholt's Intel CI access2019-10-16T23:31:42ZKenneth Graunkekenneth@whitecape.orgRe-enable Eric Anholt's Intel CI accessPlease re-enable Eric's Intel CI access:
* Email: eric@anholt.net
* GitLab user: @anholt
* Repo: Please add him to https://gitlab.freedesktop.org/Mesa_CI/repos/mesa and give him a dev/anholt branch.
Please make sure his results appear ...Please re-enable Eric's Intel CI access:
* Email: eric@anholt.net
* GitLab user: @anholt
* Repo: Please add him to https://gitlab.freedesktop.org/Mesa_CI/repos/mesa and give him a dev/anholt branch.
Please make sure his results appear on the public website.
Thanks!https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/41icelake-only developer builds2019-09-17T20:36:26ZKenneth Graunkekenneth@whitecape.orgicelake-only developer buildsI could use the ability to test Icelake on developer builds. Ideally this would be added to normal developer builds, but that may not be possible yet. In the meantime, Clayton gave me the ability to test Icelake *only* via a developer ...I could use the ability to test Icelake on developer builds. Ideally this would be added to normal developer builds, but that may not be possible yet. In the meantime, Clayton gave me the ability to test Icelake *only* via a developer build by doing a custom build:
> \<craftyguy\> Kayden: do custom build, for 'build support' use sha e69a3a83a457fe7fa705e5943e9efeb100cfa37b, select 'all-test' project in drop down. you can leave everything else as default
>
> \<craftyguy\> Kayden: also beware that this will only test ICL, so if there are regressions in other platforms.. they won't be found in this build...
However, this broke within a few days. Now, if I submit a custom job with that build support sha, it doesn't even register a new job in the mesa_custom build list. It doesn't fail, it just silently does absolutely nothing as far as I can tell.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/40waffle has moved to gitlab.freedesktop.org2019-08-22T21:47:46ZDylan Bakerwaffle has moved to gitlab.freedesktop.orgAnd the github site is not being updated currently.And the github site is not being updated currently.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/39Make build options case insensitive2019-06-25T18:41:25ZSagar Ghugesagar.ghuge@intel.comMake build options case insensitiveIn revision field, make tokens case insensitive. For e.g both MESA and mesa should work.In revision field, make tokens case insensitive. For e.g both MESA and mesa should work.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/38Unblacklist more things on iris2019-06-25T17:46:05ZKenneth Graunkekenneth@whitecape.orgUnblacklist more things on irisLocally, [almost all CTS tests are passing on iris](http://whitecape.org/stuff/brw-iris-june/cts/problems.html), so hopefully we should be able to unblacklist the entire "flaky on iris" section. I fixed a whole bunch of transform feedba...Locally, [almost all CTS tests are passing on iris](http://whitecape.org/stuff/brw-iris-june/cts/problems.html), so hopefully we should be able to unblacklist the entire "flaky on iris" section. I fixed a whole bunch of transform feedback and copy image bugs recently. I'd say to use the i965 blacklist, but we actually pass `GTF-GL46.gtf32.GL3Tests.packed_pixels.packed_pixels*` as well, which i965 has blacklisted.https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/37Suspected intermittent issue: piglit.spec.arb_texture_barrier.arb_texture_bar...2023-11-08T20:44:14ZEmil VelikovSuspected intermittent issue: piglit.spec.arb_texture_barrier.arb_texture_barrier-blending-in-shader 512 42 8 64 7The run [A] shows the following failure
| Test Name | Hardware | Architecture | Status | Filtered Status | Time |
|-|-|-|-|-|-|
| piglit.spec.arb_texture_barrier.arb_texture_barrier-blending-in-shader 512 42 8 64 7 | kbl | m64 | fail | ...The run [A] shows the following failure
| Test Name | Hardware | Architecture | Status | Filtered Status | Time |
|-|-|-|-|-|-|
| piglit.spec.arb_texture_barrier.arb_texture_barrier-blending-in-shader 512 42 8 64 7 | kbl | m64 | fail | fail | 0.594619
Yet I cannot reproduce it locally, plus the next run [B] does not show that failure.
Note: here **are** changes to the mesa code across [A] and [B] `git diff --stat faf1e946a2b..18798a0a9b6` although they are unrelated. Feel free to investigate when you have some time.
[A] https://mesa-ci.01.org/wip_18_3/builds/25/group/63a9f0ea7bb98050796b649e85481845
[B] https://mesa-ci.01.org/wip_18_3/builds/26/group/63a9f0ea7bb98050796b649e85481845https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/36dEQP/CTS NotSupported tests are flagged as "failed"2019-02-06T02:41:40ZEmil VelikovdEQP/CTS NotSupported tests are flagged as "failed"Based on [1] and [2] seems that dEQP/CTS tests reporting `Not Supported` are flagged as `fail`.
Did I understand this correctly, what the reason behind this?
In piglit we use "skip" for similar cases and I think the CI has such a state....Based on [1] and [2] seems that dEQP/CTS tests reporting `Not Supported` are flagged as `fail`.
Did I understand this correctly, what the reason behind this?
In piglit we use "skip" for similar cases and I think the CI has such a state.
Thanks
[1] https://mesa-ci.01.org/wip_18_3/builds/23/results/2940440
[2] https://github.com/KhronosGroup/VK-GL-CTS/blob/master/external/vulkancts/modules/vulkan/wsi/vktWsiDisplayTests.cpp#L2089https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/35Missing information about generated tests2019-02-14T16:25:46ZEmil VelikovMissing information about generated testsAs mentioned in #34 there is no obvious link/reference to the actual code (be that generator or generated) for `generated.` tests.
For example [1] lists only the following, thus trying to understand what's happening or reproduce is impo...As mentioned in #34 there is no obvious link/reference to the actual code (be that generator or generated) for `generated.` tests.
For example [1] lists only the following, thus trying to understand what's happening or reproduce is impossible :-(
```
2019-01-29T12:22:23,110938-0800 i915_gem_userptr_mn_invalidate_range_start+0x167/0x190 [i915]
```
[1] https://mesa-ci.01.org/wip_18_3/builds/23/results/1601927https://gitlab.freedesktop.org/Mesa_CI/mesa_jenkins/-/issues/3418.3: passing invalid arguments to the meson generated test2019-03-22T15:30:44ZEmil Velikov18.3: passing invalid arguments to the meson generated testIn `master` branch the `pl111` driver got renamed to `kmsro` but not in `18.3`. Yet the generated tests use `kmsro`.
Causing a failure like the following:
https://mesa-ci.01.org/wip_18_3/builds/23/results/1534585
Mildly related: where'...In `master` branch the `pl111` driver got renamed to `kmsro` but not in `18.3`. Yet the generated tests use `kmsro`.
Causing a failure like the following:
https://mesa-ci.01.org/wip_18_3/builds/23/results/1534585
Mildly related: where's the code that generates those, can we have a link to that from the failing tests?