[Groonga-mysql-commit] Still Failing: mroonga/mroonga#2096 (master - d1bedce)

Back to archive index

Travis CI build****@travi*****
Sun Apr 26 14:13:13 JST 2015


Build Update for mroonga/mroonga
-------------------------------------

Build: #2096
Status: Still Failing

Duration: 8 minutes and 1 second
Commit: d1bedce (master)
Author: Kouhei Sutou
Message: storage: support --auto-repair by mysqlcheck

It's an experimental feature.

If any data object such as table or column are broken (= lock is
remained), can't be repaired. If index columns are only broken (lock is
remained), Mroonga can recover the database.

Crashed check logic is just finding any existing lock. Because lock is
remained when Mroonga is crashed while updating. If other process opens
database for Mroonga, Mroonga may detect lock that is valid. You should
not use this feature when other process opens Mroonga database.

View the changeset: https://github.com/mroonga/mroonga/compare/75315b29b145...d1bedce487a0

View the full build log and details: https://travis-ci.org/mroonga/mroonga/builds/60070916

--

You can configure recipients for build notifications in your .travis.yml file. See http://docs.travis-ci.com/user/notifications


-------------- next part --------------
An HTML attachment was scrubbed...
Download 



More information about the Groonga-mysql-commit mailing list
Back to archive index