Message from discussion
synopses on smoke server
Newsgroups: perl.perl6.compiler
Path: g2news2.google.com!news1.google.com!news4.google.com!newsfeed.stanford.edu!nntp.perl.org
Return-Path: <ma...@MIT.EDU>
Mailing-List: contact perl6-compiler-h...@perl.org; run by ezmlm
Delivered-To: mailing list perl6-compi...@perl.org
Received: (qmail 20295 invoked from network); 5 Sep 2006 15:46:48 -0000
Received: from x1a.develooper.com (HELO x1.develooper.com) (216.52.237.111)
by lists.develooper.com with SMTP; 5 Sep 2006 15:46:48 -0000
Received: (qmail 10388 invoked by uid 225); 5 Sep 2006 15:46:47 -0000
Delivered-To: perl6-compi...@perl.org
Received: (qmail 10381 invoked by alias); 5 Sep 2006 15:46:47 -0000
X-Spam-Status: No, hits=-2.6 required=8.0
tests=BAYES_00,SPF_PASS
X-Spam-Check-By: la.mx.develooper.com
Received-SPF: pass (x1.develooper.com: domain of ma...@mit.edu designates 18.7.7.80 as permitted sender)
Received: from BISCAYNE-ONE-STATION.MIT.EDU (HELO biscayne-one-station.mit.edu) (18.7.7.80)
by la.mx.develooper.com (qpsmtpd/0.28) with ESMTP; Tue, 05 Sep 2006 08:46:26 -0700
Received: from outgoing.mit.edu (OUTGOING-AUTH.MIT.EDU [18.7.22.103])
by biscayne-one-station.mit.edu (8.13.6/8.9.2) with ESMTP id k85FkH9K011984
for <perl6-compi...@perl.org>; Tue, 5 Sep 2006 11:46:20 -0400 (EDT)
Received: from [220.58.112.30] (softbank220058112030.bbtec.net [220.58.112.30])
(authenticated bits=0)
(User authenticated as ma...@ATHENA.MIT.EDU)
by outgoing.mit.edu (8.13.6/8.12.4) with ESMTP id k85Fk19S016785
(version=TLSv1/SSLv3 cipher=RC4-SHA bits=128 verify=NOT)
for <perl6-compi...@perl.org>; Tue, 5 Sep 2006 11:46:05 -0400 (EDT)
Mime-Version: 1.0 (Apple Message framework v752.2)
Content-Transfer-Encoding: quoted-printable
Message-ID: <72481F59-365C-47D9-B227-393447C1B0D0@mit.edu>
Content-Type: text/plain; charset=ISO-8859-1; delsp=yes; format=flowed
To: perl6-compi...@perl.org
Subject: synopses on smoke server
Date: Tue, 5 Sep 2006 11:47:12 -0400
X-Mailer: Apple Mail (2.752.2)
X-Spam-Score: 1.217
X-Spam-Level: * (1.217)
X-Scanned-By: MIMEDefang 2.42
X-Old-Spam-Flag: NO
Approved: n...@nntp.perl.org
From: ma...@MIT.EDU (Christopher D. Malon)
Agentz++ writes, in a Pugs blog comment:
> if someone can offer regular smoke results (i.e. the tests.yml =20
> generated by `make smoke'), we can render the Synopses on feather =20
> with smoke results as well
The obvious way to get this to happen, for all runtimes, is to =20
integrate the
synopsis-with-smoke production with the existing smoke server =20
infrastructure.
I've started hacking this in, but have some concerns.
A few are mainly directed to iblech++.
1. Multi-versioning the tests: The inlined tests need to match
the revision at which the smoke was produced. Is it okay to have
the smoke server check out the relevant revision of the pugs/t directory
each time a smoke of a new revision is submitted, or is that too =20
expensive?
2. Should the synopses just be provided by a third "=BB" column on
the existing smoke.pugscode.org index page, or should the
synopses-with-smoke have a dedicated index page organized
somewhat differently?
3. What is the full path to smartlinks.pl on the smoke server?
4. Is the smoke server getting refreshed copies of the
synopses somewhere already?
5. Will a commit that changes smokeserv-server.pl be
picked up by the smoke server right away?
I might down the whole smoke system with my commit.
Anyone willing to debug with me when I do?
In summary, the basic pattern would be:
(a) smokeserv-client sends both .html and .yml of smoke
(b) If smokeserv-server gets .yml, it checks out the t/ directory for =20=
that revision, and
(c) smokeserv-server runs smartlinks.pl on the .yml with that t/ =20
directory and indexes it.
Christopher
|
