<div dir="ltr">Compilation logs are available on the buildbot (e.g. <a href="https://build.macports.org/one_line_per_build">https://build.macports.org/one_line_per_build</a>). However, the logs are for compilation with the default compilers. Very few ports would be using gcc46 or gcc47, since the default is clang.<div><br></div><div>No, there are no logs of tests run, because they are not run automatically -- but they should not have anything to do with the compilation failures in that ticket; if compilation fails, it is not possible to run tests anyway.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Wed, Oct 28, 2015 at 8:38 PM, Jeffrey Walton <span dir="ltr"><<a href="mailto:noloader@gmail.com" target="_blank">noloader@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span class="">On Wed, Oct 28, 2015 at 8:01 PM, David Strubbe <<a href="mailto:dstrubbe@macports.org">dstrubbe@macports.org</a>> wrote:<br>
> What kind of test/QA results are you talking about?<br>
<br>
</span>I'm looking for (1) compile results, and (2) the results of running<br>
the self tests if a package provides them. For example, OpenSSL<br>
provides a `make check`; while Crypto++ provides `make test`.<br>
<br>
> Whose issue 37664?<br>
<br>
<a href="http://trac.macports.org/ticket/37664" rel="noreferrer" target="_blank">http://trac.macports.org/ticket/37664</a><br>
<br>
Thanks again.<br>
<span class="im HOEnZb"><br>
> On Wed, Oct 28, 2015 at 6:55 PM, Jeffrey Walton <<a href="mailto:noloader@gmail.com">noloader@gmail.com</a>> wrote:<br>
</span><div class="HOEnZb"><div class="h5">>> ...<br>
>> I am trying to gather statistics and telemetry. I'm interested in the<br>
>> results of compiling the ports collection under the GCC compilers<br>
>> MacPorts supplies to users, and the intersection with Issue 37664.<br>
>><br>
>> Does MacPorts provide its Test/QA results online? If so, then where are<br>
>> they?<br>
</div></div></blockquote></div><br></div>