An error occurred fetching the project authors.
- 01 Dec, 2011 1 commit
-
-
Rusty Russell authored
It's reduced to a flag which means we stop processing the module. We have to enhance our dependencies a bit, but they've always been quite good. This simplifies things quite a bit.
-
- 30 Aug, 2011 1 commit
-
-
Rusty Russell authored
Rather than mug the old ->compiled version when we reduce features, keep both in the structure. This makes it clear that we are using the right version (we weren't in all cases, in particular we weren't recompiling the test helpers correctly.
-
- 01 Mar, 2011 2 commits
-
-
Rusty Russell authored
-
Rusty Russell authored
This means you don't have to recompile ccanlint to get the new flags; it's a small step towards making ccanlint useful outside the ccan repo.
-
- 17 Jan, 2011 1 commit
-
-
Rusty Russell authored
We simply build up the error string in score_file_error; a bit different but simpler than current behaviour. We keep around struct file_error because some tests need it.
-
- 07 Jan, 2011 4 commits
-
-
Rusty Russell authored
-
Rusty Russell authored
-
Rusty Russell authored
Joey Adams also pointed out that we should use strings for the dependency lists. Moving them into the structure also somewhat simplifies it.
-
Rusty Russell authored
Joey Adams rightly points out that the current keys are a mess: ideally the filenames, test keys and structure names in ccanlint should be the same. First step is to make the test names all regular, of basic form <noun>_<verb> (eg "tests_exist" rather than "has-tests").
-
- 15 Nov, 2010 1 commit
-
-
Rusty Russell authored
This means we can pass various compulation tests, but deduct points if they get warnings.
-
- 14 Nov, 2010 1 commit
-
-
Rusty Russell authored
We want to distinguish between warnings and errors: the first step is to return the output even if the command doesn't fail.
-
- 09 Nov, 2010 1 commit
-
-
Rusty Russell authored
Previously each check returned a void *, but in fact most of them fell into similar patterns. So define 'struct score' and a helper to add files to it, and use that. Under these rules, you get 0/1 if you skip a test because a dependency failed which in theory means your score (as a percentage) could drop if you fix a test.
-
- 27 Aug, 2010 1 commit
-
-
Rusty Russell authored
-
- 07 Jun, 2010 1 commit
-
-
Rusty Russell authored
Particularly useful for building tests standalone.
-
- 09 Apr, 2010 2 commits
-
-
Rusty Russell authored
-
Rusty Russell authored
The ccanlint patch is rather intrusive. First, it adds a new field to all the ccanlint tests, "key". key is a shorter, still unique description of the test (e.g. "valgrind"). The names I chose as keys for all the tests are somewhat arbitrary and often don't reflect the name of the .c source file (because some of those names are just too darn long). Second, it adds two new options to ccanlint: -l: list tests ccanlint performs -x: exclude tests (e.g. -x trailing_whitespace,valgrind) It also adds a consistency check making sure all tests have unique keys and names. The primary goal of the ccanlint patch was so I could exclude the valgrind test, which takes a really long time for some modules (I think btree takes the longest, at around 2 minutes). I'm not sure I did it 100% correctly, so you'll want to review it first.
-
- 01 Feb, 2010 1 commit
-
-
Rusty Russell authored
-
- 07 Oct, 2009 1 commit
-
-
Rusty Russell authored
Offer to run debugger when test fails, with breakpoint.
-
- 25 Sep, 2009 4 commits
-
-
Rusty Russell authored
-
Rusty Russell authored
Generally clean up temp file handling.
-
Rusty Russell authored
-
Rusty Russell authored
This means we should skip building if there are no C files in module: running tests requires building the module, but not necessarily that it has any C files.
-
- 12 Sep, 2009 1 commit
-
-
Rusty Russell authored
More sophisticated skipping: skip dependencies when one fails as well. Allow tests to change their total_score; only access it after running (other than to check it's non-zero).
-