yade-dev team mailing list archive

[Jerome Duriez <jerome.duriez@xxxxxxxxx>]

Hi,

> you can see in the pipeline
Is there yet an example in recent pipeline jobs ? I looked at that job 
<https://gitlab.com/yade-dev/trunk/-/jobs/347833875> from ASAN merge 
request #331 and could not see anything new.
What's the exact workflow ? Running --test and --check and look for some 
error/warning messages ? If there is one => problems, if there is none 
=> no problems ?


Thanks !

Jérôme

------
Chargé de Recherche / Research Associate
Irstea, RECOVER
3275 route Cezanne – CS 40061 13182 Aix-en-Provence Cedex 5 FRANCE
+33 (0)4 42 66 99 21
www.irstea.fr/duriez

On 11/11/2019 18:39, Anton Gladky wrote:
> Dear Yade developers,
>
> last weekend [1] we enabled the new target in the pipeline: make_asan.
> Also the new Yade option ENABLE_ASAN was added into the Cmake.
> Documentation is updated correspondingly.
>
> ASAN - is the abbreviation of AddressSanitizer [2] - memory error detector,
> which finds heap corruptions, memory overflows etc.
>
> Generally, Yade is being compiled with special compiler flags and then
> '-test' and
> '--check' steps are being executed. If you add a new engine or any other
> class, which is executed by "--test" or "--check" step, you can see in
> the pipeline, whether  your code is not doing something weird with the
> memory.
>
> It can help to increase the software stability, correctness of the results
> and general quality of the software.
>
> If you see some problems with this step in the pipeline - please let me know.
>
> [1] https://gitlab.com/yade-dev/trunk/merge_requests/331
> [2] https://github.com/google/sanitizers/wiki/AddressSanitizer
>
> Best regards
>
> Anton
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp