Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2019-04-02T13:22:13+00:00 2019-04-02T13:22:13+00:00 jsmall-nvidia jsmall@nvidia.com 2019-04-02T13:22:13+00:00 urn:sha1:2896aa39a529a00673a30ef4a9c3ebe76f401fea * First pass extract the test information by 'running tests'. * * Checking renderer availablilty * Using TestInfo to determine which tests are run and synthesized * Display if test is synthesized and what render api it's targetting * * Improved comments * Removed some dead code * Display ignored tests. * TestInfo -> TestRequirements * * Added DIAGNOSTIC_TEST type - test always runs (ie has no requirements). * Made diagnostic tests use DIAGNOSTIC_TEST * TestInfo -> TestRequirements * TestDetails holds TestRequirements and TestOptions * Fix debug typo. 2017-06-14T21:40:48+00:00 Tim Foley tfoley@nvidia.com 2017-06-14T16:10:22+00:00 urn:sha1:90d6a401ee0d6327b068e58a64a10f620300a38e This includes a bunch of related changes: - `slang-test` - Add a notion of an "output mode" that specifies whether we output to console (the default), or invoke the apprpriate AppVeyor command to update test status - Add a notion of test categories, so that tests can be tagged with categories, and then we can invoke only those tets in a given category, or choose to *exclude* tests with specific categories - Allow the `OSProcessSpawner` to look up an executable by "path" (meaning a full path is expected) or by "name" (meaning it should be allowed to look in the current directory, `PATH` environment variable, etc.). This was important to make sure that I can run `appveyor` without having to know its absolute path. - AppVeyor configuration - Change badge to reflect new build account for organization (rather than a single-user account) - Remove attempt to set AppVeyor build version in a clever way, since it breaks links from GitHub to AppVeyor - Change order or configurations in the build matrix to front-load the Release build (which has the main tests) - Turn on `fast_finish` flag so we don't have to wait as long for failed builds - Turn on `parallel` builds - Set `verbosity: minimal` to avoid getting build spew about Xamarin stuff I'm not using - Add custom `test_script` to invoke `test.bat` - Sets the test category based on teh build configuration, so we don't run the full test suite on every input. - `test.bat` - Allow for `-platform` and `-configuration` arguments - Rewrute a platform of `Win32` over to `x86` to match how the output directories are named - Futz around with how the directories are being passed along to work around annoying `.bat` file quoting behavior (I still don't get how batch files work) - Tests - Mark a bunch of tests as `smoke` tests - Mark the relevant tests as `render` tests (these get filtered out for AppVeyor builds) 2017-06-12T20:00:47+00:00 Tim Foley tfoley@nvidia.com 2017-06-12T19:42:17+00:00 urn:sha1:5b49974bd6ddd248b5ee1b1e29c0acfc3c422a3a Many of the existing test cases were being skipped on accident, because their file names used `.spire` and the test tool was now looking for `.slang`