Could you print the detailed failure log, as well as the autoconf, automake, libtools and gcc version? I tested on the latest mingw before alpha-2 release and didn't find any failing tests.

Hi ,
Am also getting error during step
make check

Steps followed:
Installing "protobuf-cpp-3.0.0-alpha-2.tar.gz" on ubuntu. 3.16.0-23-generic #31

1. tar xzvf protobuf-cpp-3.0.0-alpha-2.tar.gz
2. cd protobuf-3.0.0-alpha-2
3. ./configure
4. make
5. make check

In test-suit.log file i can see this error first.
[libprotobuf FATAL google/protobuf/compiler/ruby/ruby_generator_unittest.cc:53] Could not find Ruby test directory. Please run tests from somewhere within the protobuf source package.
unknown file: Failure
C++ exception with description "Could not find Ruby test directory. Please run tests from somewhere within the protobuf source package." thrown in the test body.
[ FAILED ] RubyGeneratorTest.GeneratorTest (388 ms)

can any one help to resolve this???

gRPC is prompting to install protobuf 3.0 as prerequisite so am trying to install this package.

because of this am stuck for gRPC.

Thanks in advance.
Harsha

Add @cfallin to take a look at the failing ruby tests.

All tests passed on Windows when we did the release testing, sorry. It's not possible to say any more about the cause without seeing your exact setup.

However, it seems that all four failing tests are ones that compare output to a golden file in the source tree. So perhaps there is something systematically wrong with the way your source tree is laid out, or with how your build is interacting with the filesystem?

Apologies for delay in response to this. I would imagine my source tree layout is fairly default - I just checkout and go without any messing around, but please do let me know if there is anything specific in mingw that you'd like me to check (I am more of a Java guy so all this stuff is alien to me - apologies!).

At least some of the errors are windows vs unix line endings (\n vs \r\n) - BootstrapTest.GeneratedDescriptorMatches however is not so clear

Requested version details, steps to checkout used, and output from autogen, configure, make and make check are in this gist
https://gist.github.com/matt1/4e6257f3a8a418389b35

Ah! I'm pretty sure I know what the issue is. Consider this failure from TextFormatTest:

google/protobuf/text_format_unittest.cc:121: Failure
Value of: proto_.DebugString()
  Actual: "optional_int32: 101\noptional_int64: 102\n..."
Expected: proto_debug_string_
Which is: "optional_int32: 101\r\noptional_int64: 102\r\n..."

Note the difference in line endings: \n vs. \r\n. As I suspected, this happens in every test that compares against a golden file, and your golden files have Windows-style line endings, so the contents do not match (the code generates only \n).

The answer is to change the text format that git uses to check out your tree. I believe the core.autocrlf git option controls this behavior. You'll probably want to change it globally then check out a fresh clone of protobuf.

Ah thanks - I learnt something about git today!

All tests passing. If anyone else finds the same problem, check what your core.autocrlf is. Mine was set to true and was converting the unix line endings in the tests to windows formats automatically when writing the files to the local workspace.

Set this to false with something like git config --global core.autocrlf false, clone again from scratch and build and the tests pass fine this time (since git is no longer fiddling with the line endings behind the scenes).