dash/.travis
MarcoFalke 313d79e319
Merge #16961: test: Remove python dead code linter
f4beb4996d27f2cdaf4f0a63e7dc044bf17decce test: Remove python dead code linter (Wladimir J. van der Laan)

Pull request description:

  Primarily I'd like to remove this because it is very imprecise, due to Python's dynamic nature, giving it a large list of false positives that need to be listed as exceptions. See for example #16906.

  It's also a frequent source of complaints. I'm doubtful of the usefulness of checking for dead code in a linter in the first place.
  Having some dead code in the test framework for a while is not a
  disaster.

ACKs for top commit:
  sdaftuar:
    utACK f4beb4996d27f2cdaf4f0a63e7dc044bf17decce
  practicalswift:
    ACK f4beb4996d27f2cdaf4f0a63e7dc044bf17decce -- diff looks correct
  jamesob:
    ACK f4beb4996d

Tree-SHA512: 329b1555210311d5d15799fd2cb794b3208b0ac4d8a2ffaf4dece1bcc3e0e8b1fe952d5e7a394f94a98919cab579fb579eae7db2a796cc9a1a42ef495dd17507
2021-10-05 20:34:00 +03:00
..
lint_04_install.sh Merge #16961: test: Remove python dead code linter 2021-10-05 20:34:00 +03:00
lint_05_before_script.sh Partial merge #13863: travis: move script sections to files in .travis/ subject to shellcheck 2021-07-08 13:09:43 -04:00
lint_06_script.sh Merge #15255: [tests] Remove travis_wait from lint script 2021-09-10 20:55:59 -04:00
README.md Partial merge #13863: travis: move script sections to files in .travis/ subject to shellcheck 2021-07-08 13:09:43 -04:00
test_03_before_install.sh Merge #14673: travis: Fail the UBSan Travis build in case of newly introduced UBSan errors 2021-08-18 13:56:42 -05:00
test_04_install.sh Merge #16438: travis: Print memory and number of cpus 2021-09-12 14:15:12 -04:00
test_05_before_script.sh merge #19240: macOS toolchain simplification and bump 2021-09-03 17:49:55 +05:30

travis build scripts

The .travis directory contains scripts for each build step in each build stage. Currently the travis build defines two stages lint and test. Each stage has it's own lifecycle. Every script in here is named and numbered according to which stage and lifecycle step it belongs to.