Conversation
|
Hello, we have our CI system already: http://ci.redis.io/ :-) But it does not run on RHLE 5 so we did not detected that particular build error. |
|
Wow, it's good ^^ |
|
Thanks, also not directly linked but may interest you:
Those are automatically generated multiple times every day |
|
Wow, awesome. Why I don't know about them yet. ^^ thank you. it is very useful information for me. |
|
I have a question about redis coverage. You are just enhancing redis coverage through tcl/tk? |
|
Yes, writing more Tcl tests in the test suite basically. The coverage in the linked pages is the result of the execution of the Redis test suite (written in Tcl). |
|
Thank you for your answer. I hope me increase redis test coverage. Thank you ^^ |
Related to redis#734 and redis#858 Signed-off-by: Ping Xie <[email protected]>
Optimize XXH3_accumulate_512_neon
I think it is better to apply travis ci to redis to prevent build error before releasing.
travis-ci is a free ci server.
and you will be able to check build status after commit.
but in redis, "make test" took too long time, so I just applied
"scirpt: make"
if you decide to use travis-ci . you have to register in travis-ci(just using github account)
and turn on your project compile