From: Alexander Turenko <alexander.turenko@tarantool.org> To: "Alexander V. Tikhonov" <avtikhon@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 4/4] ci: integrate Jepsen tests to GitLab CI Date: Thu, 17 Sep 2020 18:25:41 +0300 [thread overview] Message-ID: <20200917152541.n4mczy2uu6sl2edo@tkn_work_nb> (raw) In-Reply-To: <20200917071224.GA32661@hpalx> > > +jepsen: > > + <<: *docker_test_definition > > + script: > > + - ${GITLAB_MAKE} test_jepsen > > + stage: long_tests > > + when: manual > > + tags: > > + - mcs_jepsen_docker > > + artifacts: > > + paths: > > + - jepsen-tests-prefix/src/jepsen-tests/store > > + expire_in: 1 week > > + > > Let's use more time for artifacts store, may be 6 months. I agree. We sometimes return to bad results after some significant delay. > > -deps_debian: > > +deps_debian: $(BIN_DIR)/clojure $(BIN_DIR)/lein $(BIN_DIR)/terraform > > apt-get update ${APT_EXTRA_FLAGS} && apt-get install -y -f \ > > build-essential cmake coreutils sed \ > > libreadline-dev libncurses5-dev libyaml-dev libssl-dev \ > > I don't think we need to add jepsen's new targets to the base one, let's > move it to 'deps_debian_jepsen'. I agree, it is a bit strange to install jepsen dependencies for all jobs (when a separate jepsen goal exists at least). > > +deps_debian_jepsen: > > + apt-get update ${APT_EXTRA_FLAGS} && apt-get install -y -f \ > > + openjdk-8-jre openjdk-8-jre-headless libjna-java gnuplot graphviz \ > > + zip unzip openssh-client jq > > + > > +$(BIN_DIR)/clojure: deps_debian_jepsen > > + curl $(CLOJURE_URL) | sudo bash > > + > > +$(BIN_DIR)/lein: deps_debian_jepsen > > + curl $(LEIN_URL) > $@ > > + chmod a+x $@ > > + $@ version > > + > > +$(BIN_DIR)/terraform: deps_debian_jepsen > > + curl -O $(TERRAFORM_URL) > > + unzip -o $(TERRAFORM_NAME) terraform -d $(dir $@) > > + rm -f $(TERRAFORM_NAME) > > + > > Do we really need standalone targets that will not be used in separate? > This file is in makefile style, but not makefile in real, it has > standalone targets that provides some process meanings, like: > - prepare deps > - build > - test In my understanding it is Makefile anyway and it is usual for a Makefile to use a file name as a goal (so the goal will be considered as made if the file exists, if the goal is not marked as .PHONY). > > + > > +# ################### > > +# Jepsen testing > > +# ################### > > + > > +test_jepsen: deps_debian > > + cmake . -DCMAKE_BUILD_TYPE=RelWithDebInfo -DENABLE_WERROR=ON > > + make jepsen-single > > Let's use deps_debian_jepsen here. I would do it this way, yep.
next prev parent reply other threads:[~2020-09-17 15:25 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-09-16 7:07 [Tarantool-patches] [PATCH 0/4] Integrate Jepsen tests to CI sergeyb 2020-09-16 7:07 ` [Tarantool-patches] [PATCH 1/4] extra: add Terraform config files sergeyb 2020-09-18 14:20 ` Alexander V. Tikhonov 2020-09-16 7:07 ` [Tarantool-patches] [PATCH 2/4] cmake: add targets to run Jepsen tests sergeyb 2020-09-18 14:23 ` Alexander V. Tikhonov 2020-09-16 7:07 ` [Tarantool-patches] [PATCH 3/4] tools: add script " sergeyb 2020-09-18 14:32 ` Alexander V. Tikhonov 2020-09-16 7:07 ` [Tarantool-patches] [PATCH 4/4] ci: integrate Jepsen tests to GitLab CI sergeyb 2020-09-17 7:12 ` Alexander V. Tikhonov 2020-09-17 15:25 ` Alexander Turenko [this message] 2020-09-18 12:28 ` Sergey Bronnikov 2020-09-18 12:34 ` Alexander V. Tikhonov 2020-09-18 12:33 ` Sergey Bronnikov 2020-09-18 15:03 ` [Tarantool-patches] [PATCH 0/4] Integrate Jepsen tests to CI Kirill Yukhin
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20200917152541.n4mczy2uu6sl2edo@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=avtikhon@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 4/4] ci: integrate Jepsen tests to GitLab CI' \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox