[all-commits] [llvm/llvm-project] b04b92: [lldb/pexpect] Force-set the TERM environment vari...

Pavel Labath via All-commits all-commits at lists.llvm.org
Fri Dec 20 06:17:33 PST 2019


  Branch: refs/heads/master
  Home:   https://github.com/llvm/llvm-project
  Commit: b04b92c3a4640417f2074e7e903df8c2b76eadfd
      https://github.com/llvm/llvm-project/commit/b04b92c3a4640417f2074e7e903df8c2b76eadfd
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2019-12-20 (Fri, 20 Dec 2019)

  Changed paths:
    M lldb/packages/Python/lldbsuite/test/lldbpexpect.py

  Log Message:
  -----------
  [lldb/pexpect] Force-set the TERM environment variable

In some environments (typically, buildbots), this variable may not be
available. This can cause tests to behave differently.

Explicitly set the variable to "vt100" to ensure consistent test
behavior. It should not matter that we do not inherit the process TERM
variable, as the child process runs in a new virtual terminal anyway.


  Commit: 05c3b36bc9a35a8aa3ddd6a912ddceab90c39b4d
      https://github.com/llvm/llvm-project/commit/05c3b36bc9a35a8aa3ddd6a912ddceab90c39b4d
  Author: Pavel Labath <pavel at labath.sk>
  Date:   2019-12-20 (Fri, 20 Dec 2019)

  Changed paths:
    M lldb/source/Target/ThreadPlanStepRange.cpp

  Log Message:
  -----------
  [lldb] Fix a -Wreturn-type warning on gcc


Compare: https://github.com/llvm/llvm-project/compare/453dc4d7ec5a...05c3b36bc9a3


More information about the All-commits mailing list