Re: Unicycler: trying to run tests during the build process
Hi Liubov,
On Sat, Sep 08, 2018 at 01:36:10PM +0200, Liubov Chuprikova wrote:
> > In general I have no problem to skip tests in a
> > package. There can be different reasons for failing tests - sometimes
> > the test itself is wrong.
>
> The tests itself are definitely correct.
OK.
> > So if we know why a test fails excluding it
> > is perfectly fine.
>
> I tried to take a closer look today. The problem is when building in a
> clean chroot I get the following messages (many of them along with the
> build):
>
> tput: No value for $TERM and no -T specified
Tput is from package ncurses-bin. If it needs $TERM set may be it helps
to export xterm or vt100 in d/rules. I've checked codesearch
https://codesearch.debian.net/search?q=file%3Adebian%2Frules+TERM
and found something like
ifneq ($(filter $(TERM),$(KNOWN_TERM)),)
xsetenv("TERM", "dumb", 1);
xsetenv("TERM", "vt102", 1);
export TERM=linux
The later three are from some version of util-linux (not the one in
unstable any more)
> Unfortunately, I cannot trace where they come from. Then, there are two
> tests that run unicycler-runner.py with --help and check if stderr is equal
> to 0, but in my case stderr becomes equal to the same message. Have you
> seen this message before? Can you reproduce it?
I've noticed skip_failing_tests.patch. What do you mean by "reproduce"?
Should I deactivate the patch and see whether I observe the error? What
exactly is the error message?
Kind regards
Andreas.
--
http://fam-tille.de
Reply to: