Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/372
---
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 feature
GitHub user maskit opened a pull request:
https://github.com/apache/trafficserver/pull/372
TS-4063: Add regression tests for HPACK Huffman
https://issues.apache.org/jira/browse/TS-4063
You can merge this pull request into a Git repository by running:
$ git pull https
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/364
---
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 feature
benefit for variable size objects increases.
The regression tests at 1MB 16MB and 256MB, but with relatively small
objects (16KB) so the results should be applicable to more popular production
size RAM caches in the GB(s) range.
---
If your project is set up for it, you can reply to this
Github user jplevyak commented on the pull request:
https://github.com/apache/trafficserver/pull/364#issuecomment-162119403
RPRINT ram_cache: RamCache LRU Fixed Size Hit Rate 0.581543
RPRINT ram_cache: RamCache LRU Variable Size Hit Rate 0.567505
RPRINT ram_cache: RamCache LRU N
GitHub user jplevyak opened a pull request:
https://github.com/apache/trafficserver/pull/364
TS-4053: Add regression tests for hit rate and size for the RAM caches,
Tune up CLFUS.
You can merge this pull request into a Git repository by running:
$ git pull https
Github user asfgit closed the pull request at:
https://github.com/apache/trafficserver/pull/328
---
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 feature
GitHub user masaori335 opened a pull request:
https://github.com/apache/trafficserver/pull/328
TS-4001: Separate Regression Tests for HPACK from HTTP2.cc
[TS-4001](https://issues.apache.org/jira/browse/TS-4001)
You can merge this pull request into a Git repository by running
On Oct 26, 2013, at 10:42 PM, James Peach wrote:
> Hi all,
>
> The problem with the failing tests in jeknins is the ProxyConfig_Set and
> ProxyConfig_Release tests. ProxyConfig_Set isn't failing but it exhibits the
> same behaviour as ProxyConfig_Release so it would be failing if it were more
Hi all,
The problem with the failing tests in jeknins is the ProxyConfig_Set and
ProxyConfig_Release tests. ProxyConfig_Set isn't failing but it exhibits the
same behaviour as ProxyConfig_Release so it would be failing if it were more
carefully written.
The root cause of the failure is that we
it before, it really depends on what you are doing the
regression tests for. It varies wildly, and the best bet is to copy and
paste from a similar existing test. Things which changes HTTP SM and how
we handle transactions are the most "complicated" ones, but there are
plenty of existing test
-1137
> >>
> >> Could someone of the two or three people who know how this
> >> actually works, document the process of writing regression
> >> tests.
> >>
> >> I'm also be perfectly fine if you do this informally in reply
> >>
regression
tests.
I'm also be perfectly fine if you do this informally in reply
to this email! I or someone else who wants to get to know our
docs a bit more will then put it in a fine format on the site.
It's pretty easy to get something basic working ... I copied one of amc's and
On May 3, 2012, at 2:02 PM, Igor Galić wrote:
>
> Hey folks,
>
> Until we have this Bug here fixed:)
>
> https://issues.apache.org/jira/browse/TS-1137
>
> Could someone of the two or three people who know how this
> actually works, document the process of writing r
Hey folks,
Until we have this Bug here fixed:)
https://issues.apache.org/jira/browse/TS-1137
Could someone of the two or three people who know how this
actually works, document the process of writing regression
tests.
I'm also be perfectly fine if you do this informally in reply
to
Is there an output of the result of the regression tests with each build?
It would be nice to see it somewhere here:
http://ci.apache.org/builders/tserver-trunk
Cheers,
Andrew
On Mon, Dec 6, 2010 at 9:33 PM, Leif Hedstrom wrote:
> Hi all,
>
> after a lot of work from several of the de
It has a consistent grammar and we can change it if there is a standard we
should be using.
On Dec 8, 2010 5:15 PM, "Andrew Hsu" wrote:
regression_tests:software_engineering_process::fiber:digestive_track
I found the output under the "compile_4" step of the build. Could we rename
this step to
gression on commits, on the tserver-trunk bot. The expectations is
> that going forward, failed regression tests should be considered as breaking
> 'trunk', and should be fixed asap.
>
> Also, everyone should start thinking about what new regression tests needs
> to be adde
Hi all,
after a lot of work from several of the dev members, our regression
tools now completes with a success. Gavin has added support for the CI
buildbot to run the regression on commits, on the tserver-trunk bot. The
expectations is that going forward, failed regression tests should be
Sure. It will be a day or two, I want to get the capabilities put to
bed first.
Thursday, May 20, 2010, 11:23:00 AM, you wrote:
> Hi Alan,
> Can you file this as a Jira Ticket and provide as much as possible the
> necessary repro environment, code line, etc.
> thanks,
> -George
n M. Carroll wrote:
>>> I am trying to run regression tests (traffic_server -R 1) but it segfaults
>>> in Cache_part. According to TS-74
>>>
>>> "for the 'Cache_part' regression test to pass a cache storage has to be
>>> allocated>
Yes.
Wednesday, May 19, 2010, 9:28:42 PM, you wrote:
> On 05/19/2010 07:33 PM, Alan M. Carroll wrote:
>> I am trying to run regression tests (traffic_server -R 1) but it segfaults
>> in Cache_part. According to TS-74
>>
>> "for the 'Cache_part' regress
On 05/19/2010 07:33 PM, Alan M. Carroll wrote:
I am trying to run regression tests (traffic_server -R 1) but it segfaults in
Cache_part. According to TS-74
"for the 'Cache_part' regression test to pass a cache storage has to be allocated>
128MB."
I checked there is
I am trying to run regression tests (traffic_server -R 1) but it segfaults in
Cache_part. According to TS-74
"for the 'Cache_part' regression test to pass a cache storage has to be
allocated > 128MB."
I checked there is a cache.db file that is 144M. Does this reall
ION_RESULT SDK_API_HttpAltInfo: FAILED
TS-172 REGRESSION_RESULT SDK_API_HttpTxnTransform: FAILED
TS-173 REGRESSION_RESULT SDK_API_HttpTxnCache: FAILED
TS-174 REGRESSION_RESULT SDK_API_HttpHookAdd: FAILED
Note that for the following SDK API regression tests to pass
SDK_API_INKHttpConnectServe
t sure what to do in the case
where the unit / regression test actually wants a real URL, but my +1 would be
to use either www.apache.org or trafficserver.apache.org (and not
www.yahoo.com).
> regression tests returning FAILED status
>
>
>
mple, example.com is
reserved for use in documentation by IETF -- perhaps that's best.
> regression tests returning FAILED status
>
>
> Key: TS-74
> URL: https://issues.apache.org/jira/browse/TS-74
>
;
I'm thinking, but not sure, maybe something like trafficserver.apache.org
(which will be our "domain" when we graduate).
> regression tests returning FAILED status
>
>
> Key: TS-74
>
ION_RESULT SDK_API_HttpTxnTransform: FAILED
REGRESSION_RESULT SDK_API_HttpTxnCache: FAILED
REGRESSION_RESULT SDK_API_HttpHookAdd: FAILED
Note that for the following SDK API regression tests to pass
SDK_API_INKHttpConnectServerIntercept
SDK_API_INKHttpConnec
[
https://issues.apache.org/jira/browse/TS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul reassigned TS-74:
-
Assignee: George Paul
> regression tests returning FAILED sta
[
https://issues.apache.org/jira/browse/TS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul updated TS-74:
--
Fix Version/s: 2.0.0a
Environment: All
Affects Version/s: 2.0.0a
> regression tests return
[
https://issues.apache.org/jira/browse/TS-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
George Paul updated TS-74:
--
Attachment: ts_R1_out2.txt
svnversion: 905506
Trunk:
Regression Tests passed: 254
Regression Tests failed: 9
[
https://issues.apache.org/jira/browse/TS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak resolved TS-73.
Resolution: Fixed
revision 888434
> SEGV in regression tests (regression
regression tests returning FAILED status
Key: TS-74
URL: https://issues.apache.org/jira/browse/TS-74
Project: Traffic Server
Issue Type: Bug
Components: Cleanup
Reporter: John
[
https://issues.apache.org/jira/browse/TS-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Plevyak updated TS-73:
---
Attachment: ts-regressions-jp-v2.patch
fix
> SEGV in regression tests (regression
SEGV in regression tests (regression -R1)
-
Key: TS-73
URL: https://issues.apache.org/jira/browse/TS-73
Project: Traffic Server
Issue Type: Bug
Components: Core
Reporter: John
36 matches
Mail list logo
