[
https://issues.apache.org/jira/browse/TS-1834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13637270#comment-13637270
]
Leif Hedstrom commented on TS-1834:
-----------------------------------
It's definitely a problem with the test, and not logstats. The issue is passing
the relative path argument to logstats. I don't know why not all build systems
has this problem, mine does and so does the build bots. There are two ways to
fix this:
1) Make the logstats test script turn the relative path argument to an absolute
path (using e.g. readlink -f). This might break on some platforms though, e.g.
OSX doesn't seem to have the same syntax on Linux, so I'd imagine it breaks on
FBSD too.
2) Fix logstats such that it can handle relative paths.
> make test fails on logstats tests
> ---------------------------------
>
> Key: TS-1834
> URL: https://issues.apache.org/jira/browse/TS-1834
> Project: Traffic Server
> Issue Type: Bug
> Components: Build
> Reporter: Leif Hedstrom
> Assignee: James Peach
>
> Files /tmp/logstats.jvWidH and ../../../proxy/tests/logstats.json differ
> FAIL: tests/test_logstats_json
> FAIL: tests/test_logstats_summary
> Diff failures are in
> http://paste.fedoraproject.org/8018/88145136
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
