From: Noam Postavsky <npostavs@users.sourceforge.net>
To: Michael Albinus <michael.albinus@gmx.de>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: How to block tests on hydra
Date: Mon, 10 Jul 2017 23:44:05 -0400 [thread overview]
Message-ID: <CAM-tV-8h0SO0WW+RHwpiz6CcE3XKFpdZTFB-xE6TW0fMq3rOcw@mail.gmail.com> (raw)
In-Reply-To: <87y3s8wf6k.fsf@detlef>
On Sat, Jul 1, 2017 at 7:48 AM, Michael Albinus <michael.albinus@gmx.de> wrote:
> recent changes of Tramp block the test on hydra in
> gnu:emacs-trunk:coverage. I've instrumented test/Makefile.in in order to
> see the output of tramp-tests, and it looks like the blocking test is
> tramp-test36-asynchronous-requests. It works properly when running locally.
I'm surprised it does anything at all actually, isn't the (add-to-list
'buffers ...) call a bug? Should be using `push' I think.
- (add-to-list 'buffers (generate-new-buffer "foo")))
+ (push (generate-new-buffer "foo") buffers))
I noticed you added a with-timeout on that test, but it doesn't seem
to be working. Maybe a stronger method would be to use
(start-process "*watchdog*" nil shell-file-name shell-command-switch
(format "sleep 350 ; kill -SIGUSR2 %d" (emacs-pid)))
By the way, I hit the "`tramp-test36-asynchronous-requests' timed out"
message when running locally in an -O0 build, although it succeeds
with an -O2 build. Maybe I just have a weak CPU.
next prev parent reply other threads:[~2017-07-11 3:44 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-01 11:48 How to block tests on hydra Michael Albinus
2017-07-11 3:44 ` Noam Postavsky [this message]
2017-07-11 7:20 ` Michael Albinus
2017-07-11 11:45 ` Noam Postavsky
2017-07-12 12:54 ` Michael Albinus
2017-07-14 1:30 ` Noam Postavsky
2017-07-14 8:58 ` Michael Albinus
2017-07-15 3:07 ` Noam Postavsky
2017-07-15 7:30 ` Michael Albinus
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=CAM-tV-8h0SO0WW+RHwpiz6CcE3XKFpdZTFB-xE6TW0fMq3rOcw@mail.gmail.com \
--to=npostavs@users.sourceforge.net \
--cc=emacs-devel@gnu.org \
--cc=michael.albinus@gmx.de \
/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.