Skip to content
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.

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

selenium/4.28.0 package update #40017

Merged
merged 2 commits into from
Jan 20, 2025

Conversation

octo-sts[bot]
Copy link
Contributor

@octo-sts octo-sts bot commented Jan 20, 2025

@octo-sts octo-sts bot added request-version-update request for a newer version of a package automated pr labels Jan 20, 2025
Copy link
Contributor Author

octo-sts bot commented Jan 20, 2025

⚠️ EXPERIMENTAL

Please use 👍 or 👎 on this comment to indicate if you agree or disagree with the recommendation.

To provide more detailed feedback please comment on the recommendation prefixed with /ai-verify:

e.g. /ai-verify partially helpful but I also added bash to the build environment

Gen AI suggestions to solve the build error:

Based on the build log and error message, let me analyze and provide a solution:

• Detected Error:

[git checkout] execute: git clone --quiet --origin=origin --config=user.name=Melange Build [email protected] --config=advice.detachedHead=false --branch=selenium-4.28.0 --depth=1 https://github.com/SeleniumHQ/selenium /tmp/tmp.VNanER

The git clone command appears to fail silently.

• Error Category: Git/Version Control

• Failure Point: git-checkout step in the pipeline

• Root Cause Analysis:
The failure appears to be related to the git tag format in the configuration. The melange yaml is using "selenium-${{package.version}}" but upstream tags may be using a different format.

• Suggested Fix:
Modify the git-checkout step in the pipeline section to use the correct tag format:

  - uses: git-checkout
    with:
      repository: https://github.com/SeleniumHQ/selenium
      tag: v${{package.version}}  # Try changing selenium-${{package.version}} to v${{package.version}}
      expected-commit: ac342546e9e34d4ca94eceeb27cce22a4fe3b79f

Alternatively, verify the exact tag format by checking:

git ls-remote --tags https://github.com/SeleniumHQ/selenium

• Explanation:
The error occurs because the git clone command is trying to clone with a branch/tag that may not exist in the expected format. Selenium project may use a different tag naming convention than what's specified in the melange yaml.

• Additional Notes:

  • The selenium repository might use different tag formats for different types of releases
  • You can verify the exact tag format needed by checking the repository's releases page
  • If needed, you can also try using the commit hash directly instead of the tag

• References:

Let me know if you need any clarification or if you'd like me to suggest alternative approaches.

@octo-sts octo-sts bot added the ai/skip-comment Stop AI from commenting on PR label Jan 20, 2025
@OddBloke OddBloke self-assigned this Jan 20, 2025
@OddBloke OddBloke force-pushed the wolfictl-7dc4583c-7b54-46b8-a94b-726d3e834cd0 branch from be542ec to 71126ce Compare January 20, 2025 18:04
@octo-sts octo-sts bot added the bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. label Jan 20, 2025
@OddBloke OddBloke requested a review from a team January 20, 2025 18:51
@rawlingsj rawlingsj merged commit 5c89733 into main Jan 20, 2025
15 checks passed
@rawlingsj rawlingsj deleted the wolfictl-7dc4583c-7b54-46b8-a94b-726d3e834cd0 branch January 20, 2025 19:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ai/skip-comment Stop AI from commenting on PR automated pr bincapz/pass bincapz/pass Bincapz (aka. malcontent) scan didn't detect any CRITICALs on the scanned packages. manual/review-needed request-version-update request for a newer version of a package
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants