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

Author	SHA1	Message	Date
Mike Kruskal	ed5c57a574	Remove all autotools usage (#10132 ) * Bazelfying conformance tests Adding infrastructure to "Bazelify" languages other than Java and C++ * Delete benchmarks for languages supported by other repositories * Bazelfying benchmark tests * Bazelfying python Use upb's system python rule instead of branching tensorflow * Bazelfying Ruby * Bazelfying C# * Bazelfying Objective-c * Bazelfying Kokoro mac builds * Bazelfying Kokoro linux builds * Deleting all deprecated files from autotools cleanup This boils down to Makefile.am and tests.sh and all of their remaining references * Cleanup after PR reorganizing - Enable 32 bit tests - Move conformance tests back - Use select statements to select alternate runtimes - Add internal prefixes to proto library macros * Updating READMEs to use bazel instead of autotools. * Bazelfying Kokoro release builds * First round of review fixes * Second round of review fixes * Third round of review fixes * Filtering out conformance tests from Bazel on Windows (b/241484899) * Add version metadata that was previously scraped from configure.ac * fixing typo from previous fix * Adding ruby version tests * Bumping pinned upb version, and adding tests to python CI	2 years ago
Joshua Haberman	de371235c9	Sync from Piper @338284531 PROTOBUF_SYNC_PIPER	4 years ago
David L. Jones	b774da0d42	Change Python kokoro configs to test only their specified version. (#7927 ) Using non-versioned scripts for `build_file` means every Python version is tested (under Tox), and this is multiplied by each Python version running Tox. For example, when the `python38` config is used to run Tox, the Tox layer runs on Python 3.8. This then tests all of the Python versions individually, including, for example, python27 tests. This change fixes the `build_file` paths to point to the same-pathed build script. For example, `kokoro/linux/python27/presubmit.cfg` now uses `kokoro/linux/python27/build.sh`. Some additional fixes: * Use `python -m tox` in tests.sh instead of just `tox`. This helps non-site installations of tox, where the `tox` script may not be on `$PATH`. * Ensure tox (and other Python build-related packages) are available in Python testing images. (New images have been pushed.) * Disable `--warnings_as_errors` due to deprecated function. * Remove apt lists per [Docker best practices][1]. [1]: https://docs.docker.com/develop/develop-images/dockerfile_best-practices/	4 years ago
listonjesse	2ae7cf0e03	Auxillary -> Auxiliary	5 years ago
Joshua Haberman	bb30225f06	Sync from Piper @307316823 PROTOBUF_SYNC_PIPER	5 years ago
Paul Yang	f15ac4091f	Drop 3.3, 3.4 and use single version docker images for all python tests (#7396 ) * Create a new docker image for python 3.6 The previous one cannot build, because python3.6 was removed from stretch. * Drop support for 3.3 and 3.4 Also update all docker file to be single version	5 years ago
Paul Yang	4dec4f9371	Rebuild python docker image (#5475 ) * Rebuild python docker image * Update docker image * Change call to build_and_run_docker.sh * Set up python tests for different versions * Fix comments	6 years ago