All of lore.kernel.org
 help / color / mirror / Atom feed
From: Don Slutz <Don.Slutz@SierraAtlantic.com>
To: Hannu Koivisto <azure@iki.fi>
Cc: git@vger.kernel.org
Subject: Re: Tests in Cygwin
Date: Wed, 06 May 2009 15:34:36 -0400	[thread overview]
Message-ID: <4A01E64C.7050703@SierraAtlantic.com> (raw)
In-Reply-To: <83prfbhasp.fsf@kalahari.s2.org>

A lot of these failures are do to running as root (member of 
Administrators).  Using v1.6.3-rc4 (503f464...) I get:

make -i test
...
make aggregate-results
make[3]: Entering directory `/home/udslutz/BinMode/git/t'
'/bin/sh' ./aggregate-results.sh test-results/t*-*
fixed   3
success 4211
failed  5
broken  5
total   4272
make[3]: Leaving directory `/home/udslutz/BinMode/git/t'
...

  -Don Slutz



-------- Original Message --------
Subject: Tests in Cygwin
From: Hannu Koivisto <azure@iki.fi>
To: git@vger.kernel.org
Date: 4/17/2009 5:47 AM
> Greetings,
>
> I upgraded to the latest git.git as of yesterday
> (f800b65bea1504299747e7be03ee279508a74e1f) in Cygwin to see if it
> still has the rebase and bogus modified files problem(s) (reported
> earlier http://osdir.com/ml/git/2009-04/msg00619.html).  It does;
> I'll try to bisect it if I manage to make the test case automatic.
>
> I also thought I'd run all the tests just for the heck of it.  The
> result is about 240 failures which are available here (lines
> indicating passed tests removed):
>
> http://www.iki.fi/azure/tmp/git-test-results-cygwin-f800b65bea1504299747e7be03ee279508a74e1f.txt
>
> I wonder, since there seems to be some sort of mechanism to mark
> failures "known" (at least I got a couple of "still broken ..."
> lines), are all these unexpected, new problems, or is there perhaps
> some separate list of known failures on Cygwin?
>
>   



__________________________________________________________________________________________________________________
DISCLAIMER:"The information contained in this message and the attachments (if any) may be privileged and confidential and protected from disclosure. You are hereby notified that any unauthorized use, dissemination, distribution or copying of this communication, review, retransmission, or taking of any action based upon this information, by persons or entities other than the intended recipient, is strictly prohibited. If you are not the intended recipient or an employee or agent responsible for delivering this message, and have received this communication in error, please notify us immediately by replying to the message and kindly delete the original message, attachments, if any, and all its copies from your computer system. Thank you for your cooperation." 
________________________________________________________________________________________________________________

  reply	other threads:[~2009-05-06 19:34 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-17  9:47 Tests in Cygwin Hannu Koivisto
2009-05-06 19:34 ` Don Slutz [this message]
2009-05-06 20:42   ` Junio C Hamano
2009-05-07  7:13     ` Johannes Sixt
2009-05-07 15:47       ` Don Slutz
2009-05-07 18:29         ` Don Slutz
2009-05-08  0:02         ` Junio C Hamano
2009-05-08  6:03           ` Johannes Sixt
2009-05-08  2:00         ` Jeff King
2009-05-08  6:02           ` Johannes Sixt
2009-05-08  6:41             ` Junio C Hamano
2009-05-08  9:28               ` Alex Riesen
2009-05-08 14:19                 ` Don Slutz
2009-05-08 14:28                   ` Johannes Sixt
2009-05-08 16:45                   ` Alex Riesen
2009-05-08  0:00       ` Junio C Hamano

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=4A01E64C.7050703@SierraAtlantic.com \
    --to=don.slutz@sierraatlantic.com \
    --cc=azure@iki.fi \
    --cc=git@vger.kernel.org \
    /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 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.