Lines Matching +refs:run +refs:tests

17 2. If you've added code that should be tested, add tests.
60         * Note: run local tests to ensure that your changes didn't break existing functionality
69 2. Code Review and CI tests
70     * Ensure CI tests pass:
71 …   * Before sharing anything to the community, make sure that all CI tests pass on your local fork.
116 Once installed, you can ensure that our static analysis tests pass on your local development machine
123 just `contrib/largeNbDicts` and nothing else, you can run:
132 …hile (and we do), but it's not a good idea to multiply the nb of analyzers run continuously at eac…
161 take the time to run extensive, long-duration, and potentially cross-(os, platform, process, etc)
187 to run it multiple times and then aggregate the results of those runs. As a general rule of
195     benchmark achieved on each run since that is likely the fastest your process will be
214     * If you have multiple cores, you can even run your benchmark on a reserved core to prevent
234 bench option. You can run Zstd as you typically would for your scenario using some set of options
235 and then additionally also specify the `-b#` option. Doing this will run our benchmarking pipeline
270 code that you think can be made to run faster.
273 a notable amount of time to run. It is usually not worth optimzing something which accounts for les…
299 $ zstd -b1 -i5 <my-data> # this will run for 5 seconds
301 5. Once you run your benchmarking script, switch back over to instruments and attach your
330 of the first things your team will run when assessing your PR.
348 Changes cannot be merged into the main dev branch unless they pass all of our CI tests.
349 The easiest way to run these CI tests on your own before submitting a PR to our dev branch
363 …again. This time, it will be for travis-pro (which will let you view your tests on the web dashboa…
382 CI tests run every time a pull request (PR) is created or updated. The exact tests
383 that get run will depend on the destination branch you specify. Some tests take
384 longer to run than others. Currently, our CI is set up to run a short
385 series of tests when creating a PR to the dev branch and a longer series of tests
387 of the respective CI platform for more information on what gets run when.
390 branch of zstd. You can then find the status of the tests on the PR's page. You can also
391 re-run tests and cancel running tests from the PR page or from the respective CI's dashboard.