text stringlengths 0 88 |
|---|
ATTACHED_FILES |
-------------- |
Attach a list of files to a dashboard submission. |
Set this property to a list of files that will be encoded and |
submitted to the dashboard as an addition to the test result. |
ATTACHED_FILES_ON_FAIL |
---------------------- |
Attach a list of files to a dashboard submission if the test fails. |
Same as :prop_test:`ATTACHED_FILES`, but these files will only be |
included if the test does not pass. |
COST |
---- |
This property describes the cost of a test. When parallel testing is |
enabled, tests in the test set will be run in descending order of cost. |
Projects can explicitly define the cost of a test by setting this property |
to a floating point value. |
When the cost of a test is not defined by the project, |
:manual:`ctest <ctest(1)>` will initially use a default cost of ``0``. |
It computes a weighted average of the cost each time a test is run and |
uses that as an improved estimate of the cost for the next run. The more |
a test is re-run in the same build directory, the more representative the |
cost should become. |
DEPENDS |
------- |
Specifies that this test should only be run after the specified list of tests. |
Set this to a list of tests that must finish before this test is run. The |
results of those tests are not considered, the dependency relationship is |
purely for order of execution (i.e. it is really just a *run after* |
relationship). Consider using test fixtures with setup tests if a dependency |
with successful completion is required (see :prop_test:`FIXTURES_REQUIRED`). |
Examples |
~~~~~~~~ |
.. code-block:: cmake |
add_test(NAME baseTest1 ...) |
add_test(NAME baseTest2 ...) |
add_test(NAME dependsTest12 ...) |
set_tests_properties(dependsTest12 PROPERTIES DEPENDS "baseTest1;baseTest2") |
# dependsTest12 runs after baseTest1 and baseTest2, even if they fail |
DISABLED |
-------- |
.. versionadded:: 3.9 |
If set to ``True``, the test will be skipped and its status will be 'Not Run'. A |
``DISABLED`` test will not be counted in the total number of tests and its |
completion status will be reported to CDash as ``Disabled``. |
A ``DISABLED`` test does not participate in test fixture dependency resolution. |
If a ``DISABLED`` test has fixture requirements defined in its |
:prop_test:`FIXTURES_REQUIRED` property, it will not cause setup or cleanup |
tests for those fixtures to be added to the test set. |
If a test with the :prop_test:`FIXTURES_SETUP` property set is ``DISABLED``, |
the fixture behavior will be as though that setup test was passing and any test |
case requiring that fixture will still run. |
ENVIRONMENT |
----------- |
Specify environment variables that should be defined for running a test. |
Set to a :ref:`semicolon-separated list <CMake Language Lists>` list |
of environment variables and values of the form ``MYVAR=value``. |
Those environment variables will be defined while running the test. |
The environment changes from this property do not affect other tests. |
ENVIRONMENT_MODIFICATION |
------------------------ |
.. versionadded:: 3.22 |
Specify environment variables that should be modified for running a test. Note |
that the operations performed by this property are performed after the |
:prop_test:`ENVIRONMENT` property is already applied. |
Set to a :ref:`semicolon-separated list <CMake Language Lists>` of |
environment variables and values of the form ``MYVAR=OP:VALUE``, |
where ``MYVAR`` is the case-sensitive name of an environment variable |
to be modified. Entries are considered in the order specified in the |
property's value. The ``OP`` may be one of: |
- ``reset``: Reset to the unmodified value, ignoring all modifications to |
``MYVAR`` prior to this entry. Note that this will reset the variable to |
the value set by :prop_test:`ENVIRONMENT`, if it was set, and otherwise |
to its state from the rest of the CTest execution. |
- ``set``: Replaces the current value of ``MYVAR`` with ``VALUE``. |
- ``unset``: Unsets the current value of ``MYVAR``. |
- ``string_append``: Appends singular ``VALUE`` to the current value of |
``MYVAR``. |
- ``string_prepend``: Prepends singular ``VALUE`` to the current value of |
End of preview. Expand in Data Studio
Simulation runtime: the third-party half of the AVSim data generation package
This repository holds the third-party runtime of the Simulation data generation package, version 3: the pieces the pipeline needs that were not written by the authors. It contains no code and no data of the authors. It is not usable on its own: the private half of the package, AVSim/simulation, downloads this repository into the same directory at a pinned revision with its fetch_runtime.sh script and verifies it against MANIFEST.runtime.sha256.
Contents:
sifs/isaac.sif: the render container, NVIDIA Isaac Sim 5.1 with its Omniverse Kit runtime and the python packages of the kit process.toolchain/: the NVIDIA CUDA 12.6.3 toolkit installer, a rootless Apptainer installation, a standalone CPython 3.11, CMake 3.27.9.omniverse_mirror/andmaterials/: mirrors of NVIDIA Omniverse content (Isaac Sim environments and SimReady props) and the MDL materials they reference; every mirror carries itsmirror_manifest.jsonwith the upstream source.code/third_party/omniverse_assets/andcode/third_party/vMaterials_2/: NVIDIA Omniverse assets and the NVIDIA vMaterials 2 library, at the paths the code tree expects.code/src/simulation/assets/sources/<id>/source/andstore_v2/<id>/source/: the object source meshes extracted from the mirrored NVIDIA assets and from the YCB object set.envs/: the python packages injected into the kit process, static builds of ffmpeg and ffprobe, a cmake wrapper, the pip freeze of the host-side environment;wheels/: the host-side python packages;vendor/: Eigen and libigl for the offline solver build.
License: the components keep the licenses of their upstreams (NVIDIA Software License Agreement and NVIDIA CUDA End User License Agreement for the container, the toolkit and the vMaterials library; the NVIDIA Omniverse asset terms for the mirrored content; CC BY 4.0 for the YCB objects; BSD, MIT, PSF, MPL 2.0, LGPL and GPL for the open-source tools and packages). The most restrictive of them, the NVIDIA proprietary software license, governs this repository as a whole.
- Downloads last month
- -