[jira] [Commented] (REEF-314) Test REEF.NET in VS 2015

["Markus Weimer (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/REEF-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14708145#comment-14708145 ] 

Markus Weimer commented on REEF-314:
------------------------------------

I just did some more testing using Visual Studio 2015 on Windows 10. The machine only has Visual Studio 2015 installed, nothing else.

The *good* news: Importing the project into Visual Studio 2015 worked fine. I allowed it to convert our C++ project to the new version. Building from the command line works just fine using those converted build files.

The *bad* news is that the situation seems to have gotten worse since I last checked for building within VS 2015. On first build, I got similar errors to the above about our client DLL not availabe when building IMRU. Sorry, I did not copy the error and now can't reproduce it anymore. After a clean, I now get 1294 error messages about namespaces in dependencies not being available. This makes me believe that NuGet is broken for us in VS 2015. Oddly, it works from the command line.

Now, on to the *weird* news: I can actually run most of the tests (452 to be precise) when I build from the command line and then go to VS to test it. The build before the tests fails, but VS then offers to run tests using the last successful build, which in this case is the command line build. The remaining 4 tests all fail with the same message:

{noformat}
Test Name:	CanInjectAndExecuteTask
Test FullName:	Org.Apache.REEF.Evaluator.Tests.EvaluatorTests.CanInjectAndExecuteTask
Test Source:	D:\src\reef\lang\cs\Org.Apache.REEF.Evaluator.Tests\EvaluatorTests.cs : line 44
Test Outcome:	Failed
Test Duration:	0:00:00.0370995

Result StackTrace:	
at Microsoft.Hadoop.Avro.Container.StreamReader`1.MoveNext()
   at Microsoft.Hadoop.Avro.Container.SequentialReader`1.<get_Objects>d__0.MoveNext()
   at System.Linq.Enumerable.First[TSource](IEnumerable`1 source)
   at Org.Apache.REEF.Tang.Formats.AvroConfigurationSerializer.AvroDeseriaizeFromFile(String fileName) in D:\src\reef\lang\cs\Org.Apache.REEF.Tang\Formats\AvroConfigurationSerializer.cs:line 182
 --- End of inner exception stack trace ---
    at Org.Apache.REEF.Utilities.Diagnostics.Exceptions.Throw(Exception exception, String message, Logger logger) in D:\src\reef\lang\cs\Org.Apache.REEF.Utilities\Diagnostics\Exceptions.cs:line 54
   at Org.Apache.REEF.Tang.Formats.AvroConfigurationSerializer.AvroDeseriaizeFromFile(String fileName) in D:\src\reef\lang\cs\Org.Apache.REEF.Tang\Formats\AvroConfigurationSerializer.cs:line 191
   at Org.Apache.REEF.Evaluator.Tests.EvaluatorTests.CanInjectAndExecuteTask() in D:\src\reef\lang\cs\Org.Apache.REEF.Evaluator.Tests\EvaluatorTests.cs:line 51
Result Message:	
Test method Org.Apache.REEF.Evaluator.Tests.EvaluatorTests.CanInjectAndExecuteTask threw exception: 
System.ApplicationException: Cannot deserialize the file: evaluator.conf ---> System.Runtime.Serialization.SerializationException: Synchronization marker defined in the header does not match the read one.
{noformat}

Why would we get a warning from {{System.Runtime.Serialization}}? I thought we always used Avro?

> Test REEF.NET in VS 2015
> ------------------------
>
>                 Key: REEF-314
>                 URL: https://issues.apache.org/jira/browse/REEF-314
>             Project: REEF
>          Issue Type: Sub-task
>          Components: REEF.NET
>            Reporter: Markus Weimer
>            Assignee: Markus Weimer
>            Priority: Minor
>
> I'm installing the RC and will give it a go.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)