That's my fault.I do not notice that I called 'make check' in my build script. Got it.
@Bryan For the container usage, I think I should not change the config of a running TS server run in a container. So it is safe to call traffic_server when running TS in a contaner, right? @Fieck I cannot understand the python script. If I call 'trafficeserver', i need it to run in the foreground in a container. I do not know how the script accomplishes it. Thanks all of you! Guofeng On Fri, Apr 19, 2019 at 6:36 AM Bryan Call <[email protected]> wrote: > There shouldn’t be anything triggering it unless you are running make test > or make check. Maybe the Makefile got modified and was running the test or > check target after all. > > There are also regression tests that are built into the traffic_server > binary and those are run with traffic_server -R 1, but it doesn’t sound > like you are talking about the regression tests. > > -Bryan > > > > On Apr 18, 2019, at 9:50 AM, Jason Yang <[email protected]> > wrote: > > I think I had the problem too. > There was a few times, ATS always ran tests during/after make. I don’t > know why, but the problem disappeared for me mysteriously after that. So I > guess there might be something triggering this? > > > Jason > > > On Apr 18, 2019, at 12:47, Leif Hedstrom <[email protected]> wrote: > > > > On Apr 18, 2019, at 10:35 AM, Bryan Call <[email protected]> wrote: > > The tests shouldn’t run by default when you do a make or make all. They > only run if you run make test or make check. > > > Yeh. > > Maybe he’s asking how to not build the tests that are in traffic_server? > There’s a config option for that, e.g. > > % ./configure --disable-tests > > > That just removes the code from the binary, making it a tiny bit smaller > (I don’t know if many people bothers with this :). > > — Leif > > > > >
