|
| 1 | +{ |
| 2 | + "version": 1, // The version of the config file format. |
| 3 | + "project": "newrelic", |
| 4 | + "project_url": "https://github.com/newrelic/newrelic-python-agent", |
| 5 | + "show_commit_url": "https://github.com/newrelic/newrelic-python-agent/commit/", |
| 6 | + "repo": ".", |
| 7 | + "environment_type": "virtualenv", |
| 8 | + "install_timeout": 120, |
| 9 | + "pythons": ["3.8", "3.9", "3.10", "3.11", "3.12", "3.13"], |
| 10 | + "benchmark_dir": "tests/agent_benchmarks", |
| 11 | + "env_dir": ".asv/env", |
| 12 | + "results_dir": ".asv/results", |
| 13 | + "html_dir": ".asv/html", |
| 14 | + "regressions_thresholds": { |
| 15 | + ".*": 0.2, // Threshold of 20% |
| 16 | + }, |
| 17 | + |
| 18 | + // The matrix of dependencies to test. Each key of the "req" |
| 19 | + // requirements dictionary is the name of a package (in PyPI) and |
| 20 | + // the values are version numbers. An empty list or empty string |
| 21 | + // indicates to just test against the default (latest) |
| 22 | + // version. null indicates that the package is to not be |
| 23 | + // installed. If the package to be tested is only available from |
| 24 | + // PyPi, and the 'environment_type' is conda, then you can preface |
| 25 | + // the package name by 'pip+', and the package will be installed |
| 26 | + // via pip (with all the conda available packages installed first, |
| 27 | + // followed by the pip installed packages). |
| 28 | + // |
| 29 | + // The ``@env`` and ``@env_nobuild`` keys contain the matrix of |
| 30 | + // environment variables to pass to build and benchmark commands. |
| 31 | + // An environment will be created for every combination of the |
| 32 | + // cartesian product of the "@env" variables in this matrix. |
| 33 | + // Variables in "@env_nobuild" will be passed to every environment |
| 34 | + // during the benchmark phase, but will not trigger creation of |
| 35 | + // new environments. A value of ``null`` means that the variable |
| 36 | + // will not be set for the current combination. |
| 37 | + // |
| 38 | + // "matrix": { |
| 39 | + // "req": { |
| 40 | + // "numpy": ["1.6", "1.7"], |
| 41 | + // "six": ["", null], // test with and without six installed |
| 42 | + // "pip+emcee": [""] // emcee is only available for install with pip. |
| 43 | + // }, |
| 44 | + // "env": {"ENV_VAR_1": ["val1", "val2"]}, |
| 45 | + // "env_nobuild": {"ENV_VAR_2": ["val3", null]}, |
| 46 | + // }, |
| 47 | + |
| 48 | + // Combinations of libraries/python versions can be excluded/included |
| 49 | + // from the set to test. Each entry is a dictionary containing additional |
| 50 | + // key-value pairs to include/exclude. |
| 51 | + // |
| 52 | + // An exclude entry excludes entries where all values match. The |
| 53 | + // values are regexps that should match the whole string. |
| 54 | + // |
| 55 | + // An include entry adds an environment. Only the packages listed |
| 56 | + // are installed. The 'python' key is required. The exclude rules |
| 57 | + // do not apply to includes. |
| 58 | + // |
| 59 | + // In addition to package names, the following keys are available: |
| 60 | + // |
| 61 | + // - python |
| 62 | + // Python version, as in the *pythons* variable above. |
| 63 | + // - environment_type |
| 64 | + // Environment type, as above. |
| 65 | + // - sys_platform |
| 66 | + // Platform, as in sys.platform. Possible values for the common |
| 67 | + // cases: 'linux2', 'win32', 'cygwin', 'darwin'. |
| 68 | + // - req |
| 69 | + // Required packages |
| 70 | + // - env |
| 71 | + // Environment variables |
| 72 | + // - env_nobuild |
| 73 | + // Non-build environment variables |
| 74 | + // |
| 75 | + // "exclude": [ |
| 76 | + // {"python": "3.2", "sys_platform": "win32"}, // skip py3.2 on windows |
| 77 | + // {"environment_type": "conda", "req": {"six": null}}, // don't run without six on conda |
| 78 | + // {"env": {"ENV_VAR_1": "val2"}}, // skip val2 for ENV_VAR_1 |
| 79 | + // ], |
| 80 | + // |
| 81 | + // "include": [ |
| 82 | + // // additional env for python3.12 |
| 83 | + // {"python": "3.12", "req": {"numpy": "1.26"}, "env_nobuild": {"FOO": "123"}}, |
| 84 | + // // additional env if run on windows+conda |
| 85 | + // {"platform": "win32", "environment_type": "conda", "python": "3.12", "req": {"libpython": ""}}, |
| 86 | + // ], |
| 87 | + |
| 88 | + // The commits after which the regression search in `asv publish` |
| 89 | + // should start looking for regressions. Dictionary whose keys are |
| 90 | + // regexps matching to benchmark names, and values corresponding to |
| 91 | + // the commit (exclusive) after which to start looking for |
| 92 | + // regressions. The default is to start from the first commit |
| 93 | + // with results. If the commit is `null`, regression detection is |
| 94 | + // skipped for the matching benchmark. |
| 95 | + // |
| 96 | + // "regressions_first_commits": { |
| 97 | + // "some_benchmark": "352cdf", // Consider regressions only after this commit |
| 98 | + // "another_benchmark": null, // Skip regression detection altogether |
| 99 | + // }, |
| 100 | +} |
0 commit comments