-
Notifications
You must be signed in to change notification settings - Fork 15.6k
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
Comments
Sorry, this is not enough detail to be actionable. Please provide more details if you're still seeing problems. |
Having the same issue while installing protobuf ` This is the log output at the end |
Having the same issue. pi@pi4:/opt/protobuf-3.14.0 $ gcc --version on protobuf-3.14.0 RUN ] IoTest.LargeOutput =============== 1 FAILED TEST |
I had the same error ..... |
@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 ? |
This tests also fails on Khadas VIM3. It has 4GB RAM |
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
The text was updated successfully, but these errors were encountered: