unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: Arun Isaac <arunisaac@systemreboot.net>
Cc: 27673@debbugs.gnu.org
Subject: [bug#27673] Failing tests
Date: Fri, 14 Jul 2017 16:49:10 +0300	[thread overview]
Message-ID: <87zic72ko9.fsf@gmail.com> (raw)
In-Reply-To: <52c335a3.AEQANFFEJwgAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZaLFC@mailjet.com>

Arun Isaac <arunisaac@systemreboot.net> writes:
> Could you also package the tests? You'll need something very similar to
> what the emacs-which-key package has.

Sure, but they fails :-)

(arguments
 `(#:phases
   (modify-phases %standard-phases
     (add-before 'install 'check
       (lambda _
         (zero? (system* "emacs" "--batch" "-L" "."
                         "-l" "org-pomodoro-tests.el"
                         "-f" "ert-run-tests-batch-and-exit")))))))

Running 2 tests (2017-07-14 13:09:26+0000)
Test org-pomodoro-expires-when-last-clockin-is-new backtrace:
  (let ((fn-5 (function equal)) (args-6 (list nil (org-pomodoro-expire
  (let ((org-pomodoro-last-clock-in (current-time)) (org-pomodoro-expi
  (lambda nil (let ((org-pomodoro-last-clock-in (current-time)) (org-p
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test org-pomodoro-expires-when-last-cloc
  ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test o
  ert-run-tests(t #[385 "\306\307\"\203G\211\211G\310U\203\0\211@\20
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  command-line-1(("-L" "." "-l" "org-pomodoro-tests.el" "-f" "ert-run-
  command-line()
  normal-top-level()
Test org-pomodoro-expires-when-last-clockin-is-new condition:
    (void-function org-pomodoro-expires-p)
   FAILED  1/2  org-pomodoro-expires-when-last-clockin-is-new
Test org-pomodoro-expires-when-last-clockin-too-old backtrace:
  (let ((fn-0 (function equal)) (args-1 (list t (org-pomodoro-expires-
  (let ((org-pomodoro-last-clock-in (quote (0 120 0 0))) (org-pomodoro
  (lambda nil (let ((org-pomodoro-last-clock-in (quote (0 120 0 0))) (
  ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
  ert-run-test([cl-struct-ert-test org-pomodoro-expires-when-last-cloc
  ert-run-or-rerun-test([cl-struct-ert--stats t [[cl-struct-ert-test o
  ert-run-tests(t #[385 "\306\307\"\203G\211\211G\310U\203\0\211@\20
  ert-run-tests-batch(nil)
  ert-run-tests-batch-and-exit()
  command-line-1(("-L" "." "-l" "org-pomodoro-tests.el" "-f" "ert-run-
  command-line()
  normal-top-level()
Test org-pomodoro-expires-when-last-clockin-too-old condition:
    (void-function org-pomodoro-expires-p)
   FAILED  2/2  org-pomodoro-expires-when-last-clockin-too-old

Ran 2 tests, 0 results as expected, 2 unexpected (2017-07-14 13:09:26+0000)

2 unexpected results:
   FAILED  org-pomodoro-expires-when-last-clockin-is-new
   FAILED  org-pomodoro-expires-when-last-clockin-too-old

>> +    (propagated-inputs
>> +     `(("emacs-alert" ,emacs-alert)))
>> +    (home-page "https://github.com/lolownia/org-pomodoro")
>> +    (synopsis "Pomodoro technique for org-mode")
>> +    (description
>> +     "@code{emacs-org-pomodoro} adds very basic support for Pomodoro technique
>> +in Emacs org-mode.")
>
> Could you extend the description a little more, perhaps by paraphrasing
> paragraph 3 of README.md...?

Sure, I think it's appropriate:

@code{emacs-org-pomodoro} adds very basic support for Pomodoro technique
in Emacs org-mode.

Run @code{M-x org-pomodoro} for the task at point or select one of the
last tasks that you clocked time for.  Each clocked-in pomodoro starts a
timer of 25 minutes and after each pomodoro a break timer of 5 minutes
is started automatically.  Every 4 breaks a long break is started with
20 minutes.  All values are customizable.

  parent reply	other threads:[~2017-07-14 13:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-12 20:47 [bug#27673] [PATCH] gnu: Add emacs-org-pomodoro Oleg Pykhalov
2017-07-14 11:55 ` Arun Isaac
     [not found] ` <52c335a3.AEQANFFEJwgAAAAAAAAAAAPNhpIAAAACwQwAAAAAAAW9WABZaLFC@mailjet.com>
2017-07-14 13:49   ` Oleg Pykhalov [this message]
2017-07-14 14:11     ` [bug#27673] Failing tests Arun Isaac
2017-07-14 15:12       ` Leo Famulari
2017-07-14 16:34         ` Oleg Pykhalov
2017-07-17  9:46           ` bug#27673: " Arun Isaac

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://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87zic72ko9.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --cc=27673@debbugs.gnu.org \
    --cc=arunisaac@systemreboot.net \
    /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/guix.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).