From: Jeffrey Walton <noloader@gmail.com>
To: bug-gnulib@gnu.org
Subject: gnulib-tool return codes
Date: Sat, 28 Mar 2020 18:50:25 -0400 [thread overview]
Message-ID: <CAH8yC8kYJaY-4NbmT7QSiyk4SzELDu6whX840LQFh1jb2=YiuA@mail.gmail.com> (raw)
Hi Everyone,
I noticed arpa_inet-c++ tested OK
(https://travis-ci.org/github/noloader/gnulib/jobs/668196404):
****************************************
arpa_inet-c++
****************************************
Tested arpa_inet-c++ OK
But (I'm not sure what was tested):
****************************************
arpa_inet-c++
****************************************
./gnulib-tool: *** file
/home/travis/build/noloader/gnulib/./modules/arpa_inet-c++ not found
./gnulib-tool: *** Stop.
gnulib-tool: warning: module arpa_inet-c++ lacks a License
./gnulib-tool: *** file
/home/travis/build/noloader/gnulib/./modules/arpa_inet-c++ not found
./gnulib-tool: *** Stop.
gnulib-tool: warning: module arpa_inet-c++ doesn't exist
gnulib-tool: warning: module arpa_inet-c++ doesn't exist
configure.ac:8: installing 'build-aux/compile'
configure.ac:4: installing 'build-aux/install-sh'
configure.ac:4: installing 'build-aux/missing'
...
The script is picking up arpa_inet-c++ because it does a find looking
for a filename <module>-tests. In this case arpa_inet-c++-tests is
found.
The test script does check return values
(https://github.com/noloader/gnulib/blob/master/ci_tests/test_modules.sh):
if ! ./gnulib-tool --create-testdir --dir="$test_dir/$module"
"$module" 1>/dev/null;
then
echo "Failed to prepare $module" | tee -a "$result_file"
failed_tests=$((failed_tests+1))
fi
I'm guessing gnulib-tool does not return an error?
Jeff
next reply other threads:[~2020-03-28 22:50 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-03-28 22:50 Jeffrey Walton [this message]
2020-03-29 11:38 ` gnulib-tool return codes Bruno Haible
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
List information: https://lists.gnu.org/mailman/listinfo/bug-gnulib
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAH8yC8kYJaY-4NbmT7QSiyk4SzELDu6whX840LQFh1jb2=YiuA@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=bug-gnulib@gnu.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).