Closed balazske closed 5 years ago
I could not find out why the ASTMerge/interface test fails in Jenkins. (Test must be tried with sanitizer enabled?)
Yes, it failed with a clang which has the sanitizers enabled. But, I think the error would be different in case of memory corruption reported by asan.
Does it pass with GCC, if you skip the failing step of the pipeline?
On my computer the tests pass with normal GCC debug and release build (full check-clang). It passes with release sanitizer build using current clang compiler too.
I have cleaned up the workspace of the pr job (deleted the build and source dirs), lets see what happens now.
run tests
OK I will split the patch.
Related: #594
Related: #595
Next: #596
Last part: #598
The changes are made in separate PRs, closing this one.
I could not find out why the ASTMerge/interface test fails in Jenkins. (Test must be tried with sanitizer enabled?)