[Qa-jenkins-scm] [jenkins.debian.net] 04/06: reproducible: proper db design is the answer and then e3e241e can be reverted again

[Holger Levsen]

This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch master
in repository jenkins.debian.net.

commit 6e14bf653cb3f6dcb5ed03baf8d093331f45fba1
Author: Holger Levsen <holger at layer-acht.org>
Date:   Sat Sep 26 12:18:24 2015 +0200

    reproducible: proper db design is the answer and then e3e241e can be reverted again
---
 TODO | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/TODO b/TODO
index 98a93d6..e8de116 100644
--- a/TODO
+++ b/TODO
@@ -224,7 +224,9 @@ properties:
 ** a reproducible_log_grep_by_sql.(py|sh) would be nice, to only grep in packages with a certain status (build in the last X days)
 ** adopt usertag script from pkg-apparmor to notify us about new usertagged bugs automatically
 ** use reprepro and snapshot (reprepro gen-snapshot) on alioth to speed up our repo, maybe. maybe we'll just be in sid soon :-)
-** .db: stats_build table should have package ids, not just src+suite+arch as primary key
+** database issues
+*** stats_build table should have package ids, not just src+suite+arch as primary key
+*** builder column of schedule table should not be used for state-handling of _remote_scheduler.py (by setting it to 'TBD'), thus e3e241e should be reverted (also check for 'TBD' elsewhere) and this be implemented differently
 
 * missing tests:
 ** variation in kernel

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/qa/jenkins.debian.net.git