[LISPMAP-70] features-lispflowmapping build failure in autorelease Created: 02/Oct/15 Updated: 19/Oct/17 Resolved: 07/Oct/15 |
|
| Status: | Resolved |
| Project: | lispflowmapping |
| Component/s: | General |
| Affects Version/s: | Lithium |
| Fix Version/s: | None |
| Type: | Bug | ||
| Reporter: | Thanh Ha (zxiiro) | Assignee: | Unassigned |
| Resolution: | Cannot Reproduce | Votes: | 0 |
| Labels: | None | ||
| Remaining Estimate: | Not Specified | ||
| Time Spent: | Not Specified | ||
| Original Estimate: | Not Specified | ||
| Environment: |
Operating System: All |
||
| External issue ID: | 4398 |
| Description |
|
Not sure if this is related but I see this warning that maybe be the cause? [WARNING] The artifact junit:junit-dep:jar:4.11 has been relocated to junit:junit:jar:4.11 |
| Comments |
| Comment by Thanh Ha (zxiiro) [ 02/Oct/15 ] |
|
Proposed patch: https://git.opendaylight.org/gerrit/27790 |
| Comment by Thanh Ha (zxiiro) [ 02/Oct/15 ] |
|
Looks like odlparent forced us to pull in junit 4.11 which was moved from junit-dep to junit:junit. Seems the lispflowmapping code depends on 4.8.1 though. We have to options: 1) upgrade to 4.11 and fix any code issues due to the upgrade The proposed patch currently does option 2) |
| Comment by Thanh Ha (zxiiro) [ 02/Oct/15 ] |
|
Looks like something else is the issue. Seems like 0 tests are getting executed for some reason. In the logs I see: NullPointerException: FeatureWrapper requires non-null Feature in constructor Oddly the autorelease-daily-lithium job passed last night. I'll try kicking off another release build to see if it makes any difference. |
| Comment by Lori Jakab [ 07/Oct/15 ] |
|
I see that since build 55 the issue is no longer present. We didn't change anything, so I guess this was not a lispflowmapping bug, closing. |