Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
perl.perl6.internals
+ new post
About this group
Subscribe to this group
This is a Usenet group - learn more
benchmarks - testing and newfound failures
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   2 messages - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Justin DeVuyst  
View profile  
 More options Dec 13 2004, 3:04 am
Newsgroups: perl.perl6.internals
From: jus...@devuyst.com (Justin DeVuyst)
Date: Mon, 13 Dec 2004 03:04:46 -0500 (EST)
Local: Mon, Dec 13 2004 3:04 am
Subject: benchmarks - testing and newfound failures
Print | Individual message | Show original | Report this message | Find messages by this author

A few days ago I noticed that the vpm benchmark was failing.  Then
today, I saw that the majority of the OO benchmarks were failing.
I'd like to propose including testbench under fulltest so that the
benchmarks can be more readily tested.  Maybe that will help keep
the benchmarks from getting broken so easily.

I've included a patch that fixes the vpm bench.  Seems the recent
changes to split broke it.

I didn't work out the OO bench fixes yet.  Anyone else wanna take a
stab at it?  Its most likely ridiculously simple.  Actually, I have
a related question.  Since the current object isn't in P2 anymore
and "self" in PIR replaces it, what is the equivalent in pasm?  That
looks like what's breaking the OO benches right now.

Thanks,
       Justin DeVuyst

  vpm_imc.patch
1K Download

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
Leopold Toetsch  
View profile  
 More options Dec 13 2004, 4:59 am
Newsgroups: perl.perl6.internals
From: l...@toetsch.at (Leopold Toetsch)
Date: Mon, 13 Dec 2004 10:59:24 +0100
Local: Mon, Dec 13 2004 4:59 am
Subject: Re: benchmarks - testing and newfound failures
Print | Individual message | Show original | Report this message | Find messages by this author

Justin DeVuyst <jus...@devuyst.com> wrote:
> A few days ago I noticed that the vpm benchmark was failing.  Then
> today, I saw that the majority of the OO benchmarks were failing.

Yeah. Fixed.

> I'd like to propose including testbench under fulltest so that the
> benchmarks can be more readily tested.  Maybe that will help keep
> the benchmarks from getting broken so easily.

Yep. But first I've removed a bunch of benchmarks: hash-utf8 used
non-existent opcodes, b6* used python methods which aren't in core.

WRT including under fulltest: the benchmarks.t should patch the files so
that they don't run too long.

> I've included a patch that fixes the vpm bench.  Seems the recent
> changes to split broke it.

Thanks, applied
leo

 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google