<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
<p>Hi Matthias,</p>
<p>Let me see if I get this correct. You got a build failure, and
the built-in system could not diagnose it. Instead, it suggested
that you should search the build log for <span lang="en-DE"> ']
Error'. Instead, of doing this, you scrolled through the entire
log, just to find that the actual error message was printed
close to </span><span lang="en-DE"></span><span lang="en-DE">
'] Error'..?</span></p>
<p><span lang="en-DE">What exactly are we to do about this?</span></p>
<p><span lang="en-DE">The reason we do not extract this information
to the build failure summary is that it is not possible (or, if
possible, extremely non-trivial). Instead, we direct the user on
how to best go ahead to try and find this information
themselves. Fixing users not reading or following suggestions is
unfortunately out of scope for the build system. ;-)</span></p>
<p><span lang="en-DE">There is no point in trying to search for this
particular error and repeat it to the user. The "</span><span lang="en-DE">No indication of failed target found. </span><span lang="en-DE">Try searching the build log for '] Error'." is our
generic fallback when we have no way to determine the cause of
failure. There are a myriad ways of the build to fail in that
case, if we start adding special cases to this, there will be no
end.</span></p>
<p><span lang="en-DE">/Magnus<br>
</span></p>
<div class="moz-cite-prefix"><br>
</div>
<div class="moz-cite-prefix">On 2023-09-08 13:19, Baesken, Matthias
wrote:<br>
</div>
<blockquote type="cite" cite="mid:PA4PR02MB6781FA12A4431C91D386345A93EDA@PA4PR02MB6781.eurprd02.prod.outlook.com">
<meta name="Generator" content="Microsoft Word 15 (filtered medium)">
<style>@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0cm;
font-size:11.0pt;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}span.EmailStyle17
{mso-style-type:personal-compose;
font-family:"Calibri",sans-serif;
color:windowtext;}.MsoChpDefault
{mso-style-type:export-only;
font-family:"Calibri",sans-serif;
mso-fareast-language:EN-US;}div.WordSection1
{page:WordSection1;}</style><!--[if gte mso 9]><xml>
<o:shapedefaults v:ext="edit" spidmax="1026" />
</xml><![endif]--><!--[if gte mso 9]><xml>
<o:shapelayout v:ext="edit">
<o:idmap v:ext="edit" data="1" />
</o:shapelayout></xml><![endif]-->
<div class="WordSection1">
<p class="MsoNormal"><span lang="EN-US">Hello, <o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">A Windows build failed
because of some temp</span><span lang="EN-US">orary
</span><span lang="en-DE"> "Perm</span><span lang="EN-US">i</span><span lang="en-DE">ssion denied" issue we see sometimes on
Windows.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Unfortunately at the end
of the log not much info is found, the error is not reported
there .<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">.....<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">if /usr/bin/grep -q
"recipe for target .* failed" .......<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">No indication of failed
target found.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">HELP: Try searching the
build log for '] Error'.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">printf "HELP: Run 'make
doctor' to diagnose build problems.\n\n"<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">HELP: Run 'make doctor'
to diagnose build problems.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">After a lot of
scrolling through the endless build log, I found
</span><span lang="EN-US">in the middle of the build.log</span><span lang="en-DE">:<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="en-DE">make[3]: /usr/bin/bash: Permission denied<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="en-DE">make[3]: *** [Lib.gmk:62:
/cygdrive/C/Windows_x64/jdk-build-fastdebug/support/native/jdk.jpackage/jpackageapplauncher/MsiDb.obj]
Error 127<o:p></o:p></span></p>
<p class="MsoNormal" style="margin-left:36.0pt"><span lang="en-DE">make[3]: *** Waiting for unfinished jobs....<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">which probably cause</span><span lang="EN-US">d</span><span lang="en-DE"> the error.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">Could we maybe add a
grep for "bash: Permission denied" or for the recommended
</span><span lang="EN-US"> </span><span lang="en-DE">"] Error
" at the end of the
</span><span lang="EN-US">build </span><span lang="en-DE">log
?<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE">At least the grep/search
for "] Error " finds the issue pretty fast and looks like
a good erro</span><span lang="EN-US">r</span><span lang="en-DE"> reporting addition in this case.<o:p></o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="en-DE"><o:p> </o:p></span></p>
<p class="MsoNormal"><span lang="EN-US">Best regards, Matthias<o:p></o:p></span></p>
</div>
</blockquote>
</body>
</html>