lyskomd-qa July 2004

lyskomd-qa@lists.lysator.liu.se

1 participants
4 discussions

[Bug 64] aux-item-def parser: bad coverage by testsuite
by bugzilla-daemon＠cvs.lysator.liu.se 21 Jul '04

21 Jul '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=64 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Keywords|inpro | Resolution| |FIXED ------- Additional Comments From ceder(a)lysator.liu.se 2004-07-21 09:29 ------- Assuming that this means coverage of aux-item-def-parse.y, this is now more or less done. There are four uncovered lines. Three of them are unreachable code as long as no bugs creep in. The fourth line seems to be an error in gcov/bison/gcc, as the line actually is run, but the run count is reported as 0. This is a one-line statement in the grammar, the one with the comment "Empty" below: action : action CREATE { $$ = $1 | AUX_ITEM_ADD_ON_CREATE; } | action MODIFY { $$ = $1 | AUX_ITEM_ADD_ON_MODIFY; } | /* Empty */ { $$ = 0; } ; Adding a call to kom_log() on that line will still report a 0 run count, but the message will be printed to the log! Are there any other parts of the aux-item-def parser that needs more coverage? Please open a new bug in that case. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 64] aux-item-def parser: bad coverage by testsuite
by bugzilla-daemon＠cvs.lysator.liu.se 19 Jul '04

19 Jul '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=64 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Keywords| |inpro ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 985] New async: text marked as read
by bugzilla-daemon＠cvs.lysator.liu.se 18 Jul '04

18 Jul '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=985 ceder(a)lysator.liu.se changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED Target Milestone|Future |2.1.3 ------- Additional Comments From ceder(a)lysator.liu.se 2004-07-18 22:49 ------- Something similar to design 1 is now implemented and committed. See Protocol-A.texi for the details. I guess this means that 2.1.3 will actually be called 2.2.0... ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

[Bug 1382] New: Async message should be sent when membership changes
by bugzilla-daemon＠cvs.lysator.liu.se 15 Jul '04

15 Jul '04

http://bugzilla.lysator.liu.se/show_bug.cgi?id=1382 Summary: Async message should be sent when membership changes Product: lyskomd Version: 2.1.2 Platform: PC OS/Version: All Status: NEW Severity: enhancement Priority: P2 Component: server AssignedTo: ceder(a)lysator.liu.se ReportedBy: byers(a)lysator.liu.se QAContact: lyskomd-qa(a)lists.lysator.liu.se An asynchronous message should be sent when any field of a membership changes. The message should be sent to all sessions belonging to the person who owns the membership except (imo) the session that initiated the change. As far as I am concerned, async-new-membership would be OK, but a dedicated message that sends the entire membership WITHOUT read-ranges would probably be nicer as there is some risk that clients depend on async-new-membership only being sent when a membership is actually added. ------- You are receiving this mail because: ------- You are the QA contact for the bug, or are watching the QA contact.

1 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

lyskomd-qa July 2004