Chiebot-Mirror/protobuf - protobuf - Gitea: Git with a cup of tea

Author	SHA1	Message	Date
Mike Kruskal	d938afd6e3	Add sanitized builds to Kokoro (#10706 ) * Adding build configs for sanitization * Update bazel runner to accept configs to loop over * Fix Bazel query from to googletest upgrade * Fix pre-existing ODR violation * Clean up bazel configs * Fix UBSAN issues in tests * Upgrade zlib to pull in UBSAN fix * Fix conformance test UB * Add san builds to Bazel tests Add dbg to san builds Extend timeout for Bazel build * Enable ODR checks again by using static linkage in ASAN * Cleanup kokoro setup * Disable MSAN for now * Enable MSAN in kokoro build * Fix msan failure * Remove broken bazel clean * Cleanup * Fix false leaks * Fix cap-add argument * Fix asan config name * Remove LSAN verbosity * Expand size of big test, add verbose failures * Skip slow test in TSAN * Workaround for bazel issue with ubsan	2 years ago
Mike Kruskal	d220b43c6c	Enable warnings as errors during tests (#10482 ) * Enable warnings as errors by default for test builds * Fixing C++ warnings * Adding host flags, and enabling warnings as error for non-C++ too * Switch to BUILD copts instead of bazelrc to treat Windows as a snowflake * Disable warnings as errors on Windows, since it doesn't like the c++14 flag	2 years ago
Mike Kruskal	a3c8e2deb0	Integrate from Piper for C++, Java, and Python (#10455 ) * Sync from Piper @469587494 PROTOBUF_SYNC_PIPER * Fixing github SOT protoc builds * Fixing typos from google * Remove leaked util/hash reference * Fixing bad python merge * Fixing python C++ library order	2 years ago
Adam Cozzette	7df94e2473	Upgrade third_party/googletest submodule to current main branch (#10393 ) * Upgrade third_party/googletest submodule to current main branch We can finally do this upgrade now that we have dropped our autotools build. Googletest recommends living at head, so let's go straight to the most recent commit on main. For some reason the googletest archive is not present in the Bazel build mirror, so I removed that entry and just left the GitHub download link in our WORKSPACE file. Googletest now requires C++14, so I updated all the C++11 flags I could find to C++14 instead. I added a .bazelrc file to add -std=c++14 for all our Bazel builds. * Delete the empty //src/google/protobuf:protobuf_test target * Avoid building C++ unit tests in aarch64 jobs for Python and Ruby	2 years ago
Adam Cozzette	500cbd7b90	Upgrade third_party/googletest submodule to current main branch (#10393 ) * Upgrade third_party/googletest submodule to current main branch We can finally do this upgrade now that we have dropped our autotools build. Googletest recommends living at head, so let's go straight to the most recent commit on main. For some reason the googletest archive is not present in the Bazel build mirror, so I removed that entry and just left the GitHub download link in our WORKSPACE file. Googletest now requires C++14, so I updated all the C++11 flags I could find to C++14 instead. I added a .bazelrc file to add -std=c++14 for all our Bazel builds. * Delete the empty //src/google/protobuf:protobuf_test target * Avoid building C++ unit tests in aarch64 jobs for Python and Ruby	2 years ago
Adam Cozzette	98b6ead775	Remove .bazelrc file containing the -std=c++11 flag (#8874 ) MSVC warns about that flag since it's not in the format it expects, and the flag seems to be unnecessary anyway.	3 years ago
Adam Cozzette	0554bb24c0	Add a top-level .bazelrc to make sure we use C++11	3 years ago