From: Martyn Jago <firstname.lastname@example.org> To: email@example.com Subject: Re: [babel] BUG in :session Date: Sun, 25 Sep 2011 09:31:39 +0100 [thread overview] Message-ID: <firstname.lastname@example.org> (raw) In-Reply-To: <email@example.com> Hi Eric Eric Schulte <firstname.lastname@example.org> writes: > Martyn Jago <email@example.com> writes: > >> Hi Eric >> >> Eric Schulte <firstname.lastname@example.org> writes: >> >>> Martyn Jago <email@example.com> writes: >>> >>>> Hi Eric >>>> >>>> Eric Schulte <firstname.lastname@example.org> writes: >>>> >>>>> Hi Martyn, >>>>> >>>>> I've just pushed up what will hopefully be a more general solution. >>>>> Basically, language-specific test files can now signal errors if they >>>>> have unmet dependencies. These are then intercepted by `org-test-load' >>>>> and the file is not added to the test suite. Hopefully this will allow >>>>> language-specific tests to be written without breaking the config-less >>>>> test suite. >>>>> >>>>> See the top of test-ob-R.el for an example usage. >>>>> >>>>> Cheers -- Eric >>>> >>>> Unfortunately this is still broken for me. Given the exe exists but the >>>> feature doesn't (ie no personal config), the following line causes the >>>> error `peculiar error' ! >>>> >>>> (signal 'org-test-lib-not-found "ess")) >>>> >>> >>> Oh, >>> >>> I forgot to update the types of errors that I am catching after adding a >>> new error type for missing libraries (e.g., ess). This should now be >>> fixed. >>> >> >> There still seems to be a problem with test-ob-R - same error "peculiar >> error". >> > > OK, I see this error as well. I've switched from using errors to signal > a missing dependency to using catch/throw blocks. This seems to > actually work, hopefully the test suite should now run w/o error. > This now works great for me. >> >>> >>> Is there a way to see the output of the test run, all I can find is the >>> command which is executed. >> >> Yes - just click on the org-mode_Emacs_24 (title) link and then on the >> build log link. There isn't much of a log on the failing tests since >> the entire test run is broken by the signal. >> >> You can checkout the build log for my-org-mode-dev to see what you >> should get. >> > > Great, doing this I can see that everything is now running successfully > http://martynjago.com:3333/builds/org-mode_Emacs_24/4446e50/build.log > > Very nice system, I wonder if we could run something like this on the > Org-mode server. It should be fairly easy to set up a similar system on the Org-mode server, and very useful I would have thought. I agree it is a very useful system and have used it several times on other projects. Best, Martyn
next prev parent reply other threads:[~2011-09-25 8:31 UTC|newest] Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-09-21 11:19 Rainer M Krug 2011-09-21 12:57 ` Eric Schulte 2011-09-21 16:56 ` Martyn Jago 2011-09-21 18:54 ` Sebastien Vauban 2011-09-21 19:32 ` Eric Schulte 2011-09-21 19:32 ` Eric Schulte 2011-09-21 20:09 ` Sebastien Vauban 2011-09-21 21:20 ` Martyn Jago 2011-09-22 2:23 ` Eric Schulte 2011-09-23 11:36 ` Martyn Jago 2011-09-23 15:59 ` Eric Schulte 2011-09-23 16:12 ` Martyn Jago 2011-09-23 22:16 ` Sebastien Vauban 2011-09-24 22:13 ` Eric Schulte 2011-09-25 8:37 ` Martyn Jago 2011-09-26 7:54 ` Sebastien Vauban 2011-09-26 12:23 ` Eric Schulte 2011-09-26 13:59 ` Sebastien Vauban 2011-09-24 22:12 ` Eric Schulte 2011-09-25 8:31 ` Martyn Jago [this message] 2011-09-21 17:09 ` Rainer M Krug
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.orgmode.org/ * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --email@example.com \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: [babel] BUG in :session' \ /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
Code repositories for project(s) associated with this inbox: https://git.savannah.gnu.org/cgit/emacs/org-mode.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).