<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - autotools build test broken"
href="https://bugs.freedesktop.org/show_bug.cgi?id=105628">105628</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>autotools build test broken
</td>
</tr>
<tr>
<th>Product</th>
<td>Mesa
</td>
</tr>
<tr>
<th>Version</th>
<td>git
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Keywords</th>
<td>bisected, regression
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>Drivers/DRI/i965
</td>
</tr>
<tr>
<th>Assignee</th>
<td>t_arceri@yahoo.com.au
</td>
</tr>
<tr>
<th>Reporter</th>
<td>mark.a.janes@intel.com
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-3d-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>baker.dylan.c@gmail.com
</td>
</tr></table>
<p>
<div>
<pre>Building out of tree with the following flags:
configure --enable-gbm --enable-llvm --with-egl-platforms=x11,drm
--enable-glx-tls --enable-gles1 --enable-gles2
--with-gallium-drivers=svga,swrast,r300,r600,radeonsi,nouveau
--with-vulkan-drivers=intel,radeon --enable-debug
src/mesa/state_tracker/st_nir_lower_uniforms_to_ubo.c:32:10: fatal error:
nir.h: No such file or directory
#include "nir.h"
^~~~~~~
compilation terminated.
Makefile:3036: recipe for target
'state_tracker/st_nir_lower_uniforms_to_ubo.lo' failed
Bisected to series ending in:
632d5e97efa st/radeonsi: enable uniform packing in NIR backend
This showed up in the developer's CI build, but due to shortcomings of the
Intel CI, the notification would not have been usable by Tim. This bug is an
example of why Intel Mesa CI needs to invest in fully exposing CI results to
external developers.
This build is compiled with -j18, which may expose race conditions in
generating code.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>