This error should appear even for build that was previously succeeded.
The suspicion is one of the package dependencies semvar updates have caused this issue. I'm unable to isolate which dependencies because I'm unable to reproduce this locally.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet center center sets leaflet from scope should have default {[0, 0], 1} parameters on the map if not correctly defined FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet center center sets leaflet from scope should update the map center if the initial center scope properties are set FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
.....
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet center lf-center sets leaflet from scope should have default {[0, 0], 1} parameters on the map if not correctly defined FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet center lf-center sets leaflet from scope should update the map center if the initial center scope properties are set FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
.....
PhantomJS 2.1.1 (Linux 0.0.0) Directive: geojson should not create a geoJSON tilelayer if a bad structure is provided FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
07 08 2017 06:23:38.542:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-icon.png
07 08 2017 06:23:38.545:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-shadow.png
PhantomJS 2.1.1 (Linux 0.0.0) Directive: geojson should create a geoJSON tilelayer if a good structure is provided FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
07 08 2017 06:23:38.571:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-icon.png
.07 08 2017 06:23:43.570:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-icon.png
07 08 2017 06:23:43.575:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-shadow.png
PhantomJS 2.1.1 (Linux 0.0.0) Directive: geojson nested should create a geoJSON tilelayer if a good structure is provided FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
07 08 2017 06:23:43.607:WARN [web-server]: 404: /base/bower_components/leaflet/dist/images/marker-icon.png
..
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet: layers.overlays.markers marker isNested should check for a marker in a wrong layer group FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet: layers.overlays.markers marker should check for a marker in the layer group that is visible FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet: layers.overlays.markers marker should check for a marker in a wrong layer group FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
PhantomJS 2.1.1 (Linux 0.0.0) Directive: leaflet: layers.overlays.markers marker should check for a marker the old way FAILED
Error: Timeout - Async callback was not invoked within timeout specified by jasmine.DEFAULT_TIMEOUT_INTERVAL.
07 08 2017 06:24:13.724:WARN [PhantomJS 2.1.1 (Linux 0.0.0)]: Disconnected (1 times), because no message in 10000 ms.
PhantomJS 2.1.1 (Linux 0.0.0): Executed 102 of 234 (11 FAILED) (skipped 50) DISCONNECTED (1 min 6.359 secs / 56.341 secs)
This error should appear even for build that was previously succeeded. The suspicion is one of the package dependencies semvar updates have caused this issue. I'm unable to isolate which dependencies because I'm unable to reproduce this locally.