Skip to content

Install gradio from source in UI tests#2440

Merged
freddyaboulton merged 3 commits into
mainfrom
install-gradio-from-source-ui-ci
Oct 12, 2022
Merged

Install gradio from source in UI tests#2440
freddyaboulton merged 3 commits into
mainfrom
install-gradio-from-source-ui-ci

Conversation

@freddyaboulton
Copy link
Copy Markdown
Collaborator

@freddyaboulton freddyaboulton commented Oct 12, 2022

Description

Checklist:

  • I have performed a self-review of my own code
  • I have added a short summary of my change to the CHANGELOG.md
  • My code follows the style guidelines of this project
  • I have commented my code in hard-to-understand areas
  • I have made corresponding changes to the documentation
  • I have added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes

A note about the CHANGELOG

Hello 👋 and thank you for contributing to Gradio!

All pull requests must update the change log located in CHANGELOG.md, unless the pull request is labeled with the "no-changelog-update" label.

Please add a brief summary of the change to the Upcoming Release > Full Changelog section of the CHANGELOG.md file and include
a link to the PR (formatted in markdown) and a link to your github profile (if you like). For example, "* Added a cool new feature by [@myusername](link-to-your-github-profile) in [PR 11111](https://github.com/gradio-app/gradio/pull/11111)".

If you would like to elaborate on your change further, feel free to include a longer explanation in the other sections.
If you would like an image/gif/video showcasing your feature, it may be best to edit the CHANGELOG file using the
GitHub web UI since that lets you upload files directly via drag-and-drop.

@github-actions
Copy link
Copy Markdown
Contributor

All the demos for this PR have been deployed at https://huggingface.co/spaces/gradio-pr-deploys/pr-2440-all-demos

Comment thread .github/workflows/ui.yml Outdated
Copy link
Copy Markdown
Member

@pngwn pngwn Oct 12, 2022

Choose a reason for hiding this comment

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

Is this still necessary if we are using the updated runner (which comes with pip v22)?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Think so otherwise you will get (no setup.py detected but found a toml instead) error

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Let me just test to see!

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

💥 You were right

@freddyaboulton freddyaboulton marked this pull request as ready for review October 12, 2022 16:13
Comment thread CHANGELOG.md Outdated
Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

Open question but is the changelog for the repo, or just for the library?

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

I interpret it as the repo. I can remove this line though since it does not impact users of the library.

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

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

I don't mind but would be good to decide if we want it to be for the lib or for the repo. If we decide both then we should have two changelogs because the changelog is the changelog for the library first and foremost and should only include changes that impact library users.

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

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

Makes sense - noted in #2431

@pngwn
Copy link
Copy Markdown
Member

pngwn commented Oct 12, 2022

Sorry i conflicted you, because i tweaked the workflow in another PR.

@freddyaboulton freddyaboulton force-pushed the install-gradio-from-source-ui-ci branch from 6d507fa to 255755d Compare October 12, 2022 16:32
@freddyaboulton
Copy link
Copy Markdown
Collaborator Author

No problem @pngwn - just rebased. Is this good to merge?

@freddyaboulton freddyaboulton force-pushed the install-gradio-from-source-ui-ci branch from 255755d to b69a69d Compare October 12, 2022 16:40
@pngwn
Copy link
Copy Markdown
Member

pngwn commented Oct 12, 2022

yip

@freddyaboulton freddyaboulton merged commit 89fc21b into main Oct 12, 2022
@freddyaboulton freddyaboulton deleted the install-gradio-from-source-ui-ci branch October 12, 2022 16:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants