Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Failed protobuf-test(exit status: 1) #7962

Closed
junlinliu1 opened this issue Oct 13, 2020 · 6 comments
Closed

Failed protobuf-test(exit status: 1) #7962

junlinliu1 opened this issue Oct 13, 2020 · 6 comments

Comments

@junlinliu1
Copy link

When I try the make check, it says that the protobuf-test fail one.
And in the test-suite log:
it says: Failed: IoTest.LargeOutput

@perezd
Copy link
Contributor

perezd commented Oct 22, 2020

Sorry, this is not enough detail to be actionable. Please provide more details if you're still seeing problems.

@perezd perezd closed this as completed Oct 22, 2020
@xavierallem
Copy link

xavierallem commented Nov 9, 2020

Having the same issue while installing protobuf

git_hubproto

`

This is the log output at the end

test-suite.log

@Guiraud
Copy link

Guiraud commented Dec 23, 2020

Having the same issue.
Uname -a :
Linux pi4 5.4.79-v7l+ #1373 SMP Mon Nov 23 13:27:40 GMT 2020 armv7l GNU/Linux

pi@pi4:/opt/protobuf-3.14.0 $ gcc --version
gcc (Raspbian 8.3.0-6+rpi1) 8.3.0

on protobuf-3.14.0

RUN ] IoTest.LargeOutput
unknown file: Failure
C++ exception with description "std::bad_alloc" thrown in the test body.
[ FAILED ] IoTest.LargeOutput (5033 ms)

===============
[----------] Global test environment tear-down
[==========] 2174 tests from 198 test suites ran. (88557 ms total)
[ PASSED ] 2173 tests.
[ FAILED ] 1 test, listed below:
[ FAILED ] IoTest.LargeOutput

1 FAILED TEST
FAIL protobuf-test (exit status: 1)

test-suite.log

@JoaoHenriqueOliveira
Copy link

I had the same error .....

@bullekeup
Copy link

@perezd : I have more info concerning this issue, if you can look at it.

As mentioned before, the protobuf-test check failed for the IoTest.LargeOutput test.

From what I understood looking at the source, the IoTest.LargeOutput test declared in src/google/protobuf/io/zero_copy_stream_unittest.cc line 716 tries to increase buffer size to kint32max (a little bit more than 2GB). This is more than usually available as contiguous memory on RPis and similar hardware (I suppose the StringOutputStream uses contiguous memory, correct me if that's wrong).

I just had the issue on a Jetson Nano (4GB of RAM), when starting the check, memory usage grows from 1.4 GB to around 3.5 - 3.9 GB and the test fails with no swap space used (4GB swap available).

If it just indicates that we won't be able to process huge buffers at once (but on theses constrained platforms we probably don't want / need to anyway), this fail may be ignored without much risk ?

@erlingrj
Copy link

This tests also fails on Khadas VIM3.
uname - a
Linux Khadas 4.9.224 #29 SMP PREEMPT Sat May 30 14:20:51 CST 2020 aarch64 aarch64 aarch64 GNU/Linux

It has 4GB RAM

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants