feather any more, whee!) And I also thank
iblech++ (yes, iblech's alive!) for helping him through the whole
process.
The Synopses on feather will still go without smoke results, since
smoke results are always specific to a certain Perl 6 implementation
or a Pugs backend. We hope you will still like it. :)
Enjoy!
Agent
P.S. This mail has also been posted to the Pugs blog site:
http://pugs.blogs.com/pugs/2006/09/check_smoke_res.html
which contains some useful links.
On 9/18/06, Will Coleda <[EMAIL PROTECTED]> wrote:
On Sep 17, 2006, at 2:25 PM, Agent Zhang wrote:
> Our new smoke server now has some extra links named SYN in the left
> margin of the page, where one SYN link corresponds to one smoke
> report:
After much confusion, I found them on the *right*
On Sep 17, 2006, at 2:25 PM, Agent Zhang wrote:
Our new smoke server now has some extra links named SYN in the left
margin of the page, where one SYN link corresponds to one smoke
report:
After much confusion, I found them on the *right* hand side, and only
for certain smokes.
Regards.
-
ng smoke
result rendering feature in smartlinks.pl many weeks ago. At last but
not least, I really appreciate Christopher's work on the smoke
server/client mechanism to make this feature truly useful. (We don't
need auto-smoking on feather any more, whee!) And I also thank
iblech++ (yes, iblech&#x
Nick Glencross wrote:
A few new red splodges have appeared on the HP-UX smokes. In future
does it seem helpful if I investigate these?
I've just had a quick look at some of them now:
freeze_26/27: exposes a potential problem in the imcc optmiser which I
also see in valgrind on Linux. In try_al
A few new red splodges have appeared on the HP-UX smokes. In future
does it seem helpful if I investigate these?
I've just had a quick look at some of them now:
freeze_26/27: exposes a potential problem in the imcc optmiser which I
also see in valgrind on Linux. In try_allocate, mem_sys_allocate
