Andreas Schwab <schwab <at> suse.de> writes: > > What does it mean that the features/output-sync test always times out? > Here is a typical output: > > features/output-sync .................................... > Test timed out after 30 seconds > Error running /home/abuild/rpmbuild/BUILD/make-4.2/tests/../make (expected 0; got 14): > /home/abuild/rpmbuild/BUILD/make-4.2/tests/../make -f work/features/output-sync.mk.1 -j --output-sync=target > > Caught signal 14! > > Test timed out after 30 seconds
I am seeing the same issue. It seems there is a regression with 4.2. It occurs with 4.2 an 4.2.1: features/output-sync .................................... Test timed out after 30 seconds Error running /var/tmp/build-pkg-6399/obj/make-4.2/tests/../make (expected 0; got 14): /var/tmp/build-pkg-6399/obj/make-4.2/tests/../make -f work/features/output-sync.mk -j -Orecurse Caught signal 14! I have checked against 4.1 and there it is working: features/output-sync .................................... ok (14 passed) Same for 4.0: features/output-sync .................................... ok (13 passed) The system is Debian Testing (stretch/sid) with kernel 4.6.2 on an AMD FX 8350 (AMD64). _______________________________________________ Bug-make mailing list Bug-make@gnu.org https://lists.gnu.org/mailman/listinfo/bug-make
