| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This change fixes the following problems:
1) Before this change, when multiple symbols were grouped close to the
tile borders, different tiles could place different symbols, because each
tile arbitrary assigned feature ids, and these ids defined the placement
order being applied. This caused artifacts at the tile boundaries.
With this change, in tile mode the placement order of two symbols crossing
a tile border is defined by their anchor `y` values. It means that the
symbols are being placed the same order across all the tiles.
2) Before this change, the engine did not place with priority the symbols
crossing the borders between two neighboring tiles. Now it does, and it
improves a lot symbol placement stability in the tile map mode.
|
|
|
|
|
| |
- Remove the legacy build jobs
- Remove the next- namespace.
|
|
|
|
|
| |
This commit allows the variable symbols to cross the tile border only
if their anchor is the first anchor from the `text-variable-anchor` list.
|
| |
|
|
|
|
|
|
| |
* [test-runner] Add iOS RenderTestRunner test metrics
* [test-runner] Add ios probe metrics
|
|
|
|
|
|
|
|
|
|
| |
* [test-runner] Setup iOS RenderTestRunner
* [test-runner] Make app runnable on firebase
* Add iOS platform dependent expectation and ignores; Run prepare script via cmake
* Make RenderTestRunner report test status
|
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* [core] Introduce FileSourceManager and use it for default platform impl
- Add `FileSourceManager` interface that provides access to `FileSource`
instances and means of registering / unregistering `FileSource` factories
- Split `DefaultFileSource` into smaller parts
- Add `DatabaseFileSource` interface and it's default implementation
- Remove inter-dependencies between concrete `FileSource` classes
* [build] Add files to next build system
* [core] Add generic property setters / getters
* [core] Remove setOnlineStatus from OnlineFileSource interface
* [core] Hide threading implementation details from DatabaseFileSource interface
* [core] Make DB file source methods virtual
* [core] Add documentation for DatabaseFileSource and rename one method
* [core] Use simple callback instead of ActorRef
* [core] Remove ActorRef from OnlineFileSource public header
* [core] Add callback to FileSource::forward async API
* [core] Pass OfflineRegionDefinition by value
* [core] Update tests to use modular file sources
* [core] Update unit tests
* [core] Update unit tests after rebase
* [core] Backport low prio fix for cached requests
* [core] Backport pack database
* [core] Return removed factory from unRegisterFileSourceFactory
* [core] Rename shadowed args in onlinefilesource
* [core] Remove simple std::function callback aliases
* [core] Expose online file source property keys in public header file
* [test-runner] Add proxy file source test runner
* [cache] Update mbgl-cache utility to use new file source
* [metrics] Rebaseline binary size metrics
* [offline] Update offline utility
* [core] Update changelog
|
|
|
|
| |
More accurate now since everything goes through the FileSource.
|
|
|
|
|
| |
Need further investigation on why these tests are failing
after we started to use the cache database.
|
|
|
|
|
| |
Now that we use a cache, we no longer need "asset_path" and
"vendor_path".
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
This explains why these tests were not being rebaselined...
|
| |
|
|
|
|
| |
Sames as for Android, remove ignored and probes not in use.
|
|
|
|
|
|
|
| |
This was done using the new baseline bot :-)
- Removed metrics from ignored tests.
- Removed memory metrics for render tests, not in use.
|
|
|
|
|
|
|
| |
This test is ignored because we expect it to "ignore but fail".
But it will generate a fatal error because it doesn't have the
metrics file, thus should have been skipped instead.
|
|
|
|
| |
Also fail the bot in case there are new baselines.
|
|
|
|
|
|
| |
Move everything that might collect metrics to the metrics/ directory,
the only test manifests inside the render-test/ directory are the
unit tests of the probes.
|
| |
|
| |
|
|
|
|
|
|
|
| |
Press F1 to create a render test for the current view.
The test will be created at the base folder (current if nothing is
provided) + /NNNN (the next free entry).
|
| |
|
| |
|
|
|
|
|
|
| |
Chromium is using it for a while on ARM.
https://codereview.chromium.org/1153143004/patch/20001/30002
|
|
|
|
| |
Because what metters is the size we add to the APK.
|
| |
|
|
|
|
|
| |
Will give us a better view of what changed and by how much. Otherwise
the test stops at the first failure.
|
|
This test will check the size of the tools and shared libraries
built from previous bots in a single run.
We will have +/- 1% acceptable variance before the test fails.
|