mirror of
https://github.com/zeek/zeek.git
synced 2025-10-02 06:38:20 +00:00
Clean up fully after successful Docker btests
If we leave files sitting around, we trigger a Docker image double-build in CI, because the build runs once, gets tested, and then gets run again when we push the Docker image: the additional btest files cause Docker to detect a different source tree, causing an image layer violation. Also rename "cleanup" target to "clean", to align with rest of our tree.
This commit is contained in:
parent
bdb5222c27
commit
1dd6c1d716
1 changed files with 3 additions and 3 deletions
|
@ -1,11 +1,11 @@
|
||||||
DIAG=diag.log
|
DIAG=diag.log
|
||||||
BTEST=../../auxil/btest/btest
|
BTEST=../../auxil/btest/btest
|
||||||
|
|
||||||
all: cleanup btest-verbose
|
all: btest-verbose clean
|
||||||
|
|
||||||
# Showing all tests.
|
# Showing all tests.
|
||||||
btest-verbose:
|
btest-verbose:
|
||||||
@$(BTEST) -d -j -f $(DIAG)
|
@$(BTEST) -d -j -f $(DIAG)
|
||||||
|
|
||||||
cleanup:
|
clean:
|
||||||
@rm -f $(DIAG)
|
@rm -rf $(DIAG) .tmp .btest.failed.dat
|
||||||
|
|
Loading…
Add table
Add a link
Reference in a new issue