GNU bug report logs -
#53504
28.0.91 `make check && make install` failing for GNU Emacs 28.0.91 ??
Previous Next
Reported by: Auntie Carol <centzon.totochtin <at> gmail.com>
Date: Mon, 24 Jan 2022 15:39:01 UTC
Severity: normal
Tags: moreinfo
Found in version 28.0.91
Done: Lars Ingebrigtsen <larsi <at> gnus.org>
Bug is archived. No further changes may be made.
To add a comment to this bug, you must first unarchive it, by sending
a message to control AT debbugs.gnu.org, with unarchive 53504 in the body.
You can then email your comments to 53504 AT debbugs.gnu.org in the normal way.
Toggle the display of automated, internal messages from the tracker.
Report forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53504
; Package
emacs
.
(Mon, 24 Jan 2022 15:39:01 GMT)
Full text and
rfc822 format available.
Acknowledgement sent
to
Auntie Carol <centzon.totochtin <at> gmail.com>
:
New bug report received and forwarded. Copy sent to
bug-gnu-emacs <at> gnu.org
.
(Mon, 24 Jan 2022 15:39:01 GMT)
Full text and
rfc822 format available.
Message #5 received at submit <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
I've been building from Savannah's main branch for the last couple of
months. Yesterday I decided to "roll back" to 28.0.91 and ran into the
following errors:
2 unexpected results:
FAILED emacs-tests/bwrap/allows-stdout
FAILED emacs-tests/seccomp/allows-stdout
And compilation does not complete.
All works as it should when ` check` is removed from the make directive.
kernel (supplied by Pop!_OS): 5.15.8-76051508-generic
gcc (Ubuntu 11.2.0-7ubuntu2): 11.2.0
Don't know if this is a bug or my system. Anyway, thanks!
CT
=== guts of the build script ===
export CC="gcc-10"
./autogen.sh
./configure \
--with-native-compilation \
--with-gnutls=ifavailable \
--with-json \
--with-jpeg \
--with-pgtk \
--with-png \
--with-rsvg \
--with-tiff \
--with-wide-int \
--with-xft \
--with-xinput2 \
--with-xml2 \
--with-xpm
make check && sudo make install
=== cat ./test/src/emacs-tests.log ===
cat ./test/src/emacs-tests.log
Running 7 tests (2022-01-23 14:59:43+0000, selector ‘(not (or (tag
:expensive-test) (tag :unstable) (tag :nativecomp)))’)
Test emacs-tests/bwrap/allows-stdout backtrace:
signal(ert-test-failed (((should (eql status 0)) :form (eql 159 0) :
ert-fail(((should (eql status 0)) :form (eql 159 0) :value nil))
#f(compiled-function () #<bytecode 0x91b1991a23835a9>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name emacs-tests/bwrap/allows-stdout :docu
ert-run-or-rerun-test(#s(ert--stats :selector (not (or (tag :expensi
ert-run-tests((not (or (tag :expensive-test) (tag :unstable) (tag :n
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable) (
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "src/emacs-tests" "--eval"
command-line()
normal-top-level()
Test emacs-tests/bwrap/allows-stdout condition:
Info: Process output:
(ert-test-failed
((should
(eql status 0))
:form
(eql 159 0)
:value nil))
FAILED 1/7 emacs-tests/bwrap/allows-stdout (0.227544 sec)
passed 2/7 emacs-tests/seccomp/absent-file (0.044747 sec)
Test emacs-tests/seccomp/allows-stdout backtrace:
signal(ert-test-failed (((should (eql status 0)) :form (eql "Bad sys
ert-fail(((should (eql status 0)) :form (eql "Bad system call" 0) :v
#f(compiled-function () #<bytecode 0x1354e77c9d8677f7>)()
ert--run-test-internal(#s(ert--test-execution-info :test #s(ert-test
ert-run-test(#s(ert-test :name emacs-tests/seccomp/allows-stdout :do
ert-run-or-rerun-test(#s(ert--stats :selector (not (or ... ... ...))
ert-run-tests((not (or (tag :expensive-test) (tag :unstable) (tag :n
ert-run-tests-batch((not (or (tag :expensive-test) (tag :unstable) (
ert-run-tests-batch-and-exit((not (or (tag :expensive-test) (tag :un
eval((ert-run-tests-batch-and-exit '(not (or (tag :expensive-test) (
command-line-1(("-L" ":." "-l" "ert" "-l" "src/emacs-tests" "--eval"
command-line()
normal-top-level()
Test emacs-tests/seccomp/allows-stdout condition:
Info: Process output:
(ert-test-failed
((should
(eql status 0))
:form
(eql "Bad system call" 0)
:value nil))
FAILED 3/7 emacs-tests/seccomp/allows-stdout (0.277550 sec)
passed 4/7 emacs-tests/seccomp/empty-file (0.040075 sec)
passed 5/7 emacs-tests/seccomp/file-too-large (0.124284 sec)
passed 6/7 emacs-tests/seccomp/forbids-subprocess (0.307874 sec)
passed 7/7 emacs-tests/seccomp/invalid-file-size (0.049196 sec)
Ran 7 tests, 5 results as expected, 2 unexpected (2022-01-23 14:59:45+0000,
1.329448 sec)
2 unexpected results:
FAILED emacs-tests/bwrap/allows-stdout
FAILED emacs-tests/seccomp/allows-stdout
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53504
; Package
emacs
.
(Mon, 24 Jan 2022 15:46:01 GMT)
Full text and
rfc822 format available.
Message #8 received at 53504 <at> debbugs.gnu.org (full text, mbox):
Auntie Carol <centzon.totochtin <at> gmail.com> writes:
> I've been building from Savannah's main branch for the last couple of months.
> Yesterday I decided to "roll back" to 28.0.91 and ran into the following errors:
>
> 2 unexpected results:
> FAILED emacs-tests/bwrap/allows-stdout
> FAILED emacs-tests/seccomp/allows-stdout
>
> And compilation does not complete.
> All works as it should when ` check` is removed from the make directive.
There have been seccomp fixes in the emacs-28 branch earlier today --
can you try to update and rebuild Emacs and check whether the problem is
still present?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Added tag(s) moreinfo.
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Mon, 24 Jan 2022 15:46:02 GMT)
Full text and
rfc822 format available.
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53504
; Package
emacs
.
(Mon, 24 Jan 2022 18:34:03 GMT)
Full text and
rfc822 format available.
Message #13 received at 53504 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
On Mon, Jan 24, 2022 at 3:45 PM Lars Ingebrigtsen <larsi <at> gnus.org> wrote:
> Auntie Carol <centzon.totochtin <at> gmail.com> writes:
>
> > I've been building from Savannah's main branch for the last couple of
> months.
> > Yesterday I decided to "roll back" to 28.0.91 and ran into the following
> errors:
> >
> > 2 unexpected results:
> > FAILED emacs-tests/bwrap/allows-stdout
> > FAILED emacs-tests/seccomp/allows-stdout
> >
> > And compilation does not complete.
> > All works as it should when ` check` is removed from the make directive.
>
> There have been seccomp fixes in the emacs-28 branch earlier today --
> can you try to update and rebuild Emacs and check whether the problem is
> still present?
>
> There is still a failure to compile. albeit with different errors now:
~/src/emacs on HEAD (d193801)
== >>
GEN src/xml-tests.log
make[3]: Leaving directory '/home/yearluk/src/emacs/test'
make[2]: [Makefile:335: check-doit] Error 2 (ignored)
SUMMARY OF TEST RESULTS
-----------------------
Files examined: 375
Ran 5608 tests, 5466 results as expected, 33 unexpected, 109 skipped
10 files contained unexpected results:
src/emacs-tests.log
lisp/wdired-tests.log
lisp/simple-tests.log
lisp/progmodes/xref-tests.log
lisp/progmodes/project-tests.log
lisp/gnus/mml-sec-tests.log
lisp/files-tests.log
lisp/cedet/semantic-utest-ia.log
lisp/autorevert-tests.log
lisp/net/tramp-tests.log
make[2]: *** [Makefile:336: check-doit] Error 1
make[2]: Leaving directory '/home/yearluk/src/emacs/test'
make[1]: *** [Makefile:305: check] Error 2
make[1]: Leaving directory '/home/yearluk/src/emacs/test'
make: *** [Makefile:994: check] Error 2
[Message part 2 (text/html, inline)]
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53504
; Package
emacs
.
(Mon, 24 Jan 2022 18:37:01 GMT)
Full text and
rfc822 format available.
Message #16 received at 53504 <at> debbugs.gnu.org (full text, mbox):
Auntie Carol <centzon.totochtin <at> gmail.com> writes:
> There is still a failure to compile. albeit with different errors now:
With "failure to compile", you mean that the tests fail?
> 10 files contained unexpected results:
> src/emacs-tests.log
> lisp/wdired-tests.log
> lisp/simple-tests.log
> lisp/progmodes/xref-tests.log
> lisp/progmodes/project-tests.log
> lisp/gnus/mml-sec-tests.log
> lisp/files-tests.log
> lisp/cedet/semantic-utest-ia.log
> lisp/autorevert-tests.log
> lisp/net/tramp-tests.log
So you got (at least) eight new test failures in the version from today
compared to the one from yesterday? That's very odd.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
Information forwarded
to
bug-gnu-emacs <at> gnu.org
:
bug#53504
; Package
emacs
.
(Tue, 22 Feb 2022 13:55:01 GMT)
Full text and
rfc822 format available.
Message #19 received at 53504 <at> debbugs.gnu.org (full text, mbox):
Lars Ingebrigtsen <larsi <at> gnus.org> writes:
> So you got (at least) eight new test failures in the version from today
> compared to the one from yesterday?
More information was requested, but no response was given within a
month, so I'm closing this bug report. If the problem still exists,
please respond to this email and we'll reopen the bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
bug closed, send any further explanations to
53504 <at> debbugs.gnu.org and Auntie Carol <centzon.totochtin <at> gmail.com>
Request was from
Lars Ingebrigtsen <larsi <at> gnus.org>
to
control <at> debbugs.gnu.org
.
(Tue, 22 Feb 2022 13:55:02 GMT)
Full text and
rfc822 format available.
bug archived.
Request was from
Debbugs Internal Request <help-debbugs <at> gnu.org>
to
internal_control <at> debbugs.gnu.org
.
(Wed, 23 Mar 2022 11:24:04 GMT)
Full text and
rfc822 format available.
This bug report was last modified 3 years and 88 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.