Bug 45983 – Check for connector rejects after every test

Bug 45983 - Check for connector rejects after every test


Summary:	Check for connector rejects after every test

Status:	NEW

Product:	UCS Test
Classification:	Unclassified
Component:	S4 Connector
Version:	unspecified
Hardware:	Other Linux

Importance:	P5 normal (vote)
Target Milestone:	---
Assigned To:	Samba maintainers
QA Contact:

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree / graph

Reported:	2018-01-08 08:15 CET by Daniel Tröder
Modified:	2018-04-14 14:15 CEST (History)
CC List:	0 users

See Also:
What kind of report is it?:	Feature Request
What type of bug is this?:	---
Who will be affected by this bug?:	---
How will those affected feel about the bug?:	---
User Pain:
Enterprise Customer affected?:
School Customer affected?:
ISV affected?:
Waiting Support:
Flags outvoted (downgraded) after PO Review:
Ticket number:
Bug group (optional):
Max CVSS v3 score:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Daniel Tröder

2018-01-08 08:15:51 CET

In the course of a complete Jenkins test of UCS (and more with UCS@school) various connector rejects accumulate. They are not only caused by connector tests, but my the most common tests, for maybe unknown reasons.

To capture code / data structures that cause connector rejects ucs-tests that produce new rejects should be marked as failed.

To do this, the rejects before and after a tests could be compared.