Priorities for this week: Plan our Testing Infrastructure (choose lead person), Contact all GSoC students | Post closed tickets in your report. | Note: This channel is for our Tuesday status meetings (at 20:30 UTC); you probably want #parrot instead. | irclog: irclog.perlgeek.de/
Set by moderator on 10 May 2011.
01:33 lucian_ left 01:36 whiteknight left 05:39 dafrito left 08:28 contingencyplan left 12:10 whiteknight joined 12:16 bluescreen joined 12:20 bluescreen left 12:29 lucian joined 12:35 bluescreen joined 13:21 lucian left 13:35 contingencyplan joined 14:10 PacoLinux left 14:29 bluescreen left 14:43 bluescreen joined 15:03 spinclad left 15:59 particle left, particle joined 16:17 bluescreen left, bluescreen joined 16:18 particle left 16:22 lucian joined 16:27 particle joined 16:38 particle left 16:49 darbelo joined 17:07 particle1 joined 17:13 particle1 is now known as particle 17:44 darbelo left
tcurtis Reporting early so I can nap until #ps. 17:52
Did:
* Gave a lightning talk about my project at the Chicago GSoC meetup. 17:53
* Was surprised by how many people had heard of Parrot.
* Little else.
Will do:
* Read papers. 17:54
* Blog.
* Talk to darbelo again.
* Sketch LALR grammar object representation.
Blockers:
* ICPC tryouts 17:55
EOR
whiteknight WHAT I DID: 18:21
* Tested like a madman to help ensure a good release. gerd++ on another smooth one.
* Worked on the NCI issues with cotto++, plobsing++ and pmichaud++.
* Attended PDS (kid51++ and others for setting that up)
* Expanded, Cleaned up, documented, and tested the Rosella Memoize library. It's now "stable".
WHAT I WILL DO:
* See if I can break ground on some new profiling tools, or at least put out some design ideas
* More work on Rosella, trying to get several libraries improved in various ways
EOR
pmichaud What I did this past week: 18:27
- more benchmarks of Rakudo and Parrot
- built a simple sub-level profiler for Rakudo
- patched rakudo to get ~15% speed improvements
- helped restore NCI functionality for zavolaj and others
- created NCI::Utils::ncifunc as a replacement wrapper for dlfunc
- drafted a "how Parrot is doing" message for PDS
- attended PDS
- drafted a new relationship manager policy for Parrot/Rakudo
Rakudo-specific improvements:
- added infix:<gcd> and infix:<lcm> operators
- discussed changes to .perl method
- added "config.status" to Configure.pl
- fixed NaN relational comparisons
- fixed bugs in --makefile-timing flag
- refactored Mu.item to be much faster
What I plan to do this next week: 18:28
- more improvements to rakbench and profiling tools
- more Rakudo performance fixes
- create an interim Star release (likely but not definite yet)
- reviews of reports, nom, nqp
EOR
18:38 darbelo joined 18:50 darbelo left 19:04 darbelo joined 19:11 NotFound joined
NotFound What I did: 19:22
-parrot
* Minor fixes
* Started using the gcc compile farm for testing,
fixed the build in sparc/OpenBSD while on it.
-winxed
* Fixed some problems with operand types in some operators, 19:23
diagnosing more errors.
* Added more scope searching abilities, avoiding the need for
using and using static declarations.
* Improver 'using' statement both at function and a namespace level.
* Added 'using namespace' statement.
What I will do:
* Use the compiler farm for testing more platforms.
* More improvements to winxed scope search.
EOR
19:34 ShaneC joined 19:36 darbelo left, darbelo joined, particle left
mikehh What I did since my last report: 19:37
* building and testing parrot on amd64/i386, with gcc/g++
* some fixes
* building and testing rakudo and winxed against latest parrot
What I intend to do in the next week:
* testing and fixing
* start going through "skipped" tests and see which now pass and which can be "TODO"ed
* work to eliminate warnings in the build
.eor
19:48 particle joined 19:54 darbelo left, kid51 joined 19:55 particle left 20:01 particle joined 20:09 ShaneC left 20:11 bubaflub joined 20:13 darbelo joined
kid51 kid51's reportDONE 20:14
DONE
* Participated in Parrot Developer Summit Sat May 14 2011 20:15
** Prepared agenda
** Posted summary on parrot-dev
* Infrastructure: communicated with OSU OSL re mailing problems on Sat/Sun
* Cage-cleaning: closed these tickets:
** trac.parrot.org/parrot/ticket/2104
** trac.parrot.org/parrot/ticket/2105
* Testing: Extensive pre-release testing particularly on Darwin/PPC
** On Darwin/PPC, we are experiencing inconsistent test results, i.e. files that will FAIL during 'make test' but PASS during 'prove' or vice versa.
** No consistency: The (typically single) failing file will change from one commit to the next.
** Suspect this is GC-related.
** But haven't filed a TT because this is practically non-reproducible. 20:16
WILL DO
* YAPC
** Beginning to prepare talk on Parrot community and process for YAPC::NA::2011.
** Make your conference and hotel reservations before May 20 to get discount.
** Make your plane reservations now.
* Tickets: Intend to close:
** trac.parrot.org/parrot/ticket/1722
EOR
20:17 soh_cah_toa joined
cotto_work *did: 20:21
- participated in PDS, seemed to go well
-- blogged: reparrot.blogspot.com/2011/05/thoug...n-pds.html
- made sure that 3.4.0 didn't escape without some kind of nci 't' support
-- a solution was found and pmuichaud seems to be happy
-- let's not do that again 20:22
- M0 progress:
-- mostly thinking
-- scheduled meeting with allison and dukeleto for the 28th
- GSoC progress:
-- nothing
*will do:
- M0 hacking, gsoc
*eor
pmichaud clarification: "satisfied." Not "happy."
20:31 PacoLinux joined
kid51 hello 20:32
Util 7-day ticket report:
2 closed: done
6 closed: fixed
8 new
2 reopened
.end
cotto_work hello, all
NotFound Hola
Util hello
mikehh hi there
soh_cah_toa hello
cotto_work How'd our goals go this week? 20:33
GOAL 1: Find someone to lead testing infrastrcture planning
GOAL 2: Contact all GSoC students
soh_cah_toa oh yeah, i still have to meet w/ dukeleto 20:34
mikehh Release went out ok 20:35
kid51 sees only 4 posts by GSOCers on parrot.org; I thought we had 7 students
cotto_work Has anyone heard from the GObject student?
Util NotFound said he would try the GCC compile farm, but no mention of overall leading.
cotto_work is trying to find his name 20:36
soh_cah_toa i'll mirror my blog after #ps
NotFound Util: ? I mentioned it in the report and in #parrot several times.
dukeleto hola
our GObject gsoc student is MIA
cotto_work cgaertner
dukeleto Christoph Gaertner
kid51 soh_cah_toa: You already have one post on parrot.org, so I was counting you as one of the four. but mirroring is necessary if you're primary blog is elsewhere. 20:37
soh_cah_toa kid51: oh, okay. will do
dukeleto kid51: i told my student (bubaflub++) that he could write his blog post in the next week, since he is graduating today
Util NotFound: so you did. Apologies; late to meeting and still backscrolling.
NotFound I'm doing make test right now in Debian/ppc64 in the farm, by the way.
kid51 That leaves cgaertner and lucian, correct?
20:38 whiteknight left
lucian kid51: yeah 20:38
sorry, i've only just demo-ed my dissertation today
cotto_work lucian's here, so he's not a risk. ;) 20:39
kid51 okay; a short, introductory post is all we need now. 1 paragraph sufficient
lucian apparently UK uni finishes very late
yeah, will do. tomorrow, likely
tadzik lucian: you should have seen PL Uni... 20:40
20:40 darbelo left 20:42 darbelo joined
cotto_work any questions? 20:42
kid51 Questions ... in general? or in some specific area? 20:43
cotto_work kid51: in general
kid51 So there was a lot of talk during PDS and on #parrot about benchmark testing of Parrot+Rakudo.
Does anyone know who pledged to do what on whose servers? 20:44
My impression is that a lot was to be done on pmichaud's machines ... 20:45
... which makes sense, since he's the primary consumer of benchmarking reports.
cotto_work The intent is that those be the canonical machines we use to decide whether performance has improved. 20:46
kid51 okay. And is there someone from the Parrot side who is the point person on this?
cotto_work I don't recall having someone volunteer for that role. 20:48
kid51 Well, I will write him to see what more specifically he needs from us. 20:49
pmichaud I'm here
I'll continue benchmarking if only because I need to keep track of rakudo performance changes as well
so it's easy for me to simply publish results
kid51 What, if anything, do you need from us on this (other than better code)?
pmichaud I'm expecting to (next couple of days) clean up the scripts a bit so that others can do similar tests as well
kid51 Can you post to parrot-dev when that's ready? 20:50
pmichaud sure
I don't have any other specific needs on this, other than to know if there are things I can be testing that would help Parrot. (more)
bacek++ has already been using the test suite to help tune his gc work
mikehh I am quite happy to help here, but don't necessarily want to be a pointy type person 20:51
pmichaud later today I expect to have a benchmark of rakudo-2011.04 running on Parrot 3.4.0
that should give us a really good idea of how parrot performance changed from 3.3.0 to 3.4.0
kid51 I have another question. 20:52
cotto_work: From your blog post, I gather that you and whiteknight will be the core of the Profiling team -- correct?
cotto_work kid51: yes but I haven't had a chance to coordinate with him yet. 20:53
kid51 When you do, if there's any part of the task in which you can rope in a 3rd or a 4th, that would be good (more)
... because you 2 are already committed to work in many different parts of the project.
cotto_work Volunteers are welcome. 20:55
The amount of work is unclear. There could be some very low-hanging fruit that gets up 95% of the way to something usable with 5 hours work, or it could take much longer.
any other questions or thoughts, about PDS or something else from the past week? 20:59
kid51 Make your YAPC OSCON and FOSSCON travel and presentation plans now! 21:00
cotto_work good idea 21:01
mikehh oh yes - we need something like smolder to keep track of tests, any ideas there 21:04
the current implementation seems broken
cotto_work mikehh: dukeleto's been using jitterbug 21:05
jitterbug.leto.net:3000/project/parrot
mikehh that seems to give build results, we also need test results 21:06
particularly failures 21:07
cotto_work It did. I suspect it's a temporary bug.
mikehh we need some way of reporting test failures on multiple platforms, so we can look at them in more detail 21:09
hopefully something like taptinder reports frpm the gcc compiler farm and others (windoze too) 21:10
dukeleto cotto_work: parrot found some bugs in jitterbug that i haven't had time to fix yet
mikehh from
cotto_work If anyone wants to help and knows Perl 5, I'm sure dukeleto could put you to work.
mikehh well let me know what to do and I''l give it a try
dukeleto github.com/franckcuny/jitterbug/issues/70 is what is blocking parrot on jitterbug
feel free to fix any other issues, too :)
21:14 kid51 left
dukeleto hopes to get parrot+jitterbug working again soon, but can give no time estimates 21:15
any gsoc students have questions? 21:17
soh_cah_toa nope 21:18
cotto_work do any non-students have questions? 21:22
mikehh I think we need to post the weekly goals to the Parrto Developer wiki, = I can do that if you want 21:23
dukeleto i guess i have a question 21:24
cotto_work mikehh: thanks.
dukeleto: go ahead
mikehh my typing is getting really bad, probably need some sleep
dukeleto currently, we have a lot of important docs only in our repo or only on the wiki page. This makes finding them hard.
we need to improve this situation
mikehh yes
dukeleto one example is deprecation info. api.yaml stores the basics, but all the actually important details are only on the wiki 21:25
this seems suboptimal
For example, if i have a parrot git repo and no net access, i can't figure out deprecation stuff. That sucks.
Util docs.parrot.org should be exporting the HTML-rendered docs from the repo.
dukeleto Util: sure. I am mostly talking about info that is only in the wiki 21:26
Util ok
21:26 soh_cah_toa left
dukeleto I am +1 to moving *all* deprecation data into our repo, and then we can link to the deprecation info on github instead of the wiki 21:26
mikehh or both 21:27
dukeleto mikehh: we want to minimize needing to keep things in sync, because, invariably, they will fall out of sync
we need *one* canonical place for deprecation data. Storing some of it parrot.git and some in our wiki is making the information less accessible.
mikehh that also suggests moving the wiki to github 21:28
a lot of our documentation is out of sync (also our tests and other things too) 21:29
I intended to start working on the tests in the next week 21:30
21:31 soh_cah_toa joined, eternaleye_ joined
cotto_work Consolidating all the deprecation data is a good idea. 21:32
mikehh: were you volunteering? 21:33
(no pressure; just clarifying)
mikehh I'll do some work on it, as much as I can work out what is needed 21:34
cotto_work mikehh: thank you
dukeleto mikehh: i don't want to convert all wiki pages to docs in our repo, only deprecation data, just to clarify 21:35
cotto_work dukeleto: yes
What goals should we set for the week?
mikehh dukeleto: yeah, but it might be a good idea to move other things to github, let me think on it 21:36
21:36 eternaleye left
dukeleto cotto_work: performance improvement would be nice, but wishing for them doesn't make them appear 21:38
mikehh do we have any branches, ready for merging/testing after the release 21:39
cotto_work I want to get the Select dynpmc into master soon. Apparently some Rakudo folks want it. 21:40
other goals? 21:42
I have:
GOAL 1: Merge/review Select dynpmc (cotto)
GOAL 2: Contact all GSoC students
GOAL 3: Consolidate deprecations data into api.yaml (mikehh)
dukeleto cotto_work: not sure all the info should go into api.yaml, but i agree with the rest
cotto_work: we may want to store the detailed explanations in a directory of POD files
cotto_work: like docs/deprecations/deprecations_for_parrot_x_y_z.pod or somesuch 21:43
cotto_work dukeleto: that's also an option. I'll leave it to mikehh++ to decide what makes the most sense.
mikehh we would need to keep that up-to-date
I'll have a look at what we have and then discuss it on #parrot or in parrot-dev 21:44
cotto_work mikehh: sounds good
dukeleto mikehh: sounds good. we definitely need to ask for more feedback 21:46
cotto_work Is there anything else before we call it a wrap? 21:49
Let's call it a wrap. 21:52
21:52 NotFound left 21:54 bluescreen left 22:10 dukeleto left 22:11 soh_cah_toa left 22:18 bubaflub left 22:28 darbelo is now known as me, me is now known as darbelo 22:30 whiteknight joined 22:37 pmichaud left 22:42 bubaflub joined 23:11 bubaflub left 23:20 darbelo_ joined, darbelo left, darbelo_ is now known as darbelo 23:29 lucian left 23:57 darbelo left