Skip to content

chore: fix the manual cross platform test run#9252

Merged
epinzur merged 1 commit into
mainfrom
fix_manual_cp_test
Jul 31, 2025
Merged

chore: fix the manual cross platform test run#9252
epinzur merged 1 commit into
mainfrom
fix_manual_cp_test

Conversation

@epinzur
Copy link
Copy Markdown
Contributor

@epinzur epinzur commented Jul 31, 2025

An attempt to fix the manual cross-platform install test. Formerly the build worked but the test didn't initiate.

Summary by CodeRabbit

  • Chores
    • Added enhanced debugging and input validation steps to the cross-platform test workflows.
    • Introduced a new job to display workflow parameters and artifact names for improved traceability.
    • Updated job dependencies and input handling to ensure consistent parameter passing with default values.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jul 31, 2025

Walkthrough

This update enhances the cross-platform test workflows by introducing explicit input validation, additional debugging steps, and a new debug job. It ensures that required inputs are present, prints detailed parameter and artifact information, and adjusts job dependencies and input handling for clarity and traceability.

Changes

Cohort / File(s) Change Summary
Shared Workflow Debugging & Input Validation
.github/workflows/cross-platform-test-shared.yml
Adds steps to print workflow inputs and matrix values, and conditionally validates presence of required inputs (base-artifact-name, main-artifact-name) when installation method is 'wheel'.
Main Workflow Debugging, Job Dependencies, and Input Handling
.github/workflows/cross-platform-test.yml
Adds a debug step in build-if-needed to print artifact names and parameters, introduces a new debug-parameters job for parameter visibility, updates test-wheel-installation job to depend on debug-parameters, and refines input expressions with default fallbacks.

Sequence Diagram(s)

sequenceDiagram
    participant Workflow
    participant BuildJob as build-if-needed
    participant DebugJob as debug-parameters
    participant TestJob as test-wheel-installation

    Workflow->>BuildJob: Start build-if-needed
    BuildJob->>BuildJob: Print artifact names & parameters (debug step)
    BuildJob-->>Workflow: Outputs artifact names

    Workflow->>DebugJob: Start debug-parameters (needs: build-if-needed)
    DebugJob->>DebugJob: Print resolved parameters & build outputs

    Workflow->>TestJob: Start test-wheel-installation (needs: build-if-needed, debug-parameters)
    TestJob->>TestJob: Validate & print input parameters (shared workflow)
    TestJob->>TestJob: Run tests with validated inputs
Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

Possibly related PRs

Suggested labels

lgtm

Suggested reviewers

  • ogabrielluiz

Note

⚡️ Unit Test Generation is now available in beta!

Learn more here, or try it out under "Finishing Touches" below.

✨ Finishing Touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch fix_manual_cp_test

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai generate unit tests to generate unit tests for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@SonicDMG SonicDMG temporarily deployed to fix_manual_cp_test - langflow-manual-install PR #9252 July 31, 2025 09:18 — with Render Destroyed
@sonarqubecloud
Copy link
Copy Markdown

@epinzur epinzur merged commit 7827122 into main Jul 31, 2025
6 of 7 checks passed
@epinzur epinzur deleted the fix_manual_cp_test branch July 31, 2025 09:22
Copy link
Copy Markdown
Contributor

@coderabbitai coderabbitai Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (5)
.github/workflows/cross-platform-test-shared.yml (2)

82-97: Add basic Bash safety flags to the debug step

Running the debug script with set -euo pipefail (or at least set -e) will make the step fail fast on unexpected errors (e.g. missing variables, failed subshells) instead of silently continuing. It is free insurance and keeps the workflow behaviour deterministic.

-      - name: Debug workflow inputs
-        run: |
+      - name: Debug workflow inputs
+        run: |
+          set -euo pipefail
           echo "Shared workflow received inputs:"

99-109: Parameter validation can be moved to the if: guard and avoid an extra shell exit

You already know, at eval time, whether either name is missing. Using the expression language lets GitHub mark the whole job as skipped instead of launching a Bash process only to exit 1, saving one runner minute and keeping logs cleaner.

# replace the existing step with a single-line noop that never runs
- name: Validate required parameters for wheel installation
  if: inputs.install-method == 'wheel' && (inputs.base-artifact-name == '' || inputs.main-artifact-name == '')
  run: |
    echo "❌ base-artifact-name and main-artifact-name are required when install-method is 'wheel'"
    exit 1
  shell: bash
.github/workflows/cross-platform-test.yml (3)

84-92: Avoid hard-coding artifact names in the debug log

The step prints fixed strings (adhoc-dist-base / adhoc-dist-main) instead of the actual output variables, which will mislead readers if the names ever change. Emit the resolved names directly from steps.set-names.outputs (or ${{ needs.build-if-needed.outputs.* }}) to keep the log truthful.

-          echo "  base-artifact-name: adhoc-dist-base"
-          echo "  main-artifact-name: adhoc-dist-main"
+          echo "  base-artifact-name: ${{ needs.build-if-needed.outputs.base-artifact-name }}"
+          echo "  main-artifact-name: ${{ needs.build-if-needed.outputs.main-artifact-name }}"

93-111: Expressions can be simplified for readability

inputs.base-artifact-name != '' && inputs.base-artifact-name is redundant—an empty string is already “falsey”. Dropping the comparison shortens the expression without changing semantics:

${{ inputs.base-artifact-name || needs.build-if-needed.outputs.base-artifact-name || 'adhoc-dist-base' }}

Same for main-artifact-name and test-timeout. Less punctuation → easier maintenance.


119-121: Coalesce expressions the same way in the with: block

After simplifying as above you can shorten the with: section:

-      test-timeout: ${{ inputs.test-timeout || 5 }}
-      base-artifact-name: ${{ inputs.base-artifact-name != '' && inputs.base-artifact-name || needs.build-if-needed.outputs.base-artifact-name || 'adhoc-dist-base' }}
-      main-artifact-name: ${{ inputs.main-artifact-name != '' && inputs.main-artifact-name || needs.build-if-needed.outputs.main-artifact-name || 'adhoc-dist-main' }}
+      test-timeout: ${{ inputs.test-timeout || 5 }}
+      base-artifact-name: ${{ inputs.base-artifact-name || needs.build-if-needed.outputs.base-artifact-name || 'adhoc-dist-base' }}
+      main-artifact-name: ${{ inputs.main-artifact-name || needs.build-if-needed.outputs.main-artifact-name || 'adhoc-dist-main' }}

Functionally identical, a little easier on future readers.

📜 Review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 483af5b and 1f45de1.

📒 Files selected for processing (2)
  • .github/workflows/cross-platform-test-shared.yml (1 hunks)
  • .github/workflows/cross-platform-test.yml (1 hunks)

@ogabrielluiz ogabrielluiz changed the title bug: fix the manual cross platform test run chore: fix the manual cross platform test run Jul 31, 2025
2getsandesh pushed a commit to 2getsandesh/langflow-IBM that referenced this pull request Aug 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants