tests: Fix test compatibility with Python 3.14 forkserver

Python 3.14 changed the default multiprocessing start method on Linux
from "fork" to "forkserver". The test_forall_all_projects_called_once
test uses mock.patch.object on Project.GetRevisionId, but class-level
mock patches do not survive into forkserver worker processes because
they start from a clean Python interpreter rather than inheriting the
parent's memory.

Replace the mock with setting revisionId directly on each Project
instance so GetRevisionId() short-circuits without touching git.
This works with any multiprocessing start method since the string
attribute is part of the Project objects stored in _parallel_context,
which is properly serialized to workers via initargs.

Bug: 425319437
Change-Id: Icd3bbd010921d7652bb2425fad85974df9198367
Reviewed-on: https://gerrit-review.googlesource.com/c/git-repo/+/602941
Tested-by: Brian Gan <brgan@google.com>
Commit-Queue: Brian Gan <brgan@google.com>
Reviewed-by: Gavin Mak <gavinmak@google.com>
1 file changed
tree: 16ae236200c38405f54de49ac37d1499be92b70a
  1. .github/
  2. agents/
  3. docs/
  4. hooks/
  5. man/
  6. release/
  7. subcmds/
  8. tests/
  9. .flake8
  10. .gitattributes
  11. .gitignore
  12. .gitreview
  13. .mailmap
  14. .project
  15. .pydevproject
  16. cipd_manifest.txt
  17. cipd_manifest.versions
  18. color.py
  19. command.py
  20. completion.bash
  21. completion.zsh
  22. constraints.txt
  23. CONTRIBUTING.md
  24. editor.py
  25. error.py
  26. event_log.py
  27. fetch.py
  28. git_command.py
  29. git_config.py
  30. git_refs.py
  31. git_ssh
  32. git_superproject.py
  33. git_trace2_event_log.py
  34. git_trace2_event_log_base.py
  35. hooks.py
  36. LICENSE
  37. main.py
  38. MANIFEST.in
  39. manifest_xml.py
  40. pager.py
  41. platform_utils.py
  42. platform_utils_win32.py
  43. progress.py
  44. project.py
  45. pyproject.toml
  46. README.md
  47. repo
  48. repo_logging.py
  49. repo_trace.py
  50. requirements.json
  51. run_tests
  52. run_tests.vpython3
  53. run_tests.vpython3.8
  54. setup.py
  55. ssh.py
  56. wrapper.py
README.md

repo

Repo is a tool built on top of Git. Repo helps manage many Git repositories, does the uploads to revision control systems, and automates parts of the development workflow. Repo is not meant to replace Git, only to make it easier to work with Git. The repo command is an executable Python script that you can put anywhere in your path.

Contact

Please use the repo-discuss mailing list or issue tracker for questions.

You can file a new bug report under the “repo” component.

Please do not e-mail individual developers for support. They do not have the bandwidth for it, and often times questions have already been asked on repo-discuss or bugs posted to the issue tracker. So please search those sites first.

Install

Many distros include repo, so you might be able to install from there.

# Debian/Ubuntu.
$ sudo apt-get install repo

# Gentoo.
$ sudo emerge dev-vcs/repo

You can install it manually as well as it's a single script.

$ mkdir -p ~/.bin
$ PATH="${HOME}/.bin:${PATH}"
$ curl https://storage.googleapis.com/git-repo-downloads/repo > ~/.bin/repo
$ chmod a+rx ~/.bin/repo

Shell Completion

Repo includes completion scripts for Bash and Zsh.

Bash

To enable completion in Bash, source completion.bash in your ~/.bashrc:

source /path/to/git-repo/completion.bash

Zsh

To enable completion in Zsh, you can either:

  1. Copy or symlink completion.zsh to a file named _repo in a directory in your $fpath:

    mkdir -p ~/.zsh/completion
    # You can copy the file:
    cp /path/to/git-repo/completion.zsh ~/.zsh/completion/_repo
    # Or symlink it:
    ln -s /path/to/git-repo/completion.zsh ~/.zsh/completion/_repo
    

    Then add that directory to your fpath in ~/.zshrc before compinit:

    fpath=(~/.zsh/completion $fpath)
    autoload -Uz compinit
    compinit
    
  2. Or source the file directly and call compdef in your ~/.zshrc:

    source /path/to/git-repo/completion.zsh
    compdef _repo repo