ASAN on Travis

[Bram Moolenaar]

Travis reported an error in the popup window test:

Caught exception in Test_popup_beval(): Vim(call):E958: Job already finished @ function RunTheTest[40]..Test_popup_beval[40]..VerifyScreenDump, line 19

This indicates that the Vim instance running in the terminal window died
before the screenshot could be made. I had to guess why that happens
(hopefully fixed by 8.1.1648).

Apparently the error deteced by ASAN that makes this Vim instance die is
not logged, or at least it does not apppear in the logs we collect. Can
we somehow also pick up these ASAN logs? It will be very helpful in
pinpointing problems.

--
Q: Is selling software the same as selling hardware?
A: No, good hardware is sold new, good software has already been used by many.

/// Bram Moolenaar -- Br...@Moolenaar.net -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///

[Dominique Pellé]

Bram Moolenaar <Br...@moolenaar.net> wrote:

> Travis reported an error in the popup window test:
>
> Caught exception in Test_popup_beval(): Vim(call):E958: Job already finished @ function RunTheTest[40]..Test_popup_beval[40]..VerifyScreenDump, line 19
>
> This indicates that the Vim instance running in the terminal window died
> before the screenshot could be made. I had to guess why that happens
> (hopefully fixed by 8.1.1648).
>
> Apparently the error deteced by ASAN that makes this Vim instance die is
> not logged, or at least it does not apppear in the logs we collect. Can
> we somehow also pick up these ASAN logs? It will be very helpful in
> pinpointing problems.

asan build of vim just reports errors on stderr, and I assume
stderr is captured in Travis log.

Which Travis build did not report the asan error?

I looked at the latest failure and I could see a asan
error at the bottom of the log:

https://api.travis-ci.org/v3/job/555423933/log.txt

Regards
Dominique

[Bram Moolenaar]

Ah, so it's there in the raw log. I was looking at the test output and
it doesn't show there... Ah, there is a mysterious "while read log;
do" line that is collapsed. We should not collapse that part, it's
short when everything is OK and we need to see the error when it's not
OK. Looks like it's this part in the config:

asan_symbolize: &asan_symbolize
- |
while read log; do
asan_symbolize < "${log}"
done < <(find . -type f -name 'asan.*' -size +0)

Perhaps we can remove that "|" to avoid collapsing?

--
The question is: What do you do with your life?
The wrong answer is: Become the richest guy in the graveyard.
(billionaire and Oracle founder Larry Ellison)