You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There seems to be a bug in the dawn/dawn/cmake/HasUnstructuredDeps.cmake cmake that disables building and testing of the unstructured integration tests. This line should read:
if (NOT HAS_UNSTRUCTURED_DEPS)
(omitting the DEFINED). This causes the unstructured integration tests to build and run again.
However, re-activating the tests leads to a segfault in the AtlasIntegrationTestCodeGenerate binary, but only on jenkins, and only in the release build. Unfortunately, I was not able to reproduce the problem so far.
The text was updated successfully, but these errors were encountered:
## Technical Description
Introduces vertical (1D) & horizontal fields (2D) for unstructured situations. This required quite extensive changes throughout dawn.
* The horizontal field dimension in `sir::FieldDimensions` is now an optional.
* Vertical fields (1D) introduce a situation where we have a field with no location type. This affected all Validators, as well as the `PassLocalVarType`, which infers location types for local variables
* The unstructured codegens as well as de/serialization of `FieldDimensions` was adapted
## Testing
* New test covering the Validator Changes in `TestUnstructuredDimensionsCheckers`
* New test ensuring the correct working of the code generator in the unstructured integration tests, currently de-activated due to issue #1017
* New `dawn4py` test
## Resolves / Enhances
Fixes#1013
There seems to be a bug in the
dawn/dawn/cmake/HasUnstructuredDeps.cmake
cmake that disables building and testing of the unstructured integration tests. This line should read:(omitting the
DEFINED
). This causes the unstructured integration tests to build and run again.However, re-activating the tests leads to a segfault in the
AtlasIntegrationTestCodeGenerate
binary, but only on jenkins, and only in the release build. Unfortunately, I was not able to reproduce the problem so far.The text was updated successfully, but these errors were encountered: