20.09.2018 07:16, Neia Neutuladh пишет:
> On Thursday, 20 September 2018 at 02:51:52 UTC, Neia Neutuladh wrote:
>> On Monday, 10 September 2018 at 01:27:20 UTC, Neia Neutuladh wrote:
>>> Not on dlang.org anywhere, but I built a crude version of this. Results are available at http://ikeran.org/report/.
>>
>> A quick status update:
> 
> And source code is available at https://git.ikeran.org/dhasenan/dubautotester
> 
> Please don't judge me.

Autotester should show build logs because for example `nanogui` package reported as failed although it builds on my machines successfully.

On Thursday, 20 September 2018 at 06:41:54 UTC, drug wrote:
> Autotester should show build logs because for example `nanogui` package reported as failed although it builds on my machines successfully.

This is because the D project tester (i assume this is what you call autotester) uses optionally a custom script, i believe. Same problem for "iz". It's ok in the autotester but not in the dubautotester. Fortunately this one can be fixed, it's just a problem with "warningAsError".

I agree for the logs. This could help authors.

On Monday, 10 September 2018 at 12:16:03 UTC, Adam D. Ruppe wrote:
> On Sunday, 9 September 2018 at 14:28:11 UTC, Guillaume Piolat wrote:
>> I don't manage to find x-module search again, perhaps disabled.
>
> Yeah, there's a memory leak in it so leaving it up would kill the box to build actual docs. And the last couple months have been crazy IRL, but I scheduled some time this week to work on the code again (last week, pushed up a new parser with the uda on params support, etc btw).
>
> I think my solution is going to be to dump the search index in a rdbms and let it manage the memory lol (though it is an immutable binary tree, why it leaks is kinda beyond me, probably just sloppy code somewhere like "foo" ~ desc).

Perhaps -profile=gc can tell
Webfreak made a "symbol search" program which looks similar?

On Thursday, 20 September 2018 at 06:41:54 UTC, drug wrote:
> Autotester should show build logs because for example `nanogui` package reported as failed although it builds on my machines successfully.

The tester is now submodule-aware and I removed builds for packages with a `.gitmodules` file.

I'm adding logs only for failed builds. This is an annoying amount of UI work that I might well have messed up horribly.

On Thursday, 20 September 2018 at 17:06:43 UTC, Neia Neutuladh wrote:
> The tester is now submodule-aware and I removed builds for packages with a `.gitmodules` file.

I'm not sure whether this is actually a good idea. There are some projects that support both, DUB and submodules+makefile. Those would (unnecessarily) get excluded.

On Friday, 21 September 2018 at 20:49:54 UTC, 0xEAB wrote:
> On Thursday, 20 September 2018 at 17:06:43 UTC, Neia Neutuladh wrote:
>> The tester is now submodule-aware and I removed builds for packages with a `.gitmodules` file.
>
> I'm not sure whether this is actually a good idea. There are some projects that support both, DUB and submodules+makefile. Those would (unnecessarily) get excluded.

I meant that I removed the past builds for things with git submodules so that they could be rebuilt.

Stderr is captured now, but I believe I messed up the UI for it. C'est la vie.

On Friday, 21 September 2018 at 22:26:11 UTC, Neia Neutuladh wrote:
> On Friday, 21 September 2018 at 20:49:54 UTC, 0xEAB wrote:
>> On Thursday, 20 September 2018 at 17:06:43 UTC, Neia Neutuladh wrote:
>>> The tester is now submodule-aware and I removed builds for packages with a `.gitmodules` file.
>>
>> I'm not sure whether this is actually a good idea. There are some projects that support both, DUB and submodules+makefile. Those would (unnecessarily) get excluded.
>
> I meant that I removed the past builds for things with git submodules so that they could be rebuilt.
>
> Stderr is captured now, but I believe I messed up the UI for it. C'est la vie.

The "tests" check doesn't seem to work properly for DMD <= v2.072.0.

If one looks at the reports[0] for those compilers, one will that pretty everything failed.
For example, `discord-rpc`[1] doesn't even have any unittests.


[0] http://ikeran.org/report/compiler/dmd2.072.0.html
[1] http://ikeran.org/report/package/discord-rpc.html

On 10/06/2018 01:38 AM, 0xEAB wrote:
> The "tests" check doesn't seem to work properly for DMD <= v2.072.0.
> 
> If one looks at the reports[0] for those compilers, one will that pretty everything failed.
> For example, `discord-rpc`[1] doesn't even have any unittests.

I'm clearing out those build results so we'll rerun them. This should get proper error reports as well (they're working at last!).

I've also moved the project to proper hosting, which should slow it down even more but provide better security.