mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2024-12-29 10:04:41 +01:00
Code Issues Projects Releases Wiki Activity
49dcb90b4e
core-lightning/tools/test/Makefile

70 lines
2.3 KiB
Makefile
Raw Normal View History

bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
#! /usr/bin/make
#
# Rudimentary tests for the wire parsers, using a set of test
# definitions. (Covers more of the test definitions)
#
# We generate the files, and then we attempt to compile
# and run a test case.
configure: we don't need mako any more. And guard the mako-specific tests with a check instead. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-08-31 03:22:59 +02:00
# We don't run these at all unless mako is installed.
ifeq ($(HAVE_PYTHON3_MAKO),1)
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
check-units: check-tools
bolt-gen: handle enums Add parsing know-how for enum fields. This is necessary for internally defined wire generators. Enums are denoted by prefixing the field with an `e:`. Ex: msgdata,msg_name,field_name,e:enum_type,
2019-07-23 22:53:44 +02:00
TOOL_TEST_INCL_SRC := tools/test/enum.c
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
TOOL_GEN_SRC := tools/test/gen_test.c tools/test/gen_print.c
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
TOOL_GEN_OBJS := $(TOOL_GEN_SRC:.c=.o)
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
TOOL_GEN_HEADER := tools/test/gen_test.h tools/test/gen_print.h
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
TOOL_TEST_SRC := $(wildcard tools/test/run-*.c)
TOOL_TEST_OBJS := $(TOOL_TEST_SRC:.c=.o)
tools/test/Makefile: disable unless we're in DEVELOPER mode. Because it required update-mocks, which is a hack which relies on the format of linker errors (!) I'd prefer to make this --enable-developer only. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-21 05:00:25 +02:00
# Don't require update-mocks hack unless developer mode.
ifeq ($(DEVELOPER),1)
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
TOOL_TEST_PROGRAMS := $(TOOL_TEST_OBJS:.o=)
tools/test/Makefile: disable unless we're in DEVELOPER mode. Because it required update-mocks, which is a hack which relies on the format of linker errors (!) I'd prefer to make this --enable-developer only. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-21 05:00:25 +02:00
else
TOOL_TEST_PROGRAMS :=
endif
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
Makefile: fix missing dependencies for tools tests. This means they are included in `make check-source`, which they now pass (since previous commit). Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-09-09 04:43:18 +02:00
# Get dependencies correct
ALL_C_SOURCES += $(TOOL_GEN_SRC) $(TOOL_TEST_SRC)
ALL_C_HEADERS += $(TOOL_GEN_HEADER)
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
TOOL_TEST_COMMON_OBJS := \
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
common/utils.o
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
TOOLS_WIRE_DEPS := $(BOLT_DEPS) tools/test/test_cases $(wildcard tools/gen/*_template)
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
$(TOOL_TEST_OBJS) $(TOOL_GEN_OBJS): $(TOOL_GEN_HEADER)
$(TOOL_TEST_PROGRAMS): $(TOOL_TEST_COMMON_OBJS) $(TOOL_GEN_SRC:.c=.o) tools/test/enum.o
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
wire: move remaining bitcoin functions out to bitcoin/ files. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-05-16 03:29:05 +02:00
tools/test/gen_test.h: $(TOOLS_WIRE_DEPS) tools/test/Makefile
bolt-gen: rm unused bolt-generator; rename new bolt generator delete now unused wire-generator and replace it with the newer version.
2019-07-24 01:54:21 +02:00
$(BOLT_GEN) --page header $@ test_type < tools/test/test_cases > $@
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
tools/test/Makefile: fix always-on generation of tools/test/gen_test.c We need to tell it that the tmp file is an intermediate, so doesn't need remaking if it doesn't exist. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-21 02:53:36 +02:00
.INTERMEDIATE: tools/test/gen_test.c.tmp.c
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
# Parallel make sometimes tries to use file before update-mocks, so split.
tools/test/gen_test.c.tmp.c: $(TOOLS_WIRE_DEPS)
$(BOLT_GEN) --page impl tools/test/gen_test.h test_type < tools/test/test_cases > $@
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
tools/test/Makefile: we depend on tools/test/gen_test.h This is because update-mocks actually tries to build it to get link errors. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-19 04:12:57 +02:00
tools/test/gen_test.c: tools/test/gen_test.c.tmp.c $(EXTERNAL_HEADERS) tools/test/gen_test.h
tools-make: also be quiet if --quiet is flagged Missed a update-mocks.sh call
2020-05-29 22:48:55 +02:00
@MAKE=$(MAKE) tools/update-mocks.sh "$<" $(SUPPRESS_OUTPUT) && mv "$<" "$@"
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
Makefile: use completely separate spec-derived files for EXPERIMENTAL_FEATURES This avoids overwriting the ones in git, and generally makes things neater. We have convenience headers wire/peer_wire.h and wire/onion_wire.h to avoid most #ifdefs: simply include those. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-09-07 23:06:50 +02:00
tools/test/gen_print.h: wire/onion$(EXP)_wiregen.h $(TOOLS_WIRE_DEPS)
bolt-gen: rm unused bolt-generator; rename new bolt generator delete now unused wire-generator and replace it with the newer version.
2019-07-24 01:54:21 +02:00
$(BOLT_GEN) -P --page header $@ test_type < tools/test/test_cases > $@
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
tools/test/gen_print.c: $(TOOLS_WIRE_DEPS)
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
echo '#include "gen_test.h"' > $@
bolt-gen: rm unused bolt-generator; rename new bolt generator delete now unused wire-generator and replace it with the newer version.
2019-07-24 01:54:21 +02:00
$(BOLT_GEN) -P --page impl ${@:.c=.h} test_type < tools/test/test_cases >> $@
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
ALL_TEST_PROGRAMS += $(TOOL_TEST_PROGRAMS)
check-tools: $(TOOL_TEST_PROGRAMS:%=unittest/%)
configure: we don't need mako any more. And guard the mako-specific tests with a check instead. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2020-08-31 03:22:59 +02:00
endif # HAVE_PYTHON3_MAKO
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
bolt-gen: fixup the devtool/decodemsg printing facility Fixup TLV handling in the bolt printing utility, `devtools/decodemsg`
2019-07-21 05:04:59 +02:00
update-mocks: tools-update-mocks
tools-update-mocks: $(TOOL_TEST_SRC:%=update-mocks/%)
bolt-gen: add compilation tests Add a test for checking that the bolt-gens do the right thing for a fairly exhaustive test case set (and that it compiles). Note that this doesn't check that we've got the memory assignment pieces worked out. It's got a kind of exotic reliance on the update-mocks in that in order to depend on as little of the wire/ code as possible (we only import wire/wire.h), we include an AUTOGENERATE comment in the test_cases CSV file, and then run update-mocks as part of the build for that file.
2019-07-19 19:01:41 +02:00
clean: tools-test-clean
tools-test-clean:
Makefile: fix occasional race where we fail to compile tools/tests. This simplifies the dependencies: 1. Objs depend on headers, not other objs. 2. Programs depend on objs. 3. A .o file will generally implicitly depend on the .c file it's built from. 4. If a file has a build line, it's often better to list all deps there. 5. I spotted some missing 'make clean' files. The particular problem in this case seems to be that make would use tools/test/gen_test.c before it was ready. It's probably confused by the use of recursive make via update-mocks, so explicitly split that into two stages. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
2019-08-16 03:16:47 +02:00
$(RM) $(TOOL_GEN_HEADER) $(TOOL_GEN_SRC) $(TOOL_TEST_OBJS) $(TOOL_TEST_PROGRAMS)
$(RM) $(TOOL_GEN_SRC:.c=.o) tools/test/enum.o
Reference in New Issue Copy Permalink