[RELENG-41] Detect wider range of autorelease-breaking Changes Created: 26/Jan/17 Updated: 19/Oct/17 |
|
| Status: | Open |
| Project: | releng |
| Component/s: | Jenkins Job Builder |
| Affects Version/s: | unspecified |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Vratko Polak | Assignee: | Unassigned |
| Resolution: | Unresolved | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 7688 |
| Description |
|
The latest example is when (probably) a Netty upgrade made netconf-netty-util fail (on unit test I think). TODO: Add details on what really happened, then examine if a lightweight detection in distribution-check job is possible. |
| Comments |
| Comment by Robert Varga [ 26/Jan/17 ] |
|
The unit test failed on unstubbed method invocation, which really means that the netty implementation has added some calls which were not foreseen by the test. This is not something that really affects functionality, but indicates that the unit test could probably be done in a way that requires less mocking of third party libraries. Hard to say, really. |