Bug 482864 – app-benchmarks/sysbench - FATAL: failed to get database capabilities!"

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Todd 2013-08-29 01:51:50 UTC]

Created attachment 357282 [details, diff]
sysbench/drivers/mysql/drv_mysql.c patch

Errors running sysbench mysql tests:
ALERT: Error: failed to determine table 'sbtest' type!
ALERT: MySQL error: 
FATAL: failed to get database capabilities!

The following patch (also attached) claims to solve the issue:
https://gist.github.com/ericliang/2964943

[Comment 1 Pacho Ramos 2016-01-27 21:41:58 UTC]

I cannot find sysbench upstream any more... maybe this should be treecleaned instead :|

[Comment 2 Tomáš Mózes 2016-06-08 11:33:08 UTC]

Upstream is not dead:
https://github.com/akopytov/sysbench/tree/1.0

It's going to be active:
http://kaamos.me/blog//2016/03/08/towards-sysbench-1.0-history.html

[Comment 3 Tomáš Mózes 2016-06-08 13:43:13 UTC]

https://github.com/gentoo/gentoo/pull/1628

[Comment 4 Pacho Ramos 2016-06-11 20:59:29 UTC]

Do you want to proxy maintain this? Also, the pull request doesn't fix this, it only affects to the live ebuild :/

[Comment 5 Tomáš Mózes 2016-06-12 05:26:32 UTC]

Yes, I will proxy maintain this.

Regarding this bug, it's really old and I don't even know how to reproduce. I believe the author will release version 1.0 soon and we can drop this oldie.

[Comment 6 Pacho Ramos 2016-06-12 08:04:29 UTC]

I will CC proxy-maint people then

Regarding the release of a new version, I would try to directly contact upstream suggesting that and, if they don't do, maybe packaging a snapshot would be the best option

[Comment 7 Tomáš Mózes 2016-06-12 08:38:53 UTC]

From the author:
https://github.com/akopytov/sysbench/issues/48

"I understand the important of release tags, but a more general issue is that there's no releases to tag yet. I'm going to create regular tagged and versioned releases starting from sysbench 1.0, please be patient."

I'll wait some time and if nothing else, we will take a snapshot from 1.0 branch.

[Comment 8 Pacho Ramos 2016-08-21 12:37:54 UTC]

I would take a snapshot then

[Comment 9 Pacho Ramos 2016-10-08 10:52:13 UTC]

Any news on this?

[Comment 10 Tomáš Mózes 2016-10-10 04:52:29 UTC]

Added on comment on github: https://github.com/akopytov/sysbench/issues/1

If nothing happens, where can we put the snapshot?

[Comment 11 Pacho Ramos 2016-10-12 19:08:39 UTC]

Isn't github providing snapshots per commit like gitweb? If I don't misremember even vcs-snapshot.eclass was helping to use them :/

Other option would be to store the tarball in the dev account of some member of proxy maintainers team :|

[Comment 12 Tomáš Mózes 2016-10-13 05:37:56 UTC]

(In reply to Pacho Ramos from comment #11)
> Isn't github providing snapshots per commit like gitweb? If I don't
> misremember even vcs-snapshot.eclass was helping to use them :/

Yes, you are right, I never used that feature but it's possible. Something like:

https://github.com/akopytov/sysbench/archive/21029a6b42dd94faad3a56e256985027fe635db4.zip

[Comment 13 Tomáš Mózes 2016-10-17 08:38:17 UTC]

https://github.com/gentoo/gentoo/pull/2578

[Comment 14 Tomáš Mózes 2016-10-28 05:28:45 UTC]

Fixed in the latest snapshot.