aboutsummaryrefslogtreecommitdiff
path: root/tests
AgeCommit message (Collapse)AuthorFilesLines
2021-07-08Also disable GCC -Wstringop-overread in testsBoris Kolpackov1-1/+2
2021-06-09Fix cxx pattern rule testBoris Kolpackov1-6/+7
2021-06-08Redo low verbosity diagnostic deduction to use scope instead of targetBoris Kolpackov1-45/+20
2021-06-08Get rid of special *{} wildcard target type notation in target type/patternsBoris Kolpackov1-1/+1
Explicit target{} should be used instead. Also, in this context, absent target type is now treated as file{} rather than target{}, for consistency with all other cases.
2021-06-08Implement ad hoc regex pattern rule supportBoris Kolpackov3-2/+79
An ad hoc pattern rule consists of a pattern that mimics a dependency declaration followed by one or more recipes. For example: exe{~'/(.*)/'}: cxx{~'/\1/'} {{ $cxx.path -o $path($>) $path($<[0]) }} If a pattern matches a dependency declaration of a target, then the recipe is used to perform the corresponding operation on this target. For example, the following dependency declaration matches the above pattern which means the rule's recipe will be used to update this target: exe{hello}: cxx{hello} While the following declarations do not match the above pattern: exe{hello}: c{hello} # Type mismatch. exe{hello}: cxx{howdy} # Name mismatch. On the left hand side of `:` in the pattern we can have a single target or an ad hoc target group. The single target or the first (primary) ad hoc group member must be a regex pattern (~). The rest of the ad hoc group members can be patterns or substitutions (^). For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} On the left hand side of `:` in the pattern we have prerequisites which can be patterns, substitutions, or non-patterns. For example: <exe{~'/(.*)/'} file{^'/\1.map/'}>: cxx{~'/\1/'} hxx{^'/\1/'} hxx{common} {{ $cxx.path -o $path($>[0]) "-Wl,-Map=$path($>[1])" $path($<[0]) }} Substitutions on the left hand side of `:` and substitutions and non-patterns on the right hand side are added to the dependency declaration. For example, given the above rule and dependency declaration, the effective dependency is going to be: <exe{hello} file{hello.map>: cxx{hello} hxx{hello} hxx{common}
2021-06-08Only pass target to recipe_text() if recipe is not sharedBoris Kolpackov1-20/+45
2021-05-28Add support for regex-based target type/pattern specific variablesBoris Kolpackov1-0/+127
This is in addition to the already supported path-based target type/pattern specific variables. For example: hxx{*}: x = y # path-based hxx{~/.*/}: x = y # regex-based
2021-05-28Ban conversion of patterns to valuesBoris Kolpackov3-2/+5
Also improve conversion diagnostic.
2021-04-21Add buildscript depdb builtin 'env' commandKaren Arutyunov1-0/+62
2021-04-20Disable bunch of bogus GCC warningsBoris Kolpackov1-0/+2
2021-03-22Fix tests to work for compressed file cache entriesBoris Kolpackov1-1/+1
2021-03-18Add noop mode to file cache, add --file-cache option to selectBoris Kolpackov1-1/+1
2021-03-16Define intermediate build results file cache interfaceBoris Kolpackov1-1/+3
2021-02-11Improve module name to file name matching logicBoris Kolpackov1-0/+3
2021-02-11Update header unit testsBoris Kolpackov1-4/+4
2021-01-12Diagnose typed and project-qualified empty namesBoris Kolpackov1-1/+0
2020-12-14Make use of export testscript builtinKaren Arutyunov1-5/+7
2020-12-14Make export script builtin tests more robustKaren Arutyunov1-0/+5
2020-12-11Add export script pseudo-builtinKaren Arutyunov3-4/+170
2020-12-11Copy parent scope's test program list in runner's entry() function rather ↵Karen Arutyunov1-3/+29
than in scope's constructor
2020-12-11Fix set pseudo-builtin to reset special variables when requiredKaren Arutyunov1-0/+9
2020-12-11Prefix pseudo-builtin diagnostincs messages with their namesKaren Arutyunov3-12/+12
2020-12-08Redo $normalize(true) as separate $actualize()Karen Arutyunov1-9/+12
2020-12-08Add support for config.test.runnerKaren Arutyunov3-2/+107
2020-12-08Fix buildscript assertion failure on redirecting command stderr to stdoutKaren Arutyunov1-0/+23
2020-12-02Add support for buildscript depdb preambleKaren Arutyunov2-19/+304
2020-11-30Start adapting module mapper to latest GCC protocolBoris Kolpackov2-0/+10
2020-11-19Remove target files on ad hoc rule update buildscript errorKaren Arutyunov1-13/+60
2020-11-19Fix set buildscript builtin crash on WindowsKaren Arutyunov1-1/+8
2020-11-17Generalize dot escaping in target name rulesBoris Kolpackov1-20/+223
Now triple dot and escape sequence can appear almost anywhere in the target name (see target::split_name() for details).
2020-11-06Fix mistreating test operation timeout as test timeout in some caseKaren Arutyunov1-4/+8
2020-11-06Add support for test timeoutsKaren Arutyunov9-22/+888
2020-09-28Add $string.trim() functionBoris Kolpackov1-0/+7
2020-08-03Fix buildscript diagnostics so diff output is always in unified formatKaren Arutyunov1-0/+22
Also make sure diff refers program stdout as 'stdout' rather than '-' in the test rule diagnostics.
2020-07-18Add $regex.find_match() and $regex.find_search() functionsKaren Arutyunov1-0/+84
2020-07-16Save original compiler path/mode in {c,cxx}.config.path/modeBoris Kolpackov4-4/+4
It turns out that when propagating {c,cxx}.config in tests we don't want to propagate any options (such as *.std) that have been folded into our project's mode.
2020-07-06Adjust variable block applicability in dependency chainsBoris Kolpackov2-0/+95
Before the block used to apply to the set of prerequisites before the last `:`. This turned out to be counterintuitive and not very useful since prerequisite-specific variables are a lot less common than target specific. And it doesn't fit with ad hoc recipes. The new rule is if the chain ends with `:`, then the block applies to the last set of prerequisites. Otherwise, it applies to the last set of targets. For example: ./: exe{test}: cxx{main} { test = true # Applies to the exe{test} target. } ./: exe{test}: libue{test}: { bin.whole = false # Applies to the libue{test} prerequisite. } This is actually consistent with both non-chain and non-block cases. Consider: exe{test}: cxx{main} { test = true } exe{test}: libue{test}: { bin.whole = false } exe{test}: libue{test}: bin.whole = false The only exception we now have in this overall approach of "if the dependency declaration ends with a colon, then what follows is for a prerequisite" is for the first semicolon: exe{test}: { test = true } exe{test}: test = true But that's probably intuitive enough since there cannot be a prerequisite without a target.
2020-06-24Stop forcing modules support in testsBoris Kolpackov1-15/+0
2020-06-19Adapt mv builtin tests to terminology changeKaren Arutyunov1-1/+1
2020-06-18Add env script pseudo-builtinKaren Arutyunov4-143/+159
Also disable C++ recipe tests when cross-testing.
2020-06-16Add metadata for exe{b}, including whether it is statically-linkedBoris Kolpackov3-1/+11
Use this information to omit ad hoc C++ recipe tests is testing statically- linked build system.
2020-06-12Fix invalid regex in C++ recipe testsBoris Kolpackov1-2/+2
2020-06-11Add tests for ad hoc C++ recipesBoris Kolpackov3-9/+168
2020-06-10Add ad hoc recipe if-else, switch tests (and fix bug)Boris Kolpackov1-0/+149
2020-06-08Add buildscript recipe testsKaren Arutyunov2-0/+100
2020-06-08Cleanup script command failure diagnosticsKaren Arutyunov4-3/+12
2020-06-05Add depdb buildscript builtinKaren Arutyunov1-0/+1
2020-06-05Add ability to specify ad hoc recipe actionsBoris Kolpackov1-38/+70
We are reusing the buildspec syntax for that.
2020-06-04Properly handle diag directive in build script parserKaren Arutyunov1-3/+4
2020-06-03Allow process path values and targets as buildscript program namesKaren Arutyunov1-39/+297
Also deduce the recipe name.
generated by cgit v1.1 at 2024-11-01 16:06:58 +0000