Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
clang-analyzer build *successful*!
https://ci.trafficserver.apache.org/job/clang-analyzer-github/319/
---
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/1299
Linux build *successful*!
https://ci.trafficserver.apache.org/job/linux-github/1650/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
FreeBSD11 build *successful*!
https://ci.trafficserver.apache.org/job/freebsd-github/1756/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Intel CC build *successful*!
https://ci.trafficserver.apache.org/job/icc-github/187/
---
If your project is set up for it, you can reply to this email and have your
reply appear on
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
AU check *successful*!
https://ci.trafficserver.apache.org/job/autest-github/58/
---
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/1299
RAT check *successful*!
https://ci.trafficserver.apache.org/job/RAT-github/74/
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
clang format *successful*!
https://ci.trafficserver.apache.org/job/clang-format-github/61/
---
If your project is set up for it, you can reply to this email and have your
reply appear
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/226/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/94/ 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/1299
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1558/ 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/1299
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1662/ 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/1299
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/222/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1554/ 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/1299
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1658/ 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/1299
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/216/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/215/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/linux-github/1548/ 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/1299
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1652/ 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/1299
Intel CC build *failed*! See
https://ci.trafficserver.apache.org/job/icc-github/84/ 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/1299
Intel CC build *successful*! See
https://ci.trafficserver.apache.org/job/icc-github/83/ 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/1299
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1651/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user persiaAziz commented on the issue:
https://github.com/apache/trafficserver/pull/1299
@SolidWallOfCode please review
---
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 SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1299
You shouldn't need to change further methods. At worse, you could pass
`"%s", internal_msg_buffer` as the arguments.
---
If your project is set up for it, you can reply to this
Github user persiaAziz commented on the issue:
https://github.com/apache/trafficserver/pull/1299
hmm, we need to remove the usage of varargs from all subsequent methods if
we pass the internal message buffer. Looking at the code and the fail output of
regression test, we can not pass
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
clang-analyzer build *successful*! See
https://ci.trafficserver.apache.org/job/clang-analyzer-github/56/ for details.
---
If your project is set up for it, you can reply to this email
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Linux build *failed*! See
https://ci.trafficserver.apache.org/job/linux-github/1385/ 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/1299
FreeBSD build *failed*! See
https://ci.trafficserver.apache.org/job/freebsd-github/1492/ for details.
---
If your project is set up for it, you can reply to this email and have your
Github user SolidWallOfCode commented on the issue:
https://github.com/apache/trafficserver/pull/1299
After talking to @persiaAziz about this I think the best approach is to
remove the file `char const*` argument and the varargs but check for
`internal_msg_buffer` in `build_response`
Github user atsci commented on the issue:
https://github.com/apache/trafficserver/pull/1299
Linux build *successful*! See
https://ci.trafficserver.apache.org/job/Github-Linux/1184/ 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/1299
FreeBSD build *successful*! See
https://ci.trafficserver.apache.org/job/Github-FreeBSD/1291/ 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/1299
[add to whitelist]
---
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
31 matches
Mail list logo
