From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Sam Halliday Newsgroups: gmane.emacs.bugs Subject: bug#19983: 24.4; exit-emacs regression in 24.4? Date: Mon, 02 Mar 2015 22:38:42 +0000 Message-ID: <87pp8rc9e5.fsf@gmail.com> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1425337827 15554 80.91.229.3 (2 Mar 2015 23:10:27 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 2 Mar 2015 23:10:27 +0000 (UTC) To: 19983@debbugs.gnu.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Tue Mar 03 00:10:17 2015 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1YSZTX-00040m-Pq for geb-bug-gnu-emacs@m.gmane.org; Tue, 03 Mar 2015 00:10:11 +0100 Original-Received: from localhost ([::1]:60333 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSZTX-0004wW-6m for geb-bug-gnu-emacs@m.gmane.org; Mon, 02 Mar 2015 18:10:11 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:53794) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSZTT-0004uT-9D for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 18:10:08 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSZTP-0000bv-8E for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 18:10:07 -0500 Original-Received: from debbugs.gnu.org ([140.186.70.43]:34646) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSZTP-0000br-3y for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 18:10:03 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.80) (envelope-from ) id 1YSZTO-0002Yf-9z for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 18:10:02 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Sam Halliday Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Mon, 02 Mar 2015 23:10:02 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: report 19983 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: X-Debbugs-Original-To: bug-gnu-emacs@gnu.org Original-Received: via spool by submit@debbugs.gnu.org id=B.14253377729774 (code B ref -1); Mon, 02 Mar 2015 23:10:02 +0000 Original-Received: (at submit) by debbugs.gnu.org; 2 Mar 2015 23:09:32 +0000 Original-Received: from localhost ([127.0.0.1]:33214 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YSZSt-0002Xa-Kt for submit@debbugs.gnu.org; Mon, 02 Mar 2015 18:09:32 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:42573) by debbugs.gnu.org with esmtp (Exim 4.80) (envelope-from ) id 1YSYzI-0001oB-HR for submit@debbugs.gnu.org; Mon, 02 Mar 2015 17:38:57 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSYzC-0004Va-9O for submit@debbugs.gnu.org; Mon, 02 Mar 2015 17:38:51 -0500 Original-Received: from lists.gnu.org ([2001:4830:134:3::11]:42305) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSYzC-0004VW-6I for submit@debbugs.gnu.org; Mon, 02 Mar 2015 17:38:50 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44284) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSYzB-0005Bk-2U for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 17:38:50 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YSYz7-0004UQ-Sf for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 17:38:49 -0500 Original-Received: from mail-we0-x230.google.com ([2a00:1450:400c:c03::230]:35866) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YSYz7-0004UE-La for bug-gnu-emacs@gnu.org; Mon, 02 Mar 2015 17:38:45 -0500 Original-Received: by wevk48 with SMTP id k48so36323862wev.3 for ; Mon, 02 Mar 2015 14:38:44 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=from:to:subject:date:message-id:mime-version:content-type; bh=ZvykIf31s4AIjzqRxqr9XV+LjrVZ1M4OQGuvHeBmWjU=; b=JFjkN2Poy+k4U4e0e+ovUaewuQkIOLr9lAtPmRVjFGKfUOtVYaCiZFrObFBCwdg8Wl pq7Ybqq3EijEfFUP9wDFMORpewdCB2fTXb+2botJV4p2Y/RibU9Dwr5cL6wp9V5Vgw6J 1bpODBgAD4vNKJQud3EDcJglckKsv/5uc70SY9jCFyADx9qDkZtJ2ZfchhCA1G1Wu7W9 u8kxoepRT+q+PaG2jSqVyk62YBf6WohcYq+YCoOtdV8WZopV/ReOyEVqTss0b9uoHNmL 0MbNjbObs3TEayMdYQVn2y540f0Uy5E976wtrq8cLcC9tGJ1iTwjPJnIMXQVhI3z/37R 3bBQ== X-Received: by 10.180.87.33 with SMTP id u1mr39678958wiz.20.1425335924556; Mon, 02 Mar 2015 14:38:44 -0800 (PST) Original-Received: from Samskara (host86-176-86-184.range86-176.btcentralplus.com. [86.176.86.184]) by mx.google.com with ESMTPSA id dn1sm17938736wid.11.2015.03.02.14.38.42 for (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Mon, 02 Mar 2015 14:38:43 -0800 (PST) X-Google-Original-From: Sam Halliday X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Mailman-Approved-At: Mon, 02 Mar 2015 18:09:30 -0500 X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.15 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x X-Received-From: 140.186.70.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.bugs:99997 Archived-At: Hi, When running our emacs integration tests across the matrix of all emacs24 versions, we get a bizarre failure where our test suite reports an exit 0, but the emacs application exits with 1. This only happens in emacs-24.4 and is very repeatable More details, including a link to failing builds and our source code is available on our bug tracker, as well as a suspicious commit in emacs regarding EOL in stdin: https://github.com/ensime/ensime-server/issues/862 Of immediate concern to us is finding a workaround, is there something we can do to recover the original behaviour? Bleeding stdin, or piping some text to stdin? -- Best regards, Sam