[TODO] $HOME/.rvm/scripts/functions/support: line 57: shell_session_update: command not found

[timotheecour]

travis fails with

/Users/travis/.rvm/scripts/functions/support: line 57: shell_session_update: command not found

.travis.yml is here: https://github.com/nim-lang/Nim/blob/5492190bc63326069233a8aaf9f2e567cfc555f8/.travis.yml
example travis log here: https://travis-ci.org/nim-lang/Nim/jobs/367840604

this error is very common on the web, however I couldn't find an answer that works

• adding

• adding rvm get head as suggested here https://superuser.com/questions/1044130/why-am-i-having-how-can-i-fix-this-error-shell-session-update-command-not-f results in other error:

Warning, RVM 1.26.0 introduces signed releases and automated check of signatures when GPG software found.
/Users/travis/.rvm/scripts/functions/cli: line 243: return: _ret: numeric argument required
The command "rvm get head" failed and exited with 255 during .
Your build has been stopped.
/Users/travis/.travis/job_stages: line 166: shell_session_update: command not found

(eg: https://travis-ci.org/nim-lang/Nim/jobs/367878319)

• adding rvm get head || true as suggested here New Mac OS build error since the recent outage: "/Users/travis/build.sh: line 109: shell_session_update: command not found error" #6522 (comment) also fails with
  /Users/travis/.rvm/scripts/functions/support: line 57: shell_session_update: command not found

• removing set -e from .travis.yml is not an option as I don't want to silently ignore errors, as also explained by others here New Mac OS build error since the recent outage: "/Users/travis/build.sh: line 109: shell_session_update: command not found error" #6522 (comment)

@BanzaiMan - that is intentional. I need to halt the build on errors in my scripts. I agree with you that without that set -e the build would continue past the shell_session_update error, but I can't let other errors happen silently so I need the set -e. I worked around this by doing Project-OSRM/node-osrm@cdb5b6c and now builds are working fine.

This error seems to affect pretty much every project that uses -e since at least 2015. How do we fix this?

related:

#9486
#6522

[stale]

Thanks for contributing to this issue. As it has been 90 days since the last activity, we are automatically closing the issue in 24 hours. This is often because the request was already solved in some way and it just wasn't updated or it's no longer applicable. If that's not the case, please do feel free to either reopen this issue or open a new one. We'll gladly take a look again! You can read more here: https://blog.travis-ci.com/2018-03-09-closing-old-issues

[timotheecour]

/cc @DrTorte @acnagy just curious why was this closed and whether we could reopen this issue; is anyone working on this?

see #8703 (comment) for a workaround

[acnagy]

Ah, thanks for the ping - let's def reopen. AFAIK there isn't someone working on this specifically, but I'll see what I can do about raising it with people who might be able to!

[timotheecour]

great! a simple search for this issue reveals this problem is widespread and has been going on since at least april:
https://github.com/search?q=%22shell_session_update%3A+command+not+found%22&type=Issues shows 283 issues,
it's causing a lot of overhead in finding workardounds for people using travis

[ThomasWaldmann]

https://travis-ci.org/borgbackup/borg/jobs/401269432

this job worked some months ago and now is broken due to a shell_session_update issue.

i restarted the job to verify whether travis works because a current pull request was strangely failing due to reasons unrelated to the changes in the PR.

so, is there something broken on travis ci and can it please get fixed?