Skip to content

[dotnet][java][js][py][rb][rust] Update java_image_base Docker digest to 38e4b51 #14945

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
wants to merge 2 commits into from
Closed

[dotnet][java][js][py][rb][rust] Update java_image_base Docker digest to 38e4b51 #14945

wants to merge 2 commits into from

Conversation

@renovate
Copy link
Contributor

@renovate renovate bot commented Dec 26, 2024

This PR contains the following updates:

Package Type Update Change
java_image_base oci_pull digest 161a1d9 -> 38e4b51

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate bot added B-build Includes scripting, bazel and CI integrations B-dependencies Pull requests that update a dependency file labels Dec 26, 2024
@qodo-merge-pro
Copy link
Contributor

qodo-merge-pro bot commented Dec 26, 2024 •
edited
Loading

CI Failure Feedback 🧐

(Checks updated until commit cccc5f7)

Action: Java / Browser Tests (windows) / Browser Tests (chrome, windows)

Failed stage: Pull latest changes [❌]

Failure summary:

The action failed because Git refused to merge unrelated histories. This typically happens when:

  • Trying to merge two branches that don't share a common commit history
  • The branch being merged (renovate/java_image_base) has a completely different commit history from
    the target branch
  • This is often seen when trying to merge automated branches (like Renovate) that were created from
    scratch

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  Microsoft Windows Server 2022
...

169:  TWINE_USERNAME: 
170:  NODE_AUTH_TOKEN: ***
171:  SE_AVOID_STATS: true
172:  ##[endgroup]
173:  From https://github.com/SeleniumHQ/selenium
174:  * branch                  renovate/java_image_base -> FETCH_HEAD
175:  * [new branch]            renovate/java_image_base -> origin/renovate/java_image_base
176:  fatal: refusing to merge unrelated histories
177:  ##[error]Process completed with exit code 1.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @qodo-merge-pro
    Copy link
    Contributor

    qodo-merge-pro bot commented Dec 26, 2024

    CI Failure Feedback 🧐

    Action: Java / Browser Tests (macos) / Browser Tests (chrome, macos)

    Failed stage: Pull latest changes [❌]

    Failure summary:

    The action failed because Git encountered a merge conflict and couldn't automatically determine how
    to reconcile divergent branches. This typically happens when:

  • The PR branch has diverged from the target branch
  • Git's pull strategy is not configured
  • Git needs explicit instructions on how to handle the merge (rebase vs. merge)

    • Relevant error logs: 
    1:  ##[group]Operating System
2:  macOS
...

161:  hint:   git config pull.rebase true   # rebase
162:  hint:   git config pull.ff only       # fast-forward only
163:  hint:
164:  hint: You can replace "git config" with "git config --global" to set a default
165:  hint: preference for all repositories. You can also pass --rebase, --no-rebase,
166:  hint: or --ff-only on the command line to override the configured default per
167:  hint: invocation.
168:  fatal: Need to specify how to reconcile divergent branches.
169:  ##[error]Process completed with exit code 128.
    ✨ CI feedback usage guide:

    The CI feedback tool (/checks) automatically triggers when a PR has a failed check.
    The tool analyzes the failed checks and provides several feedbacks:

    • Failed stage
    • Failed test name
    • Failure summary
    • Relevant error logs

    In addition to being automatically triggered, the tool can also be invoked manually by commenting on a PR:

    /checks "https://github.com/{repo_name}/actions/runs/{run_number}/job/{job_number}"

    where {repo_name} is the name of the repository, {run_number} is the run number of the failed check, and {job_number} is the job number of the failed check.

    Configuration options

    • enable_auto_checks_feedback - if set to true, the tool will automatically provide feedback when a check is failed. Default is true.
    • excluded_checks_list - a list of checks to exclude from the feedback, for example: ["check1", "check2"]. Default is an empty list.
    • enable_help_text - if set to true, the tool will provide a help message with the feedback. Default is true.
    • persistent_comment - if set to true, the tool will overwrite a previous checks comment with the new feedback. Default is true.
    • final_update_message - if persistent_comment is true and updating a previous checks message, the tool will also create a new message: "Persistent checks updated to latest commit". Default is true.

    See more information about the checks tool in the docs.

    @renovate
    Copy link
    Contributor Author

    renovate bot commented Dec 26, 2024

    Edited/Blocked Notification

    Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

    You can manually request rebase by checking the rebase/retry box above.

    ⚠️ Warning: custom changes will be lost.

    @diemol diemol closed this Dec 26, 2024
    @diemol diemol deleted the renovate/java_image_base branch December 26, 2024 22:24
    @renovate
    Copy link
    Contributor Author

    renovate bot commented Dec 26, 2024

    Renovate Ignore Notification

    Because you closed this PR without merging, Renovate will ignore this update. You will not get PRs for the java_image_base 38e4b51 update again.

    If you accidentally closed this PR, or if you changed your mind: rename this PR to get a fresh replacement PR.

    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

    Reviewers

    No reviews

    Assignees

    No one assigned

    Labels

    B-build Includes scripting, bazel and CI integrations B-dependencies Pull requests that update a dependency file

    Projects

    None yet

    Milestone

    No milestone

    Development

    Successfully merging this pull request may close these issues.

    3 participants

    @diemol @selenium-ci