As it is not easy to get the diff from this email, here it goes really
in attach.
I know the text is not the best, but it is something to start with.
Parrot Assembler via RT wrote:
Greetings,
This message has been automatically generated in response to the
creation of a parrotbug regarding:
"Patch for tests.pod talking about testing parrot"
There is no need to reply to this message right now. Your ticket has been
assigned an ID of [perl #37887].
Please include the string:
[perl #37887]
In the subject line of all future correspondence about this issue. To do so,
you may reply to this message.
Thank you,
parrotbug
https://rt.perl.org/rt3/Ticket/Display.html?id=37887
-------------------------------------------------------------------------
Received: (qmail 20403 invoked by alias); 11 Dec 2005 19:24:20 -0000
Received: (qmail 20399 invoked from network); 11 Dec 2005 19:24:19 -0000
Received: from localhost (HELO la.mx.develooper.com) (127.0.0.1) by localhost
with SMTP; 11 Dec 2005 19:24:19 -0000
Received: (qmail 20396 invoked by alias); 11 Dec 2005 19:24:19 -0000
Received: from la.mx.develooper.com (HELO x1.develooper.com) (63.251.223.176)
by la.mx.develooper.com (qpsmtpd/0.28) with SMTP; Sun, 11 Dec 2005 11:24:12
-0800
Received: (qmail 20336 invoked by uid 225); 11 Dec 2005 19:24:09 -0000
Received: (qmail 20331 invoked by alias); 11 Dec 2005 19:24:08 -0000
Received: from eremita.di.uminho.pt (HELO eremita.di.uminho.pt)
(193.136.19.131) by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Sun, 11 Dec
2005 11:24:00 -0800
Received: by eremita.di.uminho.pt (Postfix, from userid 1000) id 6748A157054;
Sun, 11 Dec 2005 19:25:19 +0000 (WET)
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Delivered-To: [EMAIL PROTECTED]
Subject: Patch for tests.pod talking about testing parrot
X-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
Return-Path: <[EMAIL PROTECTED]>
X-Spam-Check-BY: la.mx.develooper.com
X-Old-Spam-Status: No, hits=-2.6 required=8.0 tests=BAYES_00
Date: Sun, 11 Dec 2005 19:25:19 +0000 (WET)
Received-SPF: neutral (x1.develooper.com: local policy)
Received-SPF: pass (x1.develooper.com: local policy)
X-Old-Spam-Check-BY: la.mx.develooper.com
Message-ID: <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
From: [EMAIL PROTECTED] (Alberto Manuel Brandao Simoes)
X-RT-Original-Encoding: ascii
content-type: text/plain; charset="utf-8"
---
osname= linux
osvers= 2.4.26
arch= i486-linux
cc= cc
---
Flags:
category=docs
severity=none
ack=no
---
Index: docs/tests.pod
===================================================================
--- docs/tests.pod (revision 10449)
+++ docs/tests.pod (working copy)
@@ -5,12 +5,34 @@
docs/tests.pod - Testing Parrot
-=head1 A basic guide to writing tests for Parrot
+=head1 A basic guide to writing and running tests for Parrot
This is quick and dirty pointer to how tests for Parrot should be written. The
testing system is liable to change in the future, but tests written following
the guidelines below should be easy to port into a new test suite.
+=head1 How to test parrot
+
+The easy way to test parrot is running C<make test>. If you have
+updated your code recently and tests began failing, go for a C<make
+realclean> and recompile parrot before complaining.
+
+If you architecture suport JIT, you can test parrot JIT engine using
+C<make testj>. It works just like C<make test>, but uses the JIT
+engine when possible.
+
+=head2 Submitting smoke test results
+
+Parrot has a status page with smoke test results
+L<http://smoke.parrotcode.org/smoke.html>. You can supply new tests
+results just running C<make smoke>. It will run the same tests as
+C<make test> would, but creating a HTML table with the test
+results. At the end, it will try to upload the test results to the
+smoke server.
+
+It is also possible to run a smoke test on JIT. For that, try running
+C<env PARROT_ARGS=-j make smoke>.
+
=head1 How to write a test
New tests should be added to F<*.t> files. These test files can be found in the
---
Summary of my parrot 0.4.0 (r10446) configuration:
configdate='Sun Dec 11 17:43:04 2005'
Platform:
osname=linux, archname=i486-linux
jitcapable=1, jitarchname=i386-linux,
jitosname=LINUX, jitcpuarch=i386
execcapable=1
perl=/usr/bin/perl5.8.5
Compiler:
cc='cc', ccflags=' -pipe -I/usr/local/include -D_LARGEFILE_SOURCE
-D_FILE_OFFSET_BITS=64 -D_GNU_SOURCE',
Linker and Libraries:
ld='cc', ldflags=' -L/usr/local/lib',
cc_ldflags='',
libs='-lnsl -ldl -lm -lcrypt -lutil -lpthread -lrt -lgmp'
Dynamic Linking:
share_ext='.so', ld_share_flags='-shared -L/usr/local/lib -fPIC',
load_ext='.so', ld_load_flags='-shared -L/usr/local/lib -fPIC'
Types:
iv=long, intvalsize=4, intsize=4, opcode_t=long, opcode_t_size=4,
ptrsize=4, ptr_alignment=1 byteorder=1234,
nv=double, numvalsize=8, doublesize=8
---
Environment:
HOME LANG LANGUAGE LC_ALL LC_COLLATE LD_LIBRARY_PATH
LOGDIR PATH PERL5_CPANPLUS_CONFIG SHELL
--
Alberto Simões - Departamento de Informática - Universidade do Minho
Campus de Gualtar - 4710-057 Braga - Portugal
Index: docs/tests.pod
===================================================================
--- docs/tests.pod (revision 10449)
+++ docs/tests.pod (working copy)
@@ -5,12 +5,34 @@
docs/tests.pod - Testing Parrot
-=head1 A basic guide to writing tests for Parrot
+=head1 A basic guide to writing and running tests for Parrot
This is quick and dirty pointer to how tests for Parrot should be written. The
testing system is liable to change in the future, but tests written following
the guidelines below should be easy to port into a new test suite.
+=head1 How to test parrot
+
+The easy way to test parrot is running C<make test>. If you have
+updated your code recently and tests began failing, go for a C<make
+realclean> and recompile parrot before complaining.
+
+If you architecture suport JIT, you can test parrot JIT engine using
+C<make testj>. It works just like C<make test>, but uses the JIT
+engine when possible.
+
+=head2 Submitting smoke test results
+
+Parrot has a status page with smoke test results
+L<http://smoke.parrotcode.org/smoke.html>. You can supply new tests
+results just running C<make smoke>. It will run the same tests as
+C<make test> would, but creating a HTML table with the test
+results. At the end, it will try to upload the test results to the
+smoke server.
+
+It is also possible to run a smoke test on JIT. For that, try running
+C<env PARROT_ARGS=-j make smoke>.
+
=head1 How to write a test
New tests should be added to F<*.t> files. These test files can be found in the
