From: Karl Fogel <kfogel@red-bean.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Tom Tromey <tom@tromey.com>, Ken Raeburn <raeburn@raeburn.org>,
emacs-devel@gnu.org
Subject: Re: Please test the merge of the concurrency branch
Date: Fri, 09 Dec 2016 16:58:24 -0600 [thread overview]
Message-ID: <87a8c46773.fsf@red-bean.com> (raw)
In-Reply-To: <83oa0lgnzx.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 09 Dec 2016 16:45:22 +0200")
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.
>
>I'd appreciate if people who can afford it checked out this branch and
>tested it on their systems, to make the probability of bad problems,
>which I estimate as low, to be even lower, and thus to avoid the
>danger of breaking master too hard.
Built revision ad03e7af8 to get "GNU Emacs 26.0.50.1 (x86_64-pc-linux-gnu, GTK+ Version 3.22.4) of 2016-12-09" (on a Debian GNU/Linux 'testing' distro, dist-upgraded as of this morning).
I used Emacs with no issues for a few hours, including running two shell buffers (often with simultaneous active command output), reading/writing email with Gnus, and doing various Org Mode things.
By the way, I also built an earlier revision (I don't remember the rev id now) from the branch, and used it for about an hour, likewise with no problems. Then at some point I did 'git pull' and was surprised to get a merge -- surprised, because I had no local modifications. I assume this means you or someone rebased the branch at some point? Anyway, I just deleted the branch locally and refetched it, resulting in rev ad03e7af8, which I then built and used for the rest of the day.
Best regards,
-Karl
next prev parent reply other threads:[~2016-12-09 22:58 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8c46773.fsf@red-bean.com \
--to=kfogel@red-bean.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=raeburn@raeburn.org \
--cc=tom@tromey.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.