summaryrefslogtreecommitdiff
path: root/inttest
Commit message (Collapse)AuthorAgeFilesLines
* remove more code that can be brought back later if neededTristan Sloughter2014-08-30111-1491/+0
|
* Fix OS X resource fork handling (Reported-by: Richard O'Keefe)Tuncer Ayaz2014-07-251-0/+4
| | | | | | | | | If you happen to fetch a zip archive of the git repo and try to build from that, you may, for example, ask erlc to build src/._rebar.erl. ._* are OS X resource forks and not real .erl files. This may also happen with network filesystems on OS X. To fix that, limit the files compiled by rebar to include only those which start with a letter or a digit.
* Merge branch 'erl-args-to-end' of https://github.com/NineFX/rebar into ↵Fred Hebert2014-07-154-1/+12
|\ | | | | | | | | | | | | NineFX-erl-args-to-end Conflicts: THANKS
| * Fix bug 271varnerac-ubnt2014-06-274-1/+12
| | | | | | | | | | | | | | | | | | | | Moves ct_extra_params to the end of the generated ct_run command. This allows users to pass commands to the underlying emulator using -erl_args. The included rt test demonstrates that it is possible to pass an addtional option to ct_run and -erl_args at the same time. Finally, the test executes in regular and verbose modes because rebar constructs the ct_run command differently in verbose mode.
* | Fix #249 (erlc regression)Slava Yurin2014-05-302-2/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | The combination of changes to rebar_erlc_compiler, and the fact that erl_first_files is inherited, caused a regression. To fix that, ensure every project uses its own .rebar/erlcinfo. While at it, fix the issue that erl_first_files entries were not included when initializing the dep digraph. Reported-by: Louis-Philippe Gauthier Reported-by: Roland Karlsson Thanks: Tuncer Ayaz
* | Regression test for #249Slava Yurin2014-05-307-2/+67
| |
* | Merge pull request #251 from mururu/eunit_compile_optsJared Morrow2014-05-194-0/+65
|\ \ | | | | | | Make sure that eunit/qc_compile_opts works
| * | Make sure that eunit/qc_compile_opts works fix #245Yuki Ito2014-05-134-0/+65
| | |
* | | Merge pull request #242 from tuncer/erlc-speedup-v5-fixupJared Morrow2014-05-1914-0/+282
|\ \ \ | |/ / |/| | Extra commits for #129
| * | erlc: add test suiteTuncer Ayaz2014-03-1214-0/+282
| | |
* | | Fix #267 (code path regression)Tuncer Ayaz2014-04-2314-0/+115
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Since the introduction of -r/--recursive, deps were not properly added to the code path when running ct, eunit, etc. To fix that, pass a flag down to process_dir1 and conditionalize execution of the command. This moves the decision into process_dir1 where we can decide to invoke preprocess/2 and postprocess/2 but not execute the command. Without this fix, you'd have to, for example, invoke 'rebar -r ct skip_deps=true', if you wanted to run base_dir's ct suites with deps on the code path (while skipping all non-base_dir ct suites). So, with this patch applied, if you run $ rebar ct deps will be on the code path, and only base_dir's ct suites will be tested. If you want to test ct suites in base_dir and sub_dirs, you have to run $ rebar -r ct skip_deps=true If you want to test ct suites in all dirs, you have to run $ rebar -r ct The fix is not specific to ct and applies to all commands. To be able to add inttest/code_path_no_recurse/deps, I had to fix .gitignore. While at it, I've updated and fixed all entries.
* | Keep compile recursive and update the tests to not pass -r to compileJared Morrow2014-03-114-4/+4
| |
* | Fix #56 (always-on recursion)Tuncer Ayaz2014-03-114-4/+7
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Always-on recursive application of all rebar commands causes too many issues. Recursive application is required for: 1. dealing with dependencies: get-deps, update-deps, and compile of deps right after get-deps or update-deps 2. projects with a riak-like apps/ project structure and dev process The vast majority of projects are not structured like riak. Therefore, moving forward it's best to (by default) restrict recursive behavior to dealing with deps. This commit does that and also adds command line and rebar.config options for controlling or configuring recursion. Also, we introduce two meta commands: prepare-deps (equivalent to rebar -r get-deps compile) and refresh-deps (equivalent to rebar -r update-deps compile). riak-like projects can extend the list of recursive commands (to include 'eunit' and 'compile') by adding {recursive_cmds, [eunit, compile]} to rebar.config.
* | inttest/depplugins: update docsTuncer Ayaz2014-01-011-5/+8
| |
* | Add test for regression caused by 252b31f (#90)Tuncer Ayaz2014-01-016-11/+44
|/
* inttest/rgen_1: double the timeout a second timeTuncer Ayaz2013-12-171-1/+1
| | | | | | | 60s still seems to be too low, as it timed out for at least the R15B01 job of the timeout patch merge: https://travis-ci.org/rebar/rebar/builds/15051701 https://travis-ci.org/rebar/rebar/jobs/15051703
* Change default log level to 'warn' and introduce -q/--quietTuncer Ayaz2013-12-062-1/+100
|
* inttest/rgen1: increase retest timeout (30s -> 60s)Tuncer Ayaz2013-12-061-0/+1
| | | | | The current default (30s) causes inttest/rgen1 to timeout too often. Add retest.config to double the timeout.
* Delete unused inttest/retest binaryTuncer Ayaz2013-11-271-0/+0
|
* Don't over-aggressively clean the code path in the presence of lib_dir ↵Andrew Thompson2013-10-1612-0/+109
| | | | | | | | | | | | | | | | | | | | | | | directives Rebar, when it encounters a lib_dir directive, caches the current code path, adds the libdir(s) and returns the cached copy of the path. When rebar has finished processing that directory, it restores the cached path. This is problematic in the below scenario: /(lib_dir)->G A -> B -> C -> D -> E \-> F -> D -> E When rebar is finished processing B, it restores the code path to what it was before it processed B, removing C, D, E and G from the code path. This means when it comes to process F, neither D or E are in the code path, so any header includes, rebar plugins or parse transforms will not be in the code path. Without the lib_dir directive, rebar does no code path cleanups, so everything works fine. This change makes rebar only remove the explicit lib_dir code paths it added and adds an inttest that replicates the above scenario.
* TypoAndrew Thompson2013-10-141-1/+1
|
* Address review comments and add inttest for update-depsAndrew Thompson2013-09-3018-0/+175
|
* Merge pull request #90 from Motiejus/dep_pluginDave Smith2013-05-214-0/+59
|\ | | | | Fix searching for plugins
| * Fix searching for pluginsMotiejus Jakštys2013-05-194-0/+59
| | | | | | | | | | If a plugin is in a dependency, rebar didn't search for it carefully enough.
* | Additional travisci fixesDave Smith2013-04-231-4/+15
| |
* | Adding user/email on created repos for travis CIDave Smith2013-04-221-0/+2
| |
* | Further investigation into travis CI issuesDave Smith2013-04-221-3/+12
| |
* | Add author to fix issue when compiling on travisDave Smith2013-04-221-1/+1
|/
* Remove hg from integration tests; git is defacto standard at this pointDave Smith2013-03-026-11/+11
|
* Add support for non-Erlang/OTP (raw) dependenciesAnton Lavrik2012-10-111-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | Introduce a new 'raw' option for dependency specs in rebar.config file. For example: {deps, {dependency_name, "1.0.*", {git, "<...>", {branch, "master"}}, [raw] } ]}. When this option is specified, rebar does not require the dependency to have a standard Erlang/OTP layout which assumes presence of either "src/dependency_name.app.src" or "ebin/dependency_name.app" files. 'raw' dependencies can still contain 'rebar.config' and even can have the proper OTP directory layout, but they won't be compiled. Only a subset of rebar commands will be executed on the 'raw' subdirectories: get-deps, update-deps, check-deps, list-deps and delete-deps.
* Fix inttest/ct2 ct spec file location (Thanks Peter Andersson)Tuncer Ayaz2012-09-031-1/+1
| | | | | The DirRef in the spec file is relative to the directory where the spec file is located. ct2_rt was erroneously copying the spec file to test/.
* inttest/ct2: enable rebar DEBUG log levelTuncer Ayaz2012-09-031-1/+1
|
* inttest: remove superfluous blank linesTuncer Ayaz2012-08-182-6/+0
|
* inttest: fix whitespace errorsTuncer Ayaz2012-08-1813-18/+5
|
* Fix warning in inttest/tplugins/tplugins_rt.erlTuncer Ayaz2012-07-011-1/+1
|
* Fix test: inttest/t_custom_configTuncer Ayaz2012-07-011-1/+1
|
* Add support for customising common test directoryTim Watson2011-12-282-1/+4
| | | | | | | This patch allows users to specify the directory in which common_test source files can be found. Most common_test suites are integration, rather than unit tests and keeping the sources apart from test sources for other frameworks such as eunit and PropEr is a useful feature.
* Fix config handling in root_dirTim Watson2011-10-052-2/+13
| | | | | Avoid overwriting custom config (passed with -C) when we are processing the base_dir in rebar_core.
* Load plugins dynamically from sourceTim Watson2011-08-296-0/+63
| | | | | | | | | This patch updates rebar_core to look for missing plugins (i.e. those that aren't found on the code path at runtime) in a configurable plugin directory, and dynamically compile and load them at runtime. By default, the directory "plugins" is searched, although this can be overriden by setting the plugin_dir in your rebar.config.
* Respect the --config switch when givenTim Watson2011-08-183-0/+38
| | | | | | | | Currently the --config switch does not work because when loading a new rebar config the global setting is ignored for all paths. This patch provides a check when loading new rebar config to see whether or not the current config path matches the `base_dir` set in global conf, which produces the expected behaviour.
* Add pre and post script support for all commandsTim Watson2011-03-123-0/+52
| | | | | | | | | This change makes it possible to assign pre/post scripts to all rebar commands. This allows users fine grained control over when scripts and/or shell commands should be executed, where such extensions are absolutely needed. Several examples have been added to the rebar.config.sample file.
* Add -spec support to rebar_ct command lineTim Watson2011-02-213-0/+37
| | | | | | | | | | | | | This change adds support for executing ct test runs based on test specificiations, which was missing previously. The rebar_ct module now looks for any number of files with a name ending in `test.spec` and if it finds one or more, passes these after the `-spec` argument to ct_run instead of explicitly configuring the config, user config and coverage config variables. When no specifications are found, then the module behaves as it did before this change, and both the ct1 and (new) ct2 integration tests appear to show this is a backwards compatible patch.
* Fix warningTuncer Ayaz2011-01-311-1/+1
|
* Clean up emacs file local variablesTuncer Ayaz2011-01-311-1/+1
|
* Fix file existence checksTuncer Ayaz2011-01-291-1/+1
|
* Adding simple test suite for common_test functionalityDave Smith2010-06-222-0/+38
|
* Fix bug in tdeps2_rt test; app files were not getting module listDave Smith2010-06-211-6/+6
|
* Updating retestDave Smith2010-06-141-0/+0
| | | | | --HG-- extra : rebase_source : 5035f025b5873cedfb67e42159c5ce95b07c198d
* Adding test for new release generation overlay systemDave Smith2010-06-144-0/+51
| | | | | --HG-- extra : rebase_source : cd143fdf55773dcfbeeda687570b226def42e4f5
* Updating integration testsDave Smith2010-06-093-8/+16
| | | | | --HG-- extra : rebase_source : c0bfcfbbbca005eee2a3434cbe25494399b07532
generated by cgit v1.1 at 2024-12-24 03:32:11 +0000