OutOfMemoryException is thrown when building from script

[UdiBen]

Hello,
I get OutOfMemoryException when building from build.bat:
After the build succeeded, this exception is thrown:

Running build failed.
Error:
System.OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.
   at System.Collections.Generic.List`1.set_Capacity(Int32 value)
   at System.Collections.Generic.List`1.EnsureCapacity(Int32 min)
   at System.Collections.Generic.List`1.Add(T item)
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at FSI_0001.InheritDoc.nodesReplace@21.Invoke(Tuple`2 tupledArg) in C:\dev\elasticsearch-net\build\InheritDoc.fsx:line 22
   at Microsoft.FSharp.Collections.SeqModule.Iterate[T](FSharpFunc`2 action, IEnumerable`1 source)
   at FSI_0001.InheritDoc.PatchXmlDoc(String file) in C:\dev\elasticsearch-net\build\InheritDoc.fsx:line 20
   at FSI_0002.clo@43-7.Invoke(String f) in C:\dev\elasticsearch-net\build\build.fsx:line 43
   at Microsoft.FSharp.Collections.SeqModule.Iterate[T](FSharpFunc`2 action, IEnumerable`1 source)
   at FSI_0002.clo@22-2.Invoke(Unit _arg3) in C:\dev\elasticsearch-net\build\build.fsx:line 43
   at Fake.TargetHelper.runTarget@310(String targetName)
Killing all processes that are created by FAKE and are still running.
-------------------------------------------------------------------
Target               Duration
------               --------
Clean                00:00:00.0014153
CreateKeysIfAbsent   00:00:00.0003199
Version              00:00:00.1364023
Total:               00:00:39.5886862
Status:              Failure
-------------------------------------------------------------------

Am I missing some setup?

Build Time Report

[Mpdreamz]

There is a task in there that tries to patch the XML docfiles to suport <inheritdoc /> it does so in a horribly inefficient way:

https://github.com/elasticsearch/elasticsearch-net/blob/master/build/InheritDoc.fsx

Which works on my 16GB machine :)

I might make this step only part of the release build procedure or come up with a less resource intensive way to do this.

For now you commenting this line:

https://github.com/elasticsearch/elasticsearch-net/blob/master/build/build.fsx#L43

Should fix the OOM in the build script. Mind confirming this for me?

[UdiBen]

Yep. That fixed the OOM. Thanks!
However, the build still fails because of failing NUnit tests (in general there are ~200 failing tests)

[Mpdreamz]

Just ran to confirm myself and only saw 3 failing tests.

Mind pulling the latest and rerun? If you still have failing tests mind gist'ing the console output ?

If that many tests are failing the only cause i can think of is that they can't find the json files in the bin output.

[UdiBen]

Thanks @Mpdreamz - the build does finish successfully now.
The failing tests are only when I run it manually from visual studio. I guess I'm missing something. Should it be straightforward, or there is any setup required?

[Mpdreamz]

I would not know to be honest, I use ncrunch to run my tests and sometimes the resharper test runner if I want to profile a unit test with dotTrace, both work for me.

Are you using the build in test runner? It might do something to the bin path so that it can't find the json files.

[UdiBen]

I'm running the tests with resharper runner. Against elastic server 1.1.1
I have 248 failing tests. For example:
GetTests.SimpleMultiGet fails (I started testing it after the same scenario failed in my application):
The test reproduce POST to

localhost:9200/_mget
{
  "docs": [
    {
      "_index": "nest_test_data-17036",
      "_type": "elasticsearchprojects",
      "_id": "4"
    },
    {
      "_index": "nest_test_data-17036",
      "_type": "elasticsearchprojects",
      "_id": "5"
    }
  ]
}

There is a problem with deserializing the response - it is deserialized as empty MultiGetResponse (same goes for many other tests). Any idea?