Alexander Markov
652a8be7a7
When tests are executed on certain configurations like dartkb or simarm, the test script is first compiled into a dill file, so the VM command line for running a test looks like dart .../generated_compilations/dartkb/foo_test/out.dill Certain tests have the logic to replace '_test.dart' in Platform.script with '_test_body.dart' and execute the resulting script. However, as out.dill does not contain '_test.dart', the script remains the same after replacement. As a result, test was infinitely re-executing itself, overloading bots and not making any progress. Change-Id: I7257d3553a7f0a0de2f6d8218a9eb5c8981af17d Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/98685 Commit-Queue: Ryan Macnak <rmacnak@google.com> Auto-Submit: Alexander Markov <alexmarkov@google.com> Reviewed-by: Ryan Macnak <rmacnak@google.com>
Run Existing Tests ================== See the output of ../tools/test.py --help for how to run tests. See also https://code.google.com/p/dart/wiki/Building#Testing for detailed examples. Create New Tests ================ See comments above factory StandardTestSuite.forDirectory in ../tools/testing/dart/test_suite.dart for the default test directory layout. By default test-file names must end in "_test.dart", but some test suites, such as ./co19, subclass StandardTestSuite and override this default. See comments at the beginning of ../tools/testing/dart/multitest.dart for how to create tests that pass by failing with a known error. For example, ... int x = "not an int"; /// 01: static type warning ... as part of a test will only pass the "--compiler dart2analyzer" test if the assignment generates a static type warning.