[Mono-bugs] [Bug 689490] New: IgnoreList is not being appropriately handled when a rule is run against a type, when the rule enumerates the types members (for instance, AvoidSpeculativeGenerality)
bugzilla_noreply at novell.com
bugzilla_noreply at novell.com
Sun Apr 24 10:45:17 EDT 2011
https://bugzilla.novell.com/show_bug.cgi?id=689490
https://bugzilla.novell.com/show_bug.cgi?id=689490#c0
Summary: IgnoreList is not being appropriately handled when a
rule is run against a type, when the rule enumerates
the types members (for instance,
AvoidSpeculativeGenerality)
Classification: Mono
Product: Mono: Tools
Version: 2.10.x
Platform: 64bit
OS/Version: Windows 7
Status: NEW
Severity: Normal
Priority: P5 - None
Component: Gendarme
AssignedTo: mono-bugs at lists.ximian.com
ReportedBy: ethan_j_brown at hotmail.com
QAContact: mono-bugs at lists.ximian.com
Found By: ---
Blocker: ---
User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/534.29
(KHTML, like Gecko) Chrome/12.0.733.0 Safari/534.29
See test case here:
https://github.com/Iristyle/mono-tools/commit/8469e3a4034cb1f1815cd67a505338cf75a179c7
I have populated the Runner's IgnoreList in roughly the same manner as
SuppressMessageEngine would -- that is, by MetadataToken -- to simulate the
issue. When the rule is run against the type in question, only the type is
examined for rule suppressions. However, the rule itself enumerates methods of
the class but does not check the IgnoreList for those methods in any way during
the process. So even though the type has only 1 method, which should be
ignored, the rule generates a failure on the given type.
There may be other rules that operate in this fashion.
In my production code, I can further verify the test assumptions by applying
the [SuppressMessage] at the class level, and watching the failure disappear.
Reproducible: Always
Steps to Reproduce:
1.Run linked test
2.
3.
Actual Results:
Failure
Expected Results:
DoesNotApply
--
Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
You are the assignee for the bug.
More information about the mono-bugs
mailing list