From: "Clément Pit--Claudel" <clement.pit@gmail.com>
To: emacs-devel@gnu.org
Subject: Re: Please test the merge of the concurrency branch
Date: Fri, 9 Dec 2016 18:09:03 -0500 [thread overview]
Message-ID: <77a8b755-d131-ec4c-0962-dc0132755af3@gmail.com> (raw)
In-Reply-To: <87mvg52k7o.fsf@codethink.co.uk>
[-- Attachment #1.1: Type: text/plain, Size: 2423 bytes --]
It builds fine on my machine, and it doesn't seem to break Proof General (which makes heavy use of subprocesses), nor any of my packages' test suites :)
However, make check seems to fail:
make[2]: Entering directory '/build/emacs/master-clean/doc/misc'
make[2]: Nothing to be done for 'info'.
make[2]: Leaving directory '/build/emacs/master-clean/doc/misc'
GEN info/dir
make[1]: Leaving directory '/build/emacs/master-clean'
make -C test check
make[1]: Entering directory '/build/emacs/master-clean/test'
rm -f *.tmp
test ! -d ./automated
Makefile:159: recipe for target 'check-no-automated-subdir' failed
make[1]: *** [check-no-automated-subdir] Error 1
make[1]: Leaving directory '/build/emacs/master-clean/test'
Makefile:964: recipe for target 'check' failed
make: *** [check] Error 2
This is most likely a sign of my inability to run the test suite properly, of course.
Good job on the merge! Exciting stuff.
Cheers,
Clément.
On 2016-12-09 10:30, Robert Marshall wrote:
> Eli Zaretskii <eliz@gnu.org> writes:
>
>> I've pushed to the Emacs Git repository a new branch named
>> 'test-concurrency'. It's the result of merging the concurrency branch
>> with a week-old master, followed by fixing a few bugs I found (after
>> resolving the merge conflicts).
>>
>> This is tested on Trisquel GNU/Linux (x86_64 build) and on MS-Windows
>> (x86 build with wide ints). "Tested" here means that it builds,
>> passes the test suite as well as the master version on the same
>> machine, passes the new tests that test the concurrency features, and
>> the basic functionalities that are affected by the concurrency-related
>> changes -- subprocesses and networking -- work as well as they do on
>> master.
>>
>> The new concurrency features are not thoroughly tested, so I expect
>> bugs to be reported when people start using them seriously. I don't
>> think that should preclude us from landing this on master, though, as
>> long as the "usual", a.k.a. "single-threaded" Emacs works as well as
>> the master branch.
>>
>
> It fails to build for me
>
> CC category.o
> In file included from thread.h:22:0,
> from lisp.h:797,
> from category.c:33:
> regex.h:438:9: error: unknown type name ‘ssize_t’
> (and a few more complaints about ssize_t)
>
> Debian GNU/Linux 8.6 (jessie)
>
> Robert
>
>
>
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-12-09 23:09 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-12-09 14:45 Please test the merge of the concurrency branch Eli Zaretskii
2016-12-09 15:30 ` Robert Marshall
2016-12-09 16:26 ` Eli Zaretskii
2016-12-09 16:40 ` Paul Eggert
2016-12-09 16:54 ` Eli Zaretskii
2016-12-09 16:58 ` jpff
2016-12-09 17:06 ` Eli Zaretskii
2016-12-09 16:52 ` Robert Marshall
2016-12-09 23:09 ` Clément Pit--Claudel [this message]
2016-12-10 7:14 ` Eli Zaretskii
2016-12-10 15:05 ` Clément Pit--Claudel
2016-12-10 15:50 ` Eli Zaretskii
2016-12-09 22:33 ` David Caldwell
2016-12-10 6:50 ` Eli Zaretskii
2016-12-10 13:14 ` Alan Third
2016-12-10 14:06 ` Eli Zaretskii
2016-12-09 22:58 ` Karl Fogel
2016-12-10 7:09 ` Eli Zaretskii
2016-12-12 3:05 ` Karl Fogel
2016-12-09 23:19 ` Andrés Ramírez
2016-12-10 7:14 ` Eli Zaretskii
2016-12-10 8:09 ` Andreas Politz
2016-12-10 9:07 ` Eli Zaretskii
2016-12-10 16:05 ` Joseph Mingrone
2016-12-10 17:50 ` Eli Zaretskii
2016-12-10 16:33 ` Achim Gratz
2016-12-10 16:56 ` Filipe Silva
2016-12-10 17:56 ` Eli Zaretskii
2016-12-10 17:52 ` Eli Zaretskii
2016-12-10 17:36 ` Concurrency has landed (was: Please test the merge of the concurrency branch) Eli Zaretskii
2016-12-10 18:24 ` Concurrency has landed Eli Zaretskii
2016-12-10 18:26 ` raman
2016-12-10 18:36 ` Eli Zaretskii
2016-12-10 19:22 ` Paul Eggert
2016-12-22 4:52 ` Daniel Colascione
2016-12-22 19:23 ` Paul Eggert
2016-12-22 19:32 ` Daniel Colascione
2016-12-22 19:56 ` Paul Eggert
2016-12-24 0:52 ` Stefan Monnier
2016-12-24 1:51 ` Paul Eggert
2016-12-24 4:49 ` Stefan Monnier
2016-12-24 5:04 ` Paul Eggert
2016-12-22 19:57 ` Davis Herring
2016-12-13 12:28 ` Phillip Lord
2016-12-13 16:09 ` Eli Zaretskii
2016-12-11 2:51 ` Please test the merge of the concurrency branch Ken Raeburn
2016-12-11 3:33 ` Eli Zaretskii
2016-12-11 19:40 ` Peter Wang
2016-12-11 20:31 ` Eli Zaretskii
2016-12-11 9:11 ` Michael Albinus
2016-12-11 13:54 ` Ken Raeburn
2016-12-11 15:14 ` Tramp and concurrency (was: Please test the merge of the concurrency branch) Michael Albinus
2016-12-11 15:45 ` Please test the merge of the concurrency branch Eli Zaretskii
2016-12-11 18:30 ` Daimrod
2016-12-11 18:42 ` Eli Zaretskii
2016-12-11 19:02 ` Daimrod
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=77a8b755-d131-ec4c-0962-dc0132755af3@gmail.com \
--to=clement.pit@gmail.com \
--cc=emacs-devel@gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).