Commit Graph

18 Commits

Author SHA1 Message Date
Owen Voorhees
f749e8551f [Docs] Add a section to Diagnostics.md on -verify mode 2019-09-30 17:14:32 -07:00
Joe Shajrawi
ad59d902b9 Set up testing with the standard libraries coming from the OS
We  default Swift tests to use the just-built libraries
See radars rdar://problem/35163663 and rdar://problem/42176864
2019-03-27 11:16:48 -07:00
Mathew Polzin
3d05edd239 Noticed while reading the Testing README that there were now five categories so I updated the word four to five. 2019-02-11 09:01:39 -08:00
Andreas Jönsson
0a3f38792a [Doc] Updated testing lit.py example to use macosx environment as iphonesimulator doesn't work out of the box 2018-12-23 00:03:42 +01:00
Mike Ash
1131507578 [Testing] Add a substitution for %target-is-simulator. 2018-10-04 12:32:50 -04:00
Jordan Rose
8c48e39e42 [test] Add --param remote_run_extra_args (#18885)
This goes with 810b240354: if we want to pass extra arguments to SSH
when using remote-run, there has to be a way to get them to remote-run
when using lit.
2018-08-22 13:19:03 -07:00
Vedant Kumar
9eec249a85 [docs] Document the swift-lldb test whitelist (#18730) 2018-08-15 16:48:03 -07:00
Jordan Rose
290bf08655 [docs] Update Testing.md for remote-run support 2018-08-14 11:17:08 -07:00
David Zarzycki
283713d61d [Testing] Formalize stress tests
Stress tests are, by definition, stressful. They intentionally burn a
lot of resources by using randomness to hopefully surface state machine
bugs. Additionally, many stress tests are multi-threaded these days and
they may attempt to use all of the available CPUs to better uncover
bugs. In isolation, this is not a problem, but the test suite as a whole
assumes that individual tests are single threaded and therefore running
multiple stress tests at once can quickly spiral out of control.

This change formalizes stress tests and then treats them like long
tests, i.e. tested via 'check-swift-all' and otherwise opt-in.

Finally, with this change, the CI build bots might need to change if
they are still only testing 'validation' instead of all of the tests.
I see three options:

1) Run all of the tests. -- There are very few long tests left these
   days, and the additional costs seems small relative to the cost of
   the whole validation test suite before this change.
2) Continue checking 'validation', now sans stress tests.
3) Check 'validation', *then* the stress tests. If the former doesn't
   pass, then there is no point in the latter, and by running the stress
   tests separately, they stand a better chance of uncovering bugs and
   not overwhelming build bot resources.
2018-03-20 21:45:28 -04:00
Graydon Hoare
2536bbb788 [docs] Mention lit.py -vv option, helpful for diagnosis. 2017-10-20 15:38:07 -07:00
Greg Parker
b7f744c302 [test] Replace CPU=i386_or_x86_64 with CPU=i386 || CPU=x86_64. (#11889) 2017-09-12 19:34:08 -07:00
Michael Gottesman
6a6efd9f4e Merge pull request #11463 from KingOfBrian/documentation/DeveloperOnboarding
Update README.md
2017-08-21 14:00:33 -07:00
Ewa Matejska
1272cd3aac Making master call itself 4.1, updating the swift 3 compatiblity mode to be 3.3 (from 3.2), adding ability to pass swift-version 5. Importer work not done yet. 2017-08-17 20:57:01 -07:00
Brian King
28de02ea8b Remove day-to-day language. 2017-08-17 20:39:43 -04:00
Brian King
49bb53a0e3 Change from SWIFT_BUILD_ROOT to SWIFT_BUILD_DIR in examples. SWIFT_BUILD_ROOT means something else in the build script. 2017-08-15 20:31:32 -04:00
Brian King
797c0939f2 Emphasize lit testing 2017-08-14 19:37:45 -04:00
Brian King
22fc53c660 Move note on writing long tests into the section on writing tests 2017-08-14 19:26:46 -04:00
Michael Gottesman
2289e5c509 [gardening] Convert Testing.rst to markdown and rename to Testing.md 2017-07-04 23:33:04 -07:00