path: root/fb/984b5b1b576d85f59a80c90ee5b9887737a642

Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <arklan.uthoslin@gmail.com>) id 1TMMvT-0000GT-Do
	for bitcoin-development@lists.sourceforge.net;
	Thu, 11 Oct 2012 17:52:03 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.47 as permitted sender)
	client-ip=209.85.212.47; envelope-from=arklan.uthoslin@gmail.com;
	helo=mail-vb0-f47.google.com; 
Received: from mail-vb0-f47.google.com ([209.85.212.47])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1TMMvR-0006p2-Pa
	for bitcoin-development@lists.sourceforge.net;
	Thu, 11 Oct 2012 17:52:03 +0000
Received: by mail-vb0-f47.google.com with SMTP id ez10so2274896vbb.34
	for <bitcoin-development@lists.sourceforge.net>;
	Thu, 11 Oct 2012 10:51:56 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.52.139.136 with SMTP id qy8mr786763vdb.39.1349977916204; Thu,
	11 Oct 2012 10:51:56 -0700 (PDT)
Received: by 10.220.137.139 with HTTP; Thu, 11 Oct 2012 10:51:56 -0700 (PDT)
In-Reply-To: <507705B1.2050404@mistfpga.net>
References: <CABsx9T2Y+Ku1DcvWGS+c3p+qRFKbM8O=-CuL=1kC0TZdK1Sz5A@mail.gmail.com>
	<507705B1.2050404@mistfpga.net>
Date: Thu, 11 Oct 2012 11:51:56 -0600
Message-ID: <CAGg41SWrgCKjAZH3LCGkt5juDg97wNR=VogzD59snF9yPHw2sQ@mail.gmail.com>
From: Arklan Uth Oslin <arklan.uthoslin@gmail.com>
To: steve <steve@mistfpga.net>
Content-Type: multipart/alternative; boundary=bcaec51b9d0d26665d04cbcc3ac1
X-Spam-Score: -0.6 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
	See http://spamassassin.org/tag/ for more details.
	-1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for
	sender-domain
	0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider
	(arklan.uthoslin[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	-0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from
	author's domain
	0.1 DKIM_SIGNED            Message has a DKIM or DK signature,
	not necessarily valid
	-0.1 DKIM_VALID Message has at least one valid DKIM or DK signature
X-Headers-End: 1TMMvR-0006p2-Pa
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 0.7.1 release candidate 1 ready for
	testing
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Thu, 11 Oct 2012 17:52:03 -0000

--bcaec51b9d0d26665d04cbcc3ac1
Content-Type: text/plain; charset=ISO-8859-1

i'll second the bitcoin test list.

Arklan

----------
As long as there is light, the darkness holds no fear. And yet, even in the
deepest black, there is life. - Arklan Uth Oslin

I want to leave this world the same way I came into it: backwards and on
fire. - Arklan Uth Oslin



On Thu, Oct 11, 2012 at 11:45 AM, steve <steve@mistfpga.net> wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
>
> Hi,
>
> On 11/10/2012 16:46, Gavin Andresen wrote:
> > Any progress on a release candidate QA sanity testing plan?
>
> essentially yes - in all seriousness, I have come around to your way
> of thinking, it is not worth arguing about. we end up in the same place.
>
> :) nothing is final though. I will be opening it up to Arklan in a bit
> (I have a pool match tonight so after that depending on how drunk i
> get.) and to another couple of people who have emailed me off list who
> would like to be involved in testing.
>
> I have not created any new tests for the new stuff.  this is still the
> noddy stuff.
>
> It covers everything that needs to be covered for a newbe or someone
> upgrading clients.
>
> and it is in many formats the moment (from wiki to test runner) none
> particularly useful (about to import into mantis, just fiddling with
> the fields so it does testcases)
>
> I have been trying to separate the tests into what can be automated,
> recorded and checked by watching the video and have sanity checks
> along the way (published sha and sha256 of the binaries match) -
> (obviously the test is flagged to be run manually if there is any doubt)
>
> I did take myself outside and had a little sit down and talk to
> myself.  Lets not run before we can walk. I will still keep the grand
> ideas, but they are on the back burner. (I got called a blue skies
> thinker today, wtf is one of them? I said smiled and said thanks)
>
> the main things we make sure we get tested right are all the GAT tests
> in bettermeans.They are more protocol based and should be run against
> all releases.  Lets nail that process, peer review it, retest it, then
> use that as a basis for The Process. I will temper my zealousness. I
> realise that I can come across as bullish or even aggressive in my
> emails.  I never mean too.(unless I say I am. That is not an excuse
> for my poor english language skills.)
>
> But I still think that the people running the tests should have the
> greatest say in what software is used. So once you have access to the
> server and the cases feel free to install your favourite software and
> see what other people think.
>
> but we have a vague structure and workflow so it will be interesting
> to see how it works out.
>
> the git integration will be trivial.
>
> please email me if you would like access.  I am off out in 15 mins but
> I promise to have all access sorted by tomorrow.  I am only using 3
> vps to show example testing and test platforms.  I would like it if we
> could get a technet license with the donations so far, I use mine (and
> my msdn) for work.
>
> also check out bettermeans for the formats that I will be using.
>
> bollocks. bollocks. bollocks
>
> https://secure.bettermeans.com/projects/4180
>
> bye bye bettermeans. how we never knew ye.
>
> Gavin, can we get a bitcoin-test mailing list please.  it would be
> used for discussion of testing, tools, ideas, chatter, etc.  it would
> not be a place reporting bugs... This list seems very focused and I
> always feel like I am disrupting things with my emails about test.  I
> dont mind admining the list. I would rather be vocal and inclusive, I
> dont think the dev list is the place for that.
>
> >
> >
> > Bitcoin version 0.7.1 release candidate 1 is now available from:
> >
> http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.7.1/test/
> >
> >  This is a bug-fix minor release.
> >
> > New features ------------
> >
> > * Added a boolean argument to the RPC 'stop' command, if true sets
> > -detachdb to create standalone database .dat files before shutting
> > down.
> >
> > * -salvagewallet command-line option, which moves any existing
> > wallet.dat to wallet.{timestamp}.dat and then attempts to salvage
> > public/private keys and master encryption keys (if the wallet is
> > encrypted) into a new wallet.dat. This should only be used if your
> > wallet becomes corrupted, and is not intended to replace regular
> > wallet backups.
> >
> > * Import $DataDir/bootstrap.dat automatically, if it exists.
> >
> > Dependency changes ------------------
> >
> > * Qt 4.8.2 for Windows builds
> >
> > * openssl 1.0.1c
> >
> > Bug fixes ---------
> >
> > * When running -testnet, use RPC port 18332 by default.
> >
> > * Better detection and handling of corrupt wallet.dat and
> > blkindex.dat files. Previous versions would crash with a
> > DB_RUNRECOVERY exception, this version detects most problems and
> > tells you how to recover if it cannot recover itself.
> >
> > * Fixed an uninitialized variable bug that could cause transactions
> > to be reported out of order.
> >
> > * Fixed a bug that could cause occasional crashes on exit.
> >
> > * Warn the user that they need to create fresh wallet backups after
> > they encrypt their wallet.
> >
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v2.0.17 (MingW32)
> Comment: Using GnuPG with Mozilla - http://www.enigmail.net/
>
> iQEcBAEBAgAGBQJQdwWxAAoJEFvEB9dQFvtQiuMIAJpdu23biq56apMO/KfqmSB0
> kQPflDD2XMxTknfqzRs35/EFgL0mJ/cYfY3qTW9JOWL/cit4ieq2EA4P3uQeFFDC
> NCxIuDxOzOIaZ+SzRZENXdpVWKRNP1RgUCANm3YfrJBlavr9a/om36nP1IK0W4MB
> QcPXrrZvipt1xhx1G/V6NvYbZA3lTAJBFzuz2oRJNwlYoExJFw8EHBypa67BUNOj
> NDg1Wu5Ppyq7dZbgfhw4HxIIvgwn/vaSm/tX6HJxyKN7HUJIbIyQrSbPGUvWCsBW
> KI6e88DPdG0x0ltqVXja+51n3F9G4H/zTIbB0GyiRDn0GcGwi/GolF5PAgz0tR8=
> =zniH
> -----END PGP SIGNATURE-----
>
>
> ------------------------------------------------------------------------------
> Don't let slow site performance ruin your business. Deploy New Relic APM
> Deploy New Relic app performance management and know exactly
> what is happening inside your Ruby, Python, PHP, Java, and .NET app
> Try New Relic at no cost today and get our sweet Data Nerd shirt too!
> http://p.sf.net/sfu/newrelic-dev2dev
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
>

--bcaec51b9d0d26665d04cbcc3ac1
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

i&#39;ll second the bitcoin test list.<br clear=3D"all"><div>=A0</div>
<div>Arklan<br><br>----------<br>
<div>As long as there is light, the darkness holds no fear. And yet, even i=
n the deepest black, there is life. - Arklan Uth Oslin</div></div>
<div>=A0</div>
<div>I want to leave this world the same way I came into it: backwards and =
on fire. - Arklan Uth Oslin</div><br>
<br><br><div class=3D"gmail_quote">On Thu, Oct 11, 2012 at 11:45 AM, steve =
<span dir=3D"ltr">&lt;<a href=3D"mailto:steve@mistfpga.net" target=3D"_blan=
k">steve@mistfpga.net</a>&gt;</span> wrote:<br><blockquote class=3D"gmail_q=
uote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1e=
x">
-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
<br>
Hi,<br>
<div class=3D"im"><br>
On 11/10/2012 16:46, Gavin Andresen wrote:<br>
&gt; Any progress on a release candidate QA sanity testing plan?<br>
<br>
</div>essentially yes - in all seriousness, I have come around to your way<=
br>
of thinking, it is not worth arguing about. we end up in the same place.<br=
>
<br>
:) nothing is final though. I will be opening it up to Arklan in a bit<br>
(I have a pool match tonight so after that depending on how drunk i<br>
get.) and to another couple of people who have emailed me off list who<br>
would like to be involved in testing.<br>
<br>
I have not created any new tests for the new stuff. =A0this is still the<br=
>
noddy stuff.<br>
<br>
It covers everything that needs to be covered for a newbe or someone<br>
upgrading clients.<br>
<br>
and it is in many formats the moment (from wiki to test runner) none<br>
particularly useful (about to import into mantis, just fiddling with<br>
the fields so it does testcases)<br>
<br>
I have been trying to separate the tests into what can be automated,<br>
recorded and checked by watching the video and have sanity checks<br>
along the way (published sha and sha256 of the binaries match) -<br>
(obviously the test is flagged to be run manually if there is any doubt)<br=
>
<br>
I did take myself outside and had a little sit down and talk to<br>
myself. =A0Lets not run before we can walk. I will still keep the grand<br>
ideas, but they are on the back burner. (I got called a blue skies<br>
thinker today, wtf is one of them? I said smiled and said thanks)<br>
<br>
the main things we make sure we get tested right are all the GAT tests<br>
in bettermeans.They are more protocol based and should be run against<br>
all releases. =A0Lets nail that process, peer review it, retest it, then<br=
>
use that as a basis for The Process. I will temper my zealousness. I<br>
realise that I can come across as bullish or even aggressive in my<br>
emails. =A0I never mean too.(unless I say I am. That is not an excuse<br>
for my poor english language skills.)<br>
<br>
But I still think that the people running the tests should have the<br>
greatest say in what software is used. So once you have access to the<br>
server and the cases feel free to install your favourite software and<br>
see what other people think.<br>
<br>
but we have a vague structure and workflow so it will be interesting<br>
to see how it works out.<br>
<br>
the git integration will be trivial.<br>
<br>
please email me if you would like access. =A0I am off out in 15 mins but<br=
>
I promise to have all access sorted by tomorrow. =A0I am only using 3<br>
vps to show example testing and test platforms. =A0I would like it if we<br=
>
could get a technet license with the donations so far, I use mine (and<br>
my msdn) for work.<br>
<br>
also check out bettermeans for the formats that I will be using.<br>
<br>
bollocks. bollocks. bollocks<br>
<br>
<a href=3D"https://secure.bettermeans.com/projects/4180" target=3D"_blank">=
https://secure.bettermeans.com/projects/4180</a><br>
<br>
bye bye bettermeans. how we never knew ye.<br>
<br>
Gavin, can we get a bitcoin-test mailing list please. =A0it would be<br>
used for discussion of testing, tools, ideas, chatter, etc. =A0it would<br>
not be a place reporting bugs... This list seems very focused and I<br>
always feel like I am disrupting things with my emails about test. =A0I<br>
dont mind admining the list. I would rather be vocal and inclusive, I<br>
dont think the dev list is the place for that.<br>
<div><div class=3D"h5"><br>
&gt;<br>
&gt;<br>
&gt; Bitcoin version 0.7.1 release candidate 1 is now available from:<br>
&gt; <a href=3D"http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitco=
in-0.7.1/test/" target=3D"_blank">http://sourceforge.net/projects/bitcoin/f=
iles/Bitcoin/bitcoin-0.7.1/test/</a><br>
&gt;<br>
&gt; =A0This is a bug-fix minor release.<br>
&gt;<br>
&gt; New features ------------<br>
&gt;<br>
&gt; * Added a boolean argument to the RPC &#39;stop&#39; command, if true =
sets<br>
&gt; -detachdb to create standalone database .dat files before shutting<br>
&gt; down.<br>
&gt;<br>
&gt; * -salvagewallet command-line option, which moves any existing<br>
&gt; wallet.dat to wallet.{timestamp}.dat and then attempts to salvage<br>
&gt; public/private keys and master encryption keys (if the wallet is<br>
&gt; encrypted) into a new wallet.dat. This should only be used if your<br>
&gt; wallet becomes corrupted, and is not intended to replace regular<br>
&gt; wallet backups.<br>
&gt;<br>
&gt; * Import $DataDir/bootstrap.dat automatically, if it exists.<br>
&gt;<br>
&gt; Dependency changes ------------------<br>
&gt;<br>
&gt; * Qt 4.8.2 for Windows builds<br>
&gt;<br>
&gt; * openssl 1.0.1c<br>
&gt;<br>
&gt; Bug fixes ---------<br>
&gt;<br>
&gt; * When running -testnet, use RPC port 18332 by default.<br>
&gt;<br>
&gt; * Better detection and handling of corrupt wallet.dat and<br>
&gt; blkindex.dat files. Previous versions would crash with a<br>
&gt; DB_RUNRECOVERY exception, this version detects most problems and<br>
&gt; tells you how to recover if it cannot recover itself.<br>
&gt;<br>
&gt; * Fixed an uninitialized variable bug that could cause transactions<br=
>
&gt; to be reported out of order.<br>
&gt;<br>
&gt; * Fixed a bug that could cause occasional crashes on exit.<br>
&gt;<br>
&gt; * Warn the user that they need to create fresh wallet backups after<br=
>
&gt; they encrypt their wallet.<br>
&gt;<br>
&gt;<br>
<br>
</div></div>-----BEGIN PGP SIGNATURE-----<br>
Version: GnuPG v2.0.17 (MingW32)<br>
Comment: Using GnuPG with Mozilla - <a href=3D"http://www.enigmail.net/" ta=
rget=3D"_blank">http://www.enigmail.net/</a><br>
<br>
iQEcBAEBAgAGBQJQdwWxAAoJEFvEB9dQFvtQiuMIAJpdu23biq56apMO/KfqmSB0<br>
kQPflDD2XMxTknfqzRs35/EFgL0mJ/cYfY3qTW9JOWL/cit4ieq2EA4P3uQeFFDC<br>
NCxIuDxOzOIaZ+SzRZENXdpVWKRNP1RgUCANm3YfrJBlavr9a/om36nP1IK0W4MB<br>
QcPXrrZvipt1xhx1G/V6NvYbZA3lTAJBFzuz2oRJNwlYoExJFw8EHBypa67BUNOj<br>
NDg1Wu5Ppyq7dZbgfhw4HxIIvgwn/vaSm/tX6HJxyKN7HUJIbIyQrSbPGUvWCsBW<br>
KI6e88DPdG0x0ltqVXja+51n3F9G4H/zTIbB0GyiRDn0GcGwi/GolF5PAgz0tR8=3D<br>
=3DzniH<br>
-----END PGP SIGNATURE-----<br>
<div class=3D"HOEnZb"><div class=3D"h5"><br>
---------------------------------------------------------------------------=
---<br>
Don&#39;t let slow site performance ruin your business. Deploy New Relic AP=
M<br>
Deploy New Relic app performance management and know exactly<br>
what is happening inside your Ruby, Python, PHP, Java, and .NET app<br>
Try New Relic at no cost today and get our sweet Data Nerd shirt too!<br>
<a href=3D"http://p.sf.net/sfu/newrelic-dev2dev" target=3D"_blank">http://p=
.sf.net/sfu/newrelic-dev2dev</a><br>
_______________________________________________<br>
Bitcoin-development mailing list<br>
<a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitcoin-develo=
pment@lists.sourceforge.net</a><br>
<a href=3D"https://lists.sourceforge.net/lists/listinfo/bitcoin-development=
" target=3D"_blank">https://lists.sourceforge.net/lists/listinfo/bitcoin-de=
velopment</a><br>
</div></div></blockquote></div><br>

--bcaec51b9d0d26665d04cbcc3ac1--