| Commit message (Collapse) | Author | Age | Files | Lines |
| |
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
`Renderer::clearData()` is a better API than the removed `MapOptions::keepRenderData()`:
- gives more flexibility to the client
- similar to the existing `Renderer::reduceMemoryUse()`
- the `MapOptions::keepRenderData()` API implementation could not handle the raise condition, which
happened if the new still image request had come before all tiles from the previous requests were loaded.
Co-authored-by: Dane Springmeyer <dane@mapbox.com>
|
| |
|
| |
|
|
|
|
|
|
| |
* [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
|
|
|
|
| |
Instead of trying to read it from the filesystem.
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Simplify the code path and make it print both rendering error and
metrics on fail.
|
|
|
|
|
|
| |
Metrics will now fail, but the tool will return 0 when *ONLY* metrics
fail, to make the bot continue. We will also run ignored tests and
check if they are ignored but passing.
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
|
| |
Rebaseline flag allows to update or create new metric, in cases when
metric check is failed or expected metric is missing.
|
| |
|
| |
|
|
|
|
|
| |
If there are multiple file size probes in a test file, it is
better to report all failures instead of first failed probe.
|
|
|
|
|
| |
Useful because for platform such as Android, we want to measure
the size of the library inside the APK, which is usually compressed.
|
|
|
|
|
|
|
|
| |
Added the following command line argument:
```
-u[update], --update=[update] Test results update mode.
Supported values are: "default", "platform", "metrics"
```
|
|
|
|
|
|
|
|
|
|
|
| |
- Move probe related command line arguments to manifest, example:
"probes": ["probeGFX", "probeNetwork", "probeMemory"],
"metric_path": "metrics/linux"
- Use manifest file name as a postfix for a result page
- Move injected probes 'begin' section before map object creation
- Generalize artifact storing shell script
|
|
|
|
|
|
|
|
|
|
| |
* [render-test]Add expected metrics path in manifest file
* seperate metrics.json and expected.png
* fix expected path parsing
* keep expectation path if update is enabled
|
|
|
|
|
| |
This allows injection of memory, gfx and network probes before and
after operations defined in render test are run.
|
|
|
|
|
|
|
|
|
|
|
|
| |
app (#15887)
* [render-test] Wrap test resources inside app
* [render-test] Add test app
* fix test app failure
* [render-test]add callback + add javaObjectWrapper
|
| |
|
| |
|
|
|
|
|
|
|
|
|
|
| |
* [render-test] Add manifest parser for render-test-runner
* [render-test] Refactory manifest parser
* [render-test] Parse full manifest file through CLI
* [render-test] Add linux probe manifest
|
|
|
|
|
|
| |
* [render-test] Add configurable path via CLI arguments
* [render-test] Change ignore path config
|
| |
|
| |
|
|
|
|
|
|
| |
-e[expectationsPath], --expectationsPath=[expectationsPath]
Test expectations path.
|
| |
|
| |
|
| |
|
| |
|
| |
|
|
|
|
| |
Should use the exact same path as described on style.json
|
| |
|
|
|
|
|
|
|
|
|
|
| |
For a given absolute or relative path, measure the size of the file.
This is useful for measuring if the cache has increased as expected
after moving a camera or decreased after cleaning up.
In a more hackish manner, could be used for collecting binary size
statistics of shared libraries.
|
|
|
|
|
|
|
| |
Before this change, the found paths to the expected images
erroneously included the path to the `metrics.json` file
(if this file was present) leading to raising of an
unhandled exception.
|
| |
|