#16448 closed defect (fixed)
Fix ImageryCompare red entries
Reported by: | Don-vip | Owned by: | team |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | External imagery source | Version: | |
Keywords: | compare eli jenkins | Cc: | stoecker, Klumbumbus, Stereo, Marc_marc |
Description
The test testImageryEntries is failing for 38 consecutives builds and the number of red entries increases every day without any visible action.
If nobody's feeling responsible to fix these issues we should disable the test? Otherwise it's only useless noise for those who try to keep other things stable.
Attachments (0)
Change History (11)
comment:1 by , 6 years ago
comment:3 by , 6 years ago
Summary: | Fix ImageryCompare red entries or disable integration test → Fix ImageryCompare red entries |
---|
comment:4 by , 6 years ago
Not sure why this is still reported. I added the max zoom.
* Maxzoom differs (21 != null): [AU] ACTmapi Imagery 2017 - https://data.actmapi.act.gov.au/arcgis/services/actmapi/imagery2017mga/ImageServer/WMSServer?FORMAT=image/jpeg&VERSION=1.1.1&SERVICE=WMS&REQUEST=GetMap&LAYERS=0&STYLES=&SRS={proj}&WIDTH={width}&HEIGHT={height}&BBOX={bbox}
follow-up: 10 comment:8 by , 6 years ago
Cool! For the five remaining, I've added the information to ELI after checking manually, so those can be taken over.
Will some JOSM developers be at SotM in Milan? I think it'd be good to have an imagery meeting.
comment:9 by , 6 years ago
Component: | Core imagery → External imagery source |
---|---|
Milestone: | 18.07 |
Resolution: | → fixed |
Status: | new → closed |
comment:10 by , 6 years ago
Replying to Stereo:
For the five remaining, I've added the information to ELI after checking manually, so those can be taken over.
One was wrong in ELI: https://josm.openstreetmap.de/wiki/ImageryCompareIgnores?action=diff&version=484
Will some JOSM developers be at SotM in Milan?
Not me.
ELI recently started to add many of JOSMs entries to their list as well causing again a large number of red entries. Klumbumbus and I are working on this, but given that now is holiday time I expect it will take some more weeks to resolve all these changes. It's not like it is easy. Sometimes our data is better, sometimes ELI stuff. Each entry must be examined.
And while these 38 builds are consecutive, the errors itself not. It have always been others.