-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
tput: No value for $TERM and no -T specified #15679
Comments
$TERM is not always unset in every CI environment and can also be manually set. Cypress is not calling Is there a functional problem with this message? If you just want to not see it anymore, you could set your TERM to a value and the message will no longer show for you. |
We would also be open to a PR if someone tracks this down and can test/remove it. |
It happens for me in Circle-CI. Example from someone else reporting, https://discuss.circleci.com/t/getting-error-tput-no-value-for-term/27310. |
Hi, was this solved? We're getting the same error in CI and unable to run our Cypress tests |
I tried to find out where it’s coming from, but it’s not really clear. I wrapped the cypress call in a shell script that sets up a fake
The |
Add cypress-axe cypress-axe as our main CI accesibility testing tool. Adding instructions on how to run the tests will be tackled on T302321 tput: No value for $TERM and no -T specified warning showing in CI is a known bug and still an open issue in cypress. cypress-io/cypress#15679 Bug: T307910 Co-authored-by: Lucas Werkmeister <[email protected]>
This also affects GitLab. It can easily be solved by manually setting the Setting Opinion: Since many of these runners do understand terminal escape sequences, they probably should advertise so by setting the |
putting this in my script works fine if [ "${TERM:-}" = "" ]; then
echo "Setting TERM to dumb" # makes tput happy
TERM="dumb"
fi |
Started to happen randomly when running component testings in gh actions for the first time after years |
Are you using the Cypress JavaScript Action https://github.com/cypress-io/github-action to run Cypress component testing? |
@MikeMcC399 no I was not aware of the existence of this action. We are simply using the cypress cli within a
I also would like to notice that setting the env variable
I will try the cypress action whenever I get a chance and reach back to you |
Current behavior
When running Cypress in CI environments,
$TERM
is unset and thus we always get the following error/warning:Desired behavior
There should be no warning message. I've looked at this StackOverflow answer and it seems like it should be fixed here in Cypress:
You should skip the
tput
call when running in CI environments whereTERM
isn't specified.Test code to reproduce
See this GitHub action run or all of these issues that also show the same warning message (related especially to #5571 which mentions this same warning message).
You should be able to reproduce just by running
cypress run
in a CI environment.Versions
Cypress: 6.8.0
Browser: N/A
CI: GitHub Actions (but also appears in Jenkins and CircleCI)
The text was updated successfully, but these errors were encountered: