GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — Long commit messages cause tests to fail on merge · Issue #13 · browserstack/github-actions

Long commit messages cause tests to fail on merge #13

New issue
Copy link
New issue
Copy link
Open
Open
Long commit messages cause tests to fail on merge#13
Copy link

Description

@madwort
madwort
opened on Oct 21, 2021
Issue body actions

setup-env's default behaviour for push events generates build names that are too long to pass to BrowserStack if the commit message is long. We experienced this as tests failing after merging a PR with:

selenium.common.exceptions.WebDriverException: Message: name cannot be more than 255 characters

We're planning to work around this by passing GITHUB_SHA in place of BUILD_INFO (see also bennettoxford/openprescribing#3239 )

Activity

  1. SachinMNair commented on Oct 21, 2021

    @SachinMNair
    SachinMNair
    on Oct 21, 2021
    More actions

    Hey @madwort, I have checked and yes, the build capability does not accept more than 255 characters. I will confirm it with our engineering team and get back to you

  2. SachinMNair commented on Oct 21, 2021

    @SachinMNair
    SachinMNair
    on Oct 21, 2021
    More actions

    Hey @madwort, I can confirm that the build name can be only upto 255 characters long. You can also refer this in https://www.browserstack.com/docs/automate/selenium/organize-tests

  3. madwort commented on Jan 12, 2022

    @madwort
    madwort
    on Jan 12, 2022
    Author
    More actions

    hi @SachinMNair do you think your engineering team would be willing to merge #14 ? Thanks!

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions
      You are visitor 01402503 — GeezerVison does not store the pages you look up.
      Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.