[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC
From: |
J.P. |
Subject: |
bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC |
Date: |
Mon, 18 Apr 2022 07:30:23 -0700 |
User-agent: |
Gnus/5.13 (Gnus v5.13) Emacs/29.0.50 (gnu/linux) |
Michael Albinus <michael.albinus@gmx.de> writes:
> Thinking about,
>
> make_params: "-k -C test check-lisp-erc check-lisp-erc-erc-d
> SELECTOR='$(SELECTOR_EXPENSIVE)'"
>
> is more future-proof. See test/README.
Ah, so it's right there in black and white, plain as day! Further
evidence I need to be culled from the herd. Thanks (of course).
On a tenuously related note, for some reason, I'm unable to run
make -C test -j<NN> check-lisp-erc ...
without incurring a "'warning: jobserver unavailable: using -j1". Plain
old -j without the <NN> works fine, and other targets I've tried, like
check and check-expensive, seem unaffected.
(Apologies if this is nonsense or old news or should be discussed
elsewhere: a cursory search on the bug tracker and the help list came up
empty, and the few hits on emacs-devel for "jobserver unavailable" were
all build-related red herrings, like [1].)
FWIW, the course of action prescribed by the info node "(make) Error
Messages", namely, prepending a "+", seems to remedy the problem.
diff --git a/test/Makefile.in b/test/Makefile.in
index 3b6e116e65..c0256d770d 100644
--- a/test/Makefile.in
+++ b/test/Makefile.in
@@ -247,7 +247,7 @@ define subdir_template
SUBDIR_TARGETS += check-$(subst /,-,$(1))
.PHONY: check-$(subst /,-,$(1))
check-$(subst /,-,$(1)):
- @${MAKE} check LOGFILES="$(patsubst %.el,%.log, \
+ +@${MAKE} check LOGFILES="$(patsubst %.el,%.log, \
$(patsubst $(srcdir)/%,%,$(wildcard ${srcdir}/$(1)/*.el)))"
endef
Sorry if that's just noise. As you're well aware, I know nothing! Thanks
again.
[1] https://lists.gnu.org/archive/html/emacs-devel/2010-05/msg00720.html
- bug#48598: Questions regarding layout and composition of tests (bug#48598), (continued)
- bug#48598: Questions regarding layout and composition of tests (bug#48598), Lars Ingebrigtsen, 2022/04/10
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/11
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Lars Ingebrigtsen, 2022/04/11
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/11
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Lars Ingebrigtsen, 2022/04/11
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/12
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/15
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/15
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/15
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/17
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC,
J.P. <=
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/18
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, J.P., 2022/04/21
- bug#48598: 28.0.50; buffer-naming collisions involving bouncers in ERC, Michael Albinus, 2022/04/22