<div dir="ltr">Hello,<div><br></div><div style>OK, I've pushed my change again, please let me know if you notice any more problems.</div><div style><br></div><div style>The `ghcpkg01` test runs fine if I run it on its own: make CLEANUP=1 TEST=ghcpkg01 fast</div>
<div style><br></div><div style>I rerun validate (uinsg: CPUS=8 ./validate) and I got a different cabal related failure:</div><div style><br></div><div style> Unexpected failures:</div><div> cabal shadow [bad stderr] (normal)</div>
<div><br></div><div style>Again, it passes when I run it on its own:</div><div style>make CLEANUP=1 TEST="cabal shadow" fast<br></div><div style><br></div><div style>So it seems that there is something that keeps changing... I wonder if it might be some missing dependency, so when you run things in parallel sometimes they fail?</div>
<div style><br></div><div style>-Iavor</div><div style><br></div><div><br></div><div style><br></div><div style><br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, May 31, 2013 at 8:22 AM, Ian Lynagh <span dir="ltr"><<a href="mailto:ian@well-typed.com" target="_blank">ian@well-typed.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><br>
Hi Iavor,<br>
<div class="im"><br>
On Thu, May 30, 2013 at 07:59:07PM -0700, Iavor Diatchki wrote:<br>
><br>
> I don't think that these are related to my change, but I don't really know,<br>
> so I am not going to push the fix just yet. Could you please advice on how<br>
> to investigate further?<br>
<br>
</div>For ghcpkg01, if you have a testlog from a validate run then you can<br>
search for the test in that. Otherwise you can do<br>
cd testsuite/tests<br>
make CLEANUP=1 TEST=ghcpkg01 fast<br>
if you were doing a --fast validate, or<br>
cd testsuite/tests<br>
make CLEANUP=1 TEST=ghcpkg01 fast BINDIST=YES<br>
for a normal valdiate, and see how it's failing.<br>
<div class="im"><br>
> PS: Is there some sort of a flag I could set in <a href="http://build.mk" target="_blank">build.mk</a> so that it always<br>
> builds with warnings and core lint? In some of my GHC trees this seems to<br>
> happen, and in others it does not, and for me it'd be quite helpful if it<br>
> always did.<br>
<br>
</div>You can see what settings validate uses in mk/<a href="http://validate-settings.mk" target="_blank">validate-settings.mk</a>, and<br>
copy any that you want into mk/<a href="http://build.mk" target="_blank">build.mk</a>.<br>
<br>
In particular, these add lint flags:<br>
GhcStage2HcOpts += -O -dcore-lint<br>
GhcLibHcOpts += -O -dcore-lint<br>
<br>
<br>
Thanks<br>
<span class="HOEnZb"><font color="#888888">Ian<br>
--<br>
Ian Lynagh, Haskell Consultant<br>
Well-Typed LLP, <a href="http://www.well-typed.com/" target="_blank">http://www.well-typed.com/</a><br>
</font></span></blockquote></div><br></div>