[ 
https://issues.apache.org/jira/browse/TS-3657?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14571376#comment-14571376
 ] 

Leif Hedstrom commented on TS-3657:
-----------------------------------

Yeah, if we can change tsqa such that it runs on a given build (instead of 
making its own build) doing these sort of special builds is very easy in 
Jenkins. I'd simply add an "asan" alternative to the matrix builds. Having tsqa 
run on every build, or at least some select builds, would make things a lot 
nicer. We have two particular set of jobs (latest Fedora and latest Ubuntu), 
which have multiple build VMs. So they are very capable of running additional 
"jobs" (and if needed, we can add more build VMs to those two targets).

In addition, it might make sense to have some framework for marking a 
particular tsqa test as "fast" or "slow". Such that for the per-commit builds, 
we'd only run the "fast" tests (or, the !slow ones), and then nightly or hourly 
or something, we run the big tsqa job on the dedicated QA boxes (which is where 
tsqa runs now).

Note that we're running pretty tight on resources on RackSpace, we have a 
little wiggle room still, but it's not unlimited. :). And there's real value in 
making sure the regular (commit triggered builds) finishes in reasonable time 
(~10-20 minutes for all jobs within a matrix).

> Run tsqa with ASAN (and perhaps a TSAN) builds
> ----------------------------------------------
>
>                 Key: TS-3657
>                 URL: https://issues.apache.org/jira/browse/TS-3657
>             Project: Traffic Server
>          Issue Type: Improvement
>          Components: tsqa
>            Reporter: Leif Hedstrom
>            Assignee: Thomas Jackson
>             Fix For: sometime
>
>
> We should just enable ASAN (when available) on the tsqa run(s). We will trip 
> on some other stuff as well, I've filed some other Jira's on that issue.
> But, running all of tsqa through ASAN builds would be very useful. On the CI, 
> you would have to use a different gcc. Specifically:
> {code}
> CC="/opt/gcc/bin/gcc"; export CC
> CXX="/opt/gcc/bin/g++"; export CXX
> CFLAGS="-fsanitize=address -fno-omit-frame-pointer"; export CFLAGS
> CXXFLAGS="-fsanitize=address -fno-omit-frame-pointer"; export CXXFLAGS
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Reply via email to