view tests/test-contrib-emacs.t @ 42386:15d5a2de44aa

tests: make run-tests exit non-zero if there are "errors" Previously, if there was an error such as a broken .t file that caused run-tests.py to encounter an exception during parsing, the test would be considered in an "errored" state, which is separate from "failed". The check for whether to exit non-zero or not was based entirely on whether there were any tests in a "failed" state, so if there was only an error, run-tests would exit with 0. Our test infrastructure would then consider the test as passing, causing us to have some tests with false negatives that have gone undetected for a few weeks now. Differential Revision: https://phab.mercurial-scm.org/D6452
author Kyle Lippincott <spectral@google.com>
date Tue, 28 May 2019 23:22:46 -0700
parents 19979b8b87e2
children 814c7430f828
line wrap: on
line source

#require emacs
  $ emacs -q -no-site-file -batch -l $TESTDIR/../contrib/hg-test-mode.el \
  >  -f ert-run-tests-batch-and-exit
  Running 1 tests (*) (glob)
     passed  1/1  hg-test-mode--compilation-mode-support
  
  Ran 1 tests, 1 results as expected (*) (glob)