From: Alexander Turenko <alexander.turenko@tarantool.org> To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org> Cc: tarantool-patches@dev.tarantool.org Subject: Re: [Tarantool-patches] [PATCH 0/2] ASAN build Date: Tue, 16 Jun 2020 02:04:30 +0300 [thread overview] Message-ID: <20200615230430.d63w2nc5olmggkxw@tkn_work_nb> (raw) In-Reply-To: <a2f7e99b-b264-c304-47cd-42e625261974@tarantool.org> On Tue, Jun 16, 2020 at 12:21:13AM +0200, Vladislav Shpilevoy wrote: > Hi! > > On 15/06/2020 16:01, Alexander Turenko wrote: > > LGTM except broken coverage reporting: > > > > https://travis-ci.org/github/tarantool/tarantool/jobs/698246927 > > > > It looks quite similar to > > https://github.com/tarantool/tarantool/commit/415c05868f95b45a56904d5aa581358aced05efe > > > > Maybe we should add '-o ${CMAKE_BINARY_DIR}/src/box/sql/parse.c' to > > lemon call to write absolute path in #line directives, which may help to > > avoid ambiguity. > > Thanks for noticing and for the proposed fix. I did this: > > - COMMAND ${EXT_BIN_DIR}/lemon -T${EXT_SRC_DIR}/lempar.c ${SQL_SRC_DIR}/parse.y > + COMMAND ${EXT_BIN_DIR}/lemon -T${EXT_SRC_DIR}/lempar.c -o${SQL_BIN_DIR}/parse ${SQL_SRC_DIR}/parse.y Nit: I would use `-o${SQL_BIN_DIR}/parse.c` with explicit `.c` suffix. The effect is the same, but the command line looks more natural. Up to you. > > Now parse.c contains absolute paths in #line directives. But I couldn't > wait if it helped - travis is awfully slow. Lets see if it helped tomorrow, > when the job will be finally done. You may verify it locally: $ cmake . \ -DCMAKE_BUILD_TYPE=Debug \ -DENABLE_BACKTRACE=ON \ -DENABLE_DIST=ON \ -DENABLE_BUNDLED_LIBCURL=OFF \ -DENABLE_GCOV=ON $ make -j $ echo 'print(42)' | ./src/tarantool $ lcov -c -d src -o /dev/null 2>&1 | grep WARNING Note: It seems the output format may vary across lcov versions, I see no WARNING mark on Travis-CI, just the following lines: | Processing box/CMakeFiles/box.dir/sql/parse.c.gcda | Cannot open source file parse.c After your fix the warning disappears. BTW, I see warnings re uri.rl / uri.c locally again: | geninfo: WARNING: could not open /home/alex/p/tarantool-meta/r/t-3/src/lib/uri/src/lib/uri/uri.rl | geninfo: WARNING: could not open /home/alex/p/tarantool-meta/r/t-3/src/lib/uri/src/lib/uri/uri.c | geninfo: WARNING: some exclusion markers may be ignored But don't see them on Travis-CI. This is strange. But it doesn't look related to your patchset: I see the same on master (2.5.0-142-ged935572b).
next prev parent reply other threads:[~2020-06-15 23:05 UTC|newest] Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-06-14 16:24 Vladislav Shpilevoy 2020-06-14 16:24 ` [Tarantool-patches] [PATCH 1/2] sql: don't build sql as a separate library Vladislav Shpilevoy 2020-06-15 15:42 ` Timur Safin 2020-06-14 16:24 ` [Tarantool-patches] [PATCH 2/2] cmake: split UB sanitations into separate flags Vladislav Shpilevoy 2020-06-15 15:41 ` Timur Safin 2020-06-15 22:19 ` Vladislav Shpilevoy 2020-06-15 14:01 ` [Tarantool-patches] [PATCH 0/2] ASAN build Alexander Turenko 2020-06-15 22:21 ` Vladislav Shpilevoy 2020-06-15 23:04 ` Alexander Turenko [this message] 2020-06-15 23:15 ` Vladislav Shpilevoy 2020-06-15 15:43 ` Timur Safin 2020-06-16 8:56 ` 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=20200615230430.d63w2nc5olmggkxw@tkn_work_nb \ --to=alexander.turenko@tarantool.org \ --cc=tarantool-patches@dev.tarantool.org \ --cc=v.shpilevoy@tarantool.org \ --subject='Re: [Tarantool-patches] [PATCH 0/2] ASAN build' \ /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