[SERVER-49363] Triage Coverity Issues for Query code base Created: 08/Jul/20  Updated: 27/Oct/23  Resolved: 09/Sep/20

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Task Priority: Major - P3
Reporter: Cristopher Stauffer Assignee: James Wahlin
Resolution: Gone away Votes: 0
Labels: qopt-team
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Related
related to SERVER-50818 Coverity analysis defect 114987: Wrap... Closed
related to SERVER-50826 Coverity analysis defect 111811: Unch... Closed
related to SERVER-50828 Coverity analysis defect 112053: Unch... Closed
related to SERVER-50829 Coverity analysis defect 114409: Redu... Closed
related to SERVER-50830 Coverity analysis defect 114690: Unch... Closed
related to SERVER-50831 Coverity analysis defect 114887: Unin... Closed
related to SERVER-50832 Coverity analysis defect 115076: Unin... Closed
related to SERVER-50833 Coverity analysis defect 115713: Unch... Closed
related to SERVER-50834 Coverity analysis defect 115718: Unin... Closed
related to SERVER-50836 Coverity analysis defect 115738: Unin... Closed
related to SERVER-50838 Coverity analysis defect 115741: Unch... Closed
related to SERVER-50839 Coverity analysis defect 115992: Pars... Closed
is related to SERVER-50556 Coverity analysis defect 116011: Pars... Closed
is related to SERVER-50557 Coverity analysis defect 114585: Unin... Closed
is related to SERVER-50552 Coverity analysis defect 116074: Unus... Closed
is related to SERVER-50553 Coverity analysis defect 116026: Unus... Closed
is related to SERVER-50554 Coverity analysis defect 116001: Unus... Closed
is related to SERVER-50551 Coverity analysis defect 116085: Pars... Backlog
Sprint: Query 2020-08-10, Query 2020-09-07, Query 2020-09-21
Participants:

 Description   

1. Login to coverity (use link in comments)
2. Review issues relevant to your team's ownership (filtering by the component field may help in this case)
3. For each issue that is related to your team, set the "Action" field to either Needs Fix, Ignore, Report to Coverity and click Apply button.
4. In the case of Needs Fix, choose export to generate JIRA ticket, and add the following label to the JIRA issue: "coverity-pm-1854-tracking"
5. Resolve this ticket once all untriaged query issues have been triage.



 Comments   
Comment by James Wahlin [ 09/Sep/20 ]

Closing as "Gone away" as each of the reported Query defects has been addressed in Coverity. See attached tickets for those that may be actionable.

Comment by James Wahlin [ 24/Jul/20 ]

QO will handle this.

Comment by David Storch [ 23/Jul/20 ]

james.wahlin I see that QO triaged this issue. Did you intend for QO to take this task for the upcoming sprint as well? I see it's currently not assigned to either QE or QO.

Generated at Thu Feb 08 05:19:38 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.