Matthias Felleisen writes:
>> On Nov 14, 2019, at 3:05 AM, Paulo Matos <[email protected]> wrote: > > > Let me echo Robby with 1000*thanks :) > > Thanks. >> >> 4. Builds once again all the variants with the llvm static analyser and >> keeps a record of the failures (for example: >> https://gitlab.com/racket/racket/-/jobs/350271564/artifacts/file/scan-report_mmm/2019-11-14-032030-5552-1/index.html). >> This step requires us to build LLVM with Z3 enabled so we can use the >> work from ICSE'19[7]. > > > Is this about “flaky tests”? Jon Bell at George Mason (DC) has done work on > this idea that could possibly supplement or replace this: > https://www.jonbell.net/icse18-deflaker.pdf > Thanks for the reference. I will take a look. The work for ICSE'19 was very good because the amount of reasoning the static analyzer was doing was limited generating quite a few false positives during code analysis - unrelated to testing. With Z3, given all the warning generated by the static analyzer Z3 is called trying to find a counter example. If such counter example is found, then the warning is a false positive and not shown to the user. This was integrated into LLVM early this year but for licensing reasons, LLVM cannot be built with Z3 integration enabled. We therefore build it and cache the result so we don't need to rebuild it for every commit. Kind regards, -- Paulo Matos -- You received this message because you are subscribed to the Google Groups "Racket Developers" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/racket-dev/87bltd5c74.fsf%40linki.tools.
