Closed sanchayanghosh closed 1 year ago
Here is the success log, after making the changes -
1680429205.910746370: src/main/tools/linux-sandbox-pid1.cc:556: child exited normally with code 0
1680429205.910955021: src/main/tools/linux-sandbox.cc:233: child exited normally with code 0
Target //python:protobuf_python up-to-date (nothing to build)
INFO: Elapsed time: 32.073s, Critical Path: 20.73s
INFO: 388 processes: 61 internal, 327 linux-sandbox.
INFO: Build completed successfully, 388 total actions
[bob@bob-systemproductname protobuf]$
Please find the full log success_log.log
This was fixed in b9e056f779f1c6cbf07a7a11be6f5ee6a4d433b8.
What version of protobuf and what language are you using? Version: main/v3.6.0/v3.5.0 etc. (NOTE: please try updating to the latest version of protoc/runtime possible beforehand to attempt to resolve your problem) Language: C++/Java/Python/C#/Ruby/PHP/Objective-C/Javascript
What operating system (Linux, Windows, ...) and version?
Manjaro here has been given a full system update as of yesterday
What runtime / compiler are you using (e.g., python version or gcc version)
What did you do? Steps to reproduce the behavior:
(The entire log is attached here
What did you expect to see
Build completed successfully without errors.
What did you see instead?
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
Anything else we should know about your project / environment
Triaging the issue
In the file, protobuf/src/google/protobuf/map.h
Here, when we allow integer sanitization, and provide a return type of uint64_t, the build succeeds.