wezterm/ci/run-esctest.sh

#!/bin/sh
set -x
export RUST_BACKTRACE=1
cargo run -- start --front-end null -- python -B ./ci/esctest/esctest/esctest.py \
  --expected-terminal=xterm \
  --xterm-checksum=334 \
  --v=3 \
  --timeout=0.1 \
  --no-print-logs \
  --logfile=esctest.log

#--stop-on-failure \
Add plumbing for running esctest 2019-03-18 01:23:53 +03:00			`#!/bin/sh`
			`set -x`
			`export RUST_BACKTRACE=1`
			`cargo run -- start --front-end null -- python -B ./ci/esctest/esctest/esctest.py \`
			`--expected-terminal=xterm \`
impl IRM insert mode and improve esctest conformance I've had mixed results with esctest; the IRM and cursor save/restore tests fail for me in terminal.app, iterm2 and xterm, and fail in the same way on wezterm, so I'm not sure if I'm not running those tests correctly. However, they did encourage the discovery of some other real issues in the wezterm emulation. 2019-03-18 09:10:04 +03:00			`--xterm-checksum=334 \`
Add plumbing for running esctest 2019-03-18 01:23:53 +03:00			`--v=3 \`
			`--timeout=0.1 \`
impl IRM insert mode and improve esctest conformance I've had mixed results with esctest; the IRM and cursor save/restore tests fail for me in terminal.app, iterm2 and xterm, and fail in the same way on wezterm, so I'm not sure if I'm not running those tests correctly. However, they did encourage the discovery of some other real issues in the wezterm emulation. 2019-03-18 09:10:04 +03:00			`--no-print-logs \`
Add plumbing for running esctest 2019-03-18 01:23:53 +03:00			`--logfile=esctest.log`
impl IRM insert mode and improve esctest conformance I've had mixed results with esctest; the IRM and cursor save/restore tests fail for me in terminal.app, iterm2 and xterm, and fail in the same way on wezterm, so I'm not sure if I'm not running those tests correctly. However, they did encourage the discovery of some other real issues in the wezterm emulation. 2019-03-18 09:10:04 +03:00
			`#--stop-on-failure \`