PR is not created when the lockfile-only Cargo update fails

[psalaberria002]

How are you running Renovate?

Self-hosted Renovate

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitHub, 39.8.0

Please tell us more about your question or problem

I noticed we had a couple of entries under Other Branches and both were related to Cargo lockfile branches.

After inspecting the logs, I saw there were failures related to precise cargo upgrades due to dependency constraints, and other entries about Renovate not being able to open PRs because there weren't any changed files to commit.

The cargo update command that fails looks as follows.

cargo update --config net.git-fetch-with-cli=true --manifest-path Cargo.toml --package archery@1.2.0 --precise 1.2.1
    Updating crates.io index
error: failed to select a version for `triomphe`.
    ... required by package `moka v0.12.8`
    ... which satisfies dependency `moka = "^0.12.7"` (locked to 0.12.8) of package `xxx_auth_testutils v0.1.0 (xxx_auth_testutils)`
versions that meet the requirements `>=0.1.3, <0.1.12` are: 0.1.11, 0.1.10, 0.1.9, 0.1.8, 0.1.7, 0.1.6, 0.1.5, 0.1.4, 0.1.3

all possible versions conflict with previously selected packages.

  previously selected package `triomphe v0.1.13`
    ... which satisfies dependency `triomphe = "^0.1.13"` of package `archery v1.2.1`
    ... which satisfies dependency `archery = "^1.2.0"` of package `internal-jwks-host v0.2.0 (/internal-jwks-host)`

failed to select a version for `triomphe` which could resolve this conflict

Is this behavior expected?

Any workarounds to avoid having these branches run in each cycle in Renovate?

Logs (if relevant)

Logs

DEBUG: git status counts after post-upgrade tasks (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "dep": "archery",
       "addedCount": 0,
       "modifiedCount": 0,
       "deletedCount": 0,
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: Checking 0 added or modified files for post-upgrade changes (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "dep": "archery",
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: Branch timestamp: 2024-08-13T18:50:29.155977+00:00 (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: PR is older than 2 hours, raise PR with lock file errors (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: 1 file(s) to commit (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: Preparing files for committing to branch renovate/archery-1.x-lockfile (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: Setting git author name: renovate-infrastructure[bot] (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "trace_id": "4bcb88c2e6a65909a6b8e017d3701926",
       "span_id": "0a8051e19d334332",
       "trace_flags": "01"
DEBUG: Setting git author email: 152190926+renovate-infrastructure[bot]@users.noreply.github.com (repository=xxx, branch=renovate/archery-1.x-lockfile)
DEBUG Detected empty commit - aborting git push (repository=xxx, branch=renovate/archery-1.x-lockfile)
       "commitRes": {
         "author": null,
         "branch": "",
         "commit": "",
         "root": false,
         "summary": {"changes": 0, "insertions": 0, "deletions": 0}
       },

[rarkins]

It is expected that some combinations of upgrades may not be resolvable in this manner.

Please clarify what you're seeing. e.g. branches exist, but not associated PRs? Is this because you have prCreation=success set?

[psalaberria002]

Branches are not created in Github, but I see the entries in the 'Other Branches' section.

We have a quite heavy post upgrade command, and these 'stuck' upgrades are slowing down the runs.

We are using config:best-practices. Haven't set prCreation explicitly.

[rarkins]

Try deleting those branches, and if they're recreated then capture the debug logs when it happens