Making it easier to work with shaders https://git.yummers.dev/slang.git/atom?h=master 2022-05-18T17:57:37+00:00 2022-05-18T17:57:37+00:00 Alexey Panteleev alpanteleev@nvidia.com 2022-05-18T17:57:37+00:00 urn:sha1:69cb6e8f300d77e74bd2c7dfe15d12e10b38f512 See https://github.com/shader-slang/slang/issues/2213 2017-10-14T01:14:42+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2017-10-14T01:14:42+00:00 urn:sha1:64ddefb90cf440df7879d1f2f9cc61de71e0f181 Move reflection JSON generation into separate test fixture 2017-09-29T20:43:08+00:00 Tim Foley tfoleyNV@users.noreply.github.com 2017-09-29T20:43:08+00:00 urn:sha1:8a0ebb9fa25fd44def17b03b3f8aa1a33ad77940 * Get tests running/passing under Linux - Fix up `dlopen` abstraction - Fix up some test cases to request hlsl (rather than default to dxbc) so they can run on non-Windows targets - Fix up test runner ignore tests that can't run on current platform (and not count those as failure) - Fix file handle leeak in process spawner absttraction - Get additional test-related applications building - More tweaks to Travis script; in theory deployment is set up now (yeah, right) * fixup * fixup: Travis environment variable syntax * fixup: Buffer->begin * fixup: actually run full tests on one config * fixup: add build status badge for Travis 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-09T20:44:59+00:00 Tim Foley tfoley@nvidia.com 2017-06-09T18:34:21+00:00 urn:sha1:fcf83dbf9effab3bd98bad2b83b2468b7eb05cfd