Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1401
you didn't see this crasher in 7.0.0 right ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1388
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Clang/11/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Clang/10/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user biilmann commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Not this one no. We've seen a crash that looks related in the crash logs
from 7.0.x but it is much rarer and I don't currently have a core-dump of that.
---
If your project is set up for
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/issues/1402
If possible, can you test with 7.0 or 7.1x (branch) and see if it happens
there too ?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1445/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1388
[approve ci] to get the clang-analyzer build
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1388
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1446/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1388
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1339/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
Linux build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1338/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1388
@jablko do we need two commits here? Or can they be squashed?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1381
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1330/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1381
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1437/ for details.
---
If your project is set up for it, you can reply to this email and have your
https://ci.trafficserver.apache.org/job/osx-master/compiler=clang,label=osx,type=release/1370/display/redirect
Github user jablko closed the pull request at:
https://github.com/apache/trafficserver/pull/1397
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the
Github user jablko commented on the issue:
https://github.com/apache/trafficserver/pull/1397
> it seems the checks for hwloc are not done well
How can I reproduce this? I'm not seeing traffic_top getting hwloc:
```
$ ldd -r -u cmd/traffic_top/.libs/traffic_top
Github user jablko commented on the issue:
https://github.com/apache/trafficserver/pull/1398
Oh, and I guess it still requires curses, so maybe leave in
`AM_CONDITIONAL([BUILD_TRAFFIC_TOP], [test "x$ax_cv_curses" = xyes])`?
---
If your project is set up for it, you can reply to this
GitHub user shenzhang920 opened an issue:
https://github.com/apache/trafficserver/issues/1399
Paft of tcp_congestion_control code was erased by push TS-3612
ATS can change the tcp_congestion_control algorithm on both client side and
server side, this functionality was added in 5.x.
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
Linux build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1331/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user jablko commented on the issue:
https://github.com/apache/trafficserver/pull/1398
> Linux build failed!
Try with AC_DEFINE vs. AM_CONDITIONAL:
```M4Sugar
AX_LIB_CURL([7.19], [AC_DEFINE([HAS_CURL], [1], [Define if libcurl >=
7.19.])])
```
---
If
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1438/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1381
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1439/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1398
Testing to see if clang-analyzer builds triggers [approve ci]
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
GitHub user jablko opened a pull request:
https://github.com/apache/trafficserver/pull/1400
traffic_via depends on the PCRE library
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jablko/trafficserver ldadd
Alternatively you
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/5/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
Linux build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1333/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1440/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1381
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1332/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/1/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1332
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/4/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1441/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1334/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1381
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/3/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1392
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/2/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1400
Testing again [approve ci]
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/7/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1336/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1443/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1400
Testing again [approve ci]
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/9/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1337/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1444/ for details.
---
If your project is set up for it, you can reply to this email and have
Github user bryancall commented on the issue:
https://github.com/apache/trafficserver/issues/1401
What does the vc look like?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user biilmann commented on the issue:
https://github.com/apache/trafficserver/issues/1401
Some info on the vc:
```
p vc
$1 = (UnixNetVConnection *) 0x2b9a7802ff10
p vc.closed
$2 = 0
p vc.action_
$3 = {_vptr.Action = 0x788a90 , continuation =
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1442/ for details.
---
If your project is set up for it, you can reply to this email and have
GitHub user biilmann opened an issue:
https://github.com/apache/trafficserver/issues/1401
Segfault in write_to_net_io with 7.1.x
Seeing frequent segfaults when trying 7.1.x on some production traffic.
What happens is that the `MUTEX_TRY_LOCK_FOR` segfaults since
Github user zwoop commented on the issue:
https://github.com/apache/trafficserver/pull/1398
Testing to see if clang-analyzer builds triggers [approve ci]
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
clang-analyzer build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Clang/6/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1398
Linux build *failed*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1335/ for details.
---
If your project is set up for it, you can reply to this email and have your
reply
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1400
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Clang/8/ for details.
---
If your project is set up for it, you can reply to this email and have
GitHub user jaaju opened an issue:
https://github.com/apache/trafficserver/issues/1402
Crash in InactivityCop::check_inactivity with dead HttpSM, ATS 6.2.1
We are seeing this crash in ATS 6.2.1, with http/2 enabled:
```
Program terminated with signal 6, Aborted.
#0
51 matches
Mail list logo
