From: "Jason Pyeron" <jpyeron@pdinc.us>
To: <cygwin-apps@cygwin.com>
Subject: RE: cygport test has zero exit status on failures
Date: Tue, 18 May 2021 15:17:53 -0400 [thread overview]
Message-ID: <03dc01d74c1a$80c3df60$824b9e20$@pdinc.us> (raw)
In-Reply-To: <8735ukejz2.fsf@Otto.invalid>
> -----Original Message-----
> From: ASSI
> Sent: Tuesday, May 18, 2021 12:37 AM
>
> Jason Pyeron writes:
> > What is the historic rationale behind the "OR true" after the make
> > check?
>
> Not historic for the most part, I'd say. Cygport can also do
> cross-builds of packages and in those cases the tests will seldomly work
> (at all or at least partly) unless upstream walked the extra mile.
> Also, due to ATWIL syndrome and other factors, Cygwin is often not
Which is why I want the tests to fail - so it causes patches to be created... and pushed upstream.
> explicitly considered a target platform or (even then) treated wrongly
> in different ways, so even when building natively you will encounter
> your fair share of spurious test fails.
>
> > It seems silly to have to redefine src_test() as {
> > cd ${B}
> > make check
> > }, just to have a failure exit code if the test fail.
>
> It would be equally silly the other way around in a different set of
> circumstances. But yes, making this configurable might be useful, but
> this should then be done in the local configuration, not in the cygport
> file.
If I put it in ~/.config/cygport.conf it will impact all packages, not just the "one". The only place it is limited to applicable package is in the package.cygport file, or am I missing something?
e.g.
$ cat pdfgrep.cygport
NAME="pdfgrep"
VERSION=2.1.2
RELEASE=1
CATEGORY="Text"
SUMMARY="Command-line utility for searching text in PDFs"
DESCRIPTION="Pdfgrep is a tool to search text in PDF files. It works much
like grep, with one distinction: it operates on pages and not on lines."
HOMEPAGE="https://pdfgrep.org/"
SRC_URI="https://pdfgrep.org/download/pdfgrep-${VERSION}.tar.gz"
# git format-patch --stdout v2.1.2..cygwin-2.1.2 > v2.1.2..cygwin-2.1.2.patch
PATCH_URI="v2.1.2..cygwin-2.1.2.patch"
BUILD_REQUIRES="asciidoc gcc-g++ libpoppler-cpp-devel libgcrypt-devel libpcre-devel dejagnu texlive-collection-latex"
src_test() {
cd ${B}
make check
}
next prev parent reply other threads:[~2021-05-18 19:17 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-09 21:12 Jason Pyeron
2021-05-10 5:06 ` ASSI
2021-05-17 22:29 ` Jason Pyeron
2021-05-18 4:36 ` ASSI
2021-05-18 19:17 ` Jason Pyeron [this message]
2021-05-18 20:16 ` Achim Gratz
2021-05-18 20:57 ` Jason Pyeron
2021-05-19 5:16 ` ASSI
2021-05-19 7:05 ` Marco Atzeri
2021-05-19 16:32 ` Jason Pyeron
2021-05-19 17:14 ` Achim Gratz
2021-05-19 17:24 ` Marco Atzeri
2021-05-19 17:30 ` Achim Gratz
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='03dc01d74c1a$80c3df60$824b9e20$@pdinc.us' \
--to=jpyeron@pdinc.us \
--cc=cygwin-apps@cygwin.com \
/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).