Running with gitlab-runner 13.9.0 (2ebc4dc4)
  on Lightweight gitlab runner (aws) mVSs9rcP
section_start:1615806051:prepare_executor
Preparing the "docker+machine" executor
Using Docker executor with image registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder ...
Authenticating with credentials from job payload (GitLab Registry)
Pulling docker image registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder ...
Using docker image sha256:7a8b6166d0ac62e097d8f2792171398f4e486e073ec1dd2bf783d9bb175cf6b0 for registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder with digest registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder@sha256:67d4d5a709b4a68232621dd6c5fd4ed418c64064b2ac428b60c0fefd543041ff ...
section_end:1615806052:prepare_executor
section_start:1615806052:prepare_script
Preparing environment
Running on runner-mvss9rcp-project-6497-concurrent-0 via runner-mvss9rcp-apertis-lightweight-machine-1615804472-87b7f9d1...
section_end:1615806053:prepare_script
section_start:1615806053:get_sources
Getting source from Git repository
Fetching changes...
Initialized empty Git repository in /builds/pkg/fscrypt/.git/
Created fresh repository.
Checking out 3daa56ec as debian/bullseye...

Skipping Git submodules setup
section_end:1615806054:get_sources
section_start:1615806054:step_script
Executing "step_script" stage of the job script
Using docker image sha256:7a8b6166d0ac62e097d8f2792171398f4e486e073ec1dd2bf783d9bb175cf6b0 for registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder with digest registry.gitlab.apertis.org/infrastructure/apertis-docker-images/v2022dev2-package-source-builder@sha256:67d4d5a709b4a68232621dd6c5fd4ed418c64064b2ac428b60c0fefd543041ff ...
$ mkdir -p .git/info
$ echo '* -text -eol -crlf -ident -filter -working-tree-encoding -export-subst' > .git/info/attributes
$ echo 'debian/changelog merge=dpkg-mergechangelogs' >> .git/info/attributes
$ UPSTREAM_RELEASE=$CI_COMMIT_BRANCH
$ DOWNSTREAM_RELEASES_VAR=DOWNSTREAM_RELEASES_$(echo $UPSTREAM_RELEASE|sed "s@/@_@")
$ if [ -z "$DOWNSTREAM_RELEASES" ] # collapsed multi-line command
Checking downstream targets in DOWNSTREAM_RELEASES_debian_bullseye
$ if [ -z "$DOWNSTREAM_RELEASES" ] # collapsed multi-line command
$ apertis-pkg-merge-upstream-to-downstreams --upstream=${UPSTREAM_RELEASE} --downstream=${DOWNSTREAM_RELEASES} ${CI_AUTH_PROJECT_URL}
Branch 'debian/bullseye' set up to track remote branch 'debian/bullseye' from 'origin'.
Looking at apertis/v2022dev2 <- debian/bullseye
Traceback (most recent call last):
  File "/usr/bin/apertis-pkg-merge-upstream-to-downstreams", line 130, in <module>
    main()
  File "/usr/bin/apertis-pkg-merge-upstream-to-downstreams", line 89, in main
    if git("merge-base", "--is-ancestor", upstream_branch, downstream_branch, _ok_code=[0,1]).exit_code == 0:
  File "/usr/lib/python3/dist-packages/sh.py", line 1520, in __call__
    return RunningCommand(cmd, call_args, stdin, stdout, stderr)
  File "/usr/lib/python3/dist-packages/sh.py", line 784, in __init__
    self.wait()
  File "/usr/lib/python3/dist-packages/sh.py", line 841, in wait
    self.handle_command_exit_code(exit_code)
  File "/usr/lib/python3/dist-packages/sh.py", line 865, in handle_command_exit_code
    raise exc
sh.ErrorReturnCode_128: 

  RAN: /usr/bin/git merge-base --is-ancestor debian/bullseye apertis/v2022dev2

  STDOUT:


  STDERR:
fatal: Not a valid object name apertis/v2022dev2

section_end:1615806055:step_script
section_start:1615806055:cleanup_file_variables
Cleaning up file based variables
section_end:1615806055:cleanup_file_variables
ERROR: Job failed: exit code 1