| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
It's no longer needed because crucible-ls-tests now lists *all* tests.
|
|
|
|
|
|
Python with opencv provides us a lot more control of what's going on and
its interface shouldn't change arbitrarily.
|
|
From crucible-run man page:
--junit-xml=<junit-xml-file>
Write JUnit XML to the given file.
The option is just a stub. It doesn't do anything yet but print
a FINISHME.
|
|
|
|
|
|
|
|
|
|
It used to be that, of glslang couldn't compile a shader, we would
gracefully fall back to glsl. However, since we no longer support GLSL in
our driver, this isn't really an option anymore. Therefore, it makes no
sense to handle these errors gracefully and we should instead let the test
author know that we can't compile it.
|
|
|
|
crucible-report crashed with an assertion if the two run's set of tests
differed. This made it impossible to compare results from two Crucible
revisions if tests were added/deleted/renamed between those revisions.
|
|
This should make it just a little easier to seee what's going on in test
results. And colored results are far cooler than black-and-white ones.
|
|
|
|
The shaderc project from Google (https://github.com/google/shaderc)
provides a glslang wrapper program called 'glslc' that has a much improved
command-line interfacce. In particular, we no longer have to read and
write files with specific names to a temporary directory in order to
compile shaders. This should make the build process substantially smoother
at the expense of having to install a tool.
|
|
|
|
|
|
|
|
crucible-dump-image dumps an image file to an ASCII table that displays
each pixel's bytes.
This proved immensely useful when inspecting stencil buffers.
|
|
|
|
Used to control whether the runner starts each test in its own process
or its own thread.
|
|
If separate cleanup threads are disabled, then each test's cleanup
handlers will run inside the test's "result" thread. If enabled, then
the "result" thread will create a new thread in which to run the cleanup
handlers.
Tested by:
* Inspecting `crucible run --no-separate-cleanup-threads
func.draw-indexed` in gdb.
* Confirming the result totals are the same with and without
--no-separate-cleanup-threads.
|
|
This controls whether the test runner's master process forks or not.
Tested with:
* crucible run --no-fork func.draw-indexed
Test passes.
* crucible run --no-fork
Test func.cmd-buffer.small-secondaries crashes the testrun.
|
|
Import the jpegs files, taken from my camera:
grass-2014x1536.jpg
pink-leaves-3264x2448.jpg
Use ImageMagick at buildtime to generate grayscale PNG images from the
JPEG files. Generate an image for each miplevel, beginning with the
base level extent 2048x1024.
Images will be used to fill depth and stencil miptrees.
|
|
|
|
|
|
compile.
|
|
This way compute shaders are valid.
|
|
|
|
|
|
By default, we'll prefer the GLSL source for now.
|
|
|
|
Add options --dump and --no-dump to crucible-run. The options enable or
disable duming images into Crucible's data directory. Also define a new
test function, t_dump_image(), that respects the cmdline option. The
function is unused for now, but will be used in follow-up patches.
|
|
|
