From: Mark Wielaard <mark@klomp.org>
To: Anthony Balkissoon <abalkiss@redhat.com>
Cc: Casey Marshall <csm@gnu.org>, mauve-discuss@sources.redhat.com
Subject: Re: RFC: Jessie tests
Date: Thu, 27 Jul 2006 19:44:00 -0000 [thread overview]
Message-ID: <1154029430.2977.8.camel@dijkstra.wildebeest.org> (raw)
In-Reply-To: <1154024927.2457.86.camel@tony.toronto.redhat.com>
Hi Casey,
On Thu, 2006-07-27 at 14:28 -0400, Anthony Balkissoon wrote:
> On Wed, 2006-07-26 at 17:30 -0700, Casey Marshall wrote:
> > So, these tests will only compile and run right now against the ssl-
> > nio branch, and after the merge will work with the generics branch,
> > but not with trunk. Will either situation be unreasonably disruptive?
> > If not, I'll check these tests in this weekend.
> >
> I don't think this is a problem. They will show up as FAILs but that's
> about the worst that should happen. Doesn't bother me, but maybe
> someone else has some input.
As Tony says, the Harness just marks those tests as FAILs for now since
they don't compile. But I think that is fine.
Cheers,
Mark
prev parent reply other threads:[~2006-07-27 19:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-27 0:30 Casey Marshall
2006-07-27 18:28 ` Anthony Balkissoon
2006-07-27 19:44 ` Mark Wielaard [this message]
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=1154029430.2977.8.camel@dijkstra.wildebeest.org \
--to=mark@klomp.org \
--cc=abalkiss@redhat.com \
--cc=csm@gnu.org \
--cc=mauve-discuss@sources.redhat.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.
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).