Hi,
Thanks for the report. So, the question now is why is fopen
failing here?
I have an amd64 development box, make has built just last week
both outside and inside clean environments, and the tests passed. The
build daemons reported no issues as well. Something has changed.
On Mon, May 19 2014, Yunqiang Su wrote:
> I test in on both amd64 and mips64el.
> I tried to run this step manually, it does hang.
Here is the logs from mipsel:
https://buildd.debian.org/status/fetch.php?pkg=make-dfsg&arch=mipsel&ver=4.0-7&stamp=1400046228
so this used to build.
> Test timed out after 5 seconds
> misc/fopen-fail ......................................... Error
> running /«PKGBUILDDIR»/debian/build-make-guile/tests/../make (expected
> 512; got 14): /«PKGBUILDDIR»/debian/build-make-guile/tests/../make -f
> work/misc/fopen-fail.mk
> FAILED (0/1 passed)
I can see it now as well. I wonder what changed?
I get this with the installed version of make as well as the newly
created one.
This is not guile related:
--8<---------------cut here---------------start------------->8---
Running tests for GNU make on Linux glaurung.internal.golden-gryphon.com
3.14-1-amd64 x86_64
GNU Make 4.0
misc/fopen-fail .........................................
Test timed out after 5 seconds
Error running /tmp/test/make-dfsg-4.0/debian/build-make/tests/../make (expected
512; got 14): /tmp/test/make-dfsg-4.0/debian/build-make/tests/../make -f
work/misc/fopen-fail.mk
Caught signal 14!
FAILED (0/1 passed)
1 Test in 1 Category Failed (See .diff* files in work dir for details) :-(
Makefile:1247: recipe for target 'check-regression' failed
--8<---------------cut here---------------end--------------->8---
It is surprisingly hard to determine what the test is actually
running.
manoj
--
Nachman's Rule: When it comes to foreign food, the less authentic the
better. Gerald Nachman
Manoj Srivastava <sriva...@acm.org> <http://www.golden-gryphon.com/>
4096R/C5779A1C E37E 5EC5 2A01 DA25 AD20 05B6 CF48 9438 C577 9A1C
signature.asc
Description: PGP signature
