Skip to content

Long commit messages cause tests to fail on merge #13

@madwort

Description

@madwort

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 )

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions