Team Chat Logs

February 15, 2010

2010 1
Mo Tu We Th Fr Sa Su
1 2 3 4 5 6 7
8 9 10 11 12 13 14
15 16 17 18 19 20 21
22 23 24 25 26 27 28
<< <   > >>

[07:11:01.768110]<Hodgestar>osimons: You around?
[07:11:15.276678]<osimons>Hodgestar: yeah
[07:11:30.657967]<Hodgestar>osimons: I'm about to file a ticket in the bug tracker for implementing reading build files from external sources.
[07:12:06.212990]<osimons>Hodgestar: don't you know our bug tracker is full? you need to close some tickets before being able to create new ones...
[07:12:07.370495]<Hodgestar>Now to try find any related tickets. :)
[07:12:17.596069]<Hodgestar>osimons: I do. :/
[07:12:35.144470]<osimons>hehe. would that be like a report type for 'build'?
[07:12:36.731383]<Hodgestar>But this was what I needed now. :)
[07:13:15.002713]<osimons>there is no such open tickets, but i have often wondered about it - if we are talking about the same thing.
[07:14:12.355859]<osimons>i'm envisioning a 'build' type summarizer that can list files/tasks/targets or whatever and summarize the events
[07:14:18.578964]<Hodgestar>I have found the ticket: http://bitten.edgewall.org/ticket/230
[07:14:29.280745]<osimons>problem is that all the build tools vary a lot in what they actually do...
[07:14:39.004470]<Hodgestar>This is not *quite* what I've implemented.
[07:15:04.633134]<osimons>AHHH. recipe.
[07:15:19.123261]<Hodgestar>http://bitten.edgewall.org/ticket/301 -- what I've implement is closer to this.
[07:15:37.469003]<Hodgestar>Oops. Bad word to leave out of my initial description. :)
[07:16:08.588990]<Hodgestar>Let me add to #301.
[07:16:34.420619]<osimons>i see. "build files" as in recipes or partial recipes for inclusion in the bitten recipe/steps. not "build files" as output from running build tools.
[07:16:36.714412]<osimons>got it.
[07:16:45.034554]<osimons>then there are really a lot of related tickets...
[07:17:45.032666]<osimons>bitten.edgewall.org/query?status=!closed&group=milestone - most should be on 0.7 milestone i think
[07:19:55.238682]<osimons>http://bitten.edgewall.org/query?status=!closed&group=milestone&max=150 actually seeing we now have passed 100 open tickets again...
[07:22:39.749704]<osimons>Hodgestar: done in a way that allows us to extend the logic of xml parsing - like later adding conditional steps and so on? i haven't spent any time thinking about this really, so don't quite have a good picture of what it should look like
[07:29:31.927054]<Hodgestar>I've uploaded the patch. I'm busy describing what I've done in the ticket.
[07:36:45.393802]<Hodgestar>Okay. Ticket updated.
[07:36:48.466226]<Hodgestar>Off home.
[07:37:33.023104]<Hodgestar>Thoughts welcome.
[15:06:56.942773]<fatbrain_t>hi, running pylint usign <sh:exec ... /> is there some way I can supress any status message != 0 causing build-failure?
[15:24:53.973422]<osimons>fatbrain: i think that is what the script does - not sure what happens if your run it like a python module, like: <python:exec module="pylint.lint" output="pylint.out" args="--output-format=parseable mypackage" />
[15:25:28.814573]<osimons>as long as it raises exit != 0, bitten will see it as an error
[15:26:28.365457]<osimons>however, your best best expecting this is to use onerror="ignore" on your step to at least not make build abort due to trivial issues
[15:32:46.927996]<osimons>as a final idea you could of course make a tiny wrapper yourself that ignores error codes < 32 (that is just used for reporting according to pylint --help).
[15:33:16.001435]<osimons>> 0 and < 32 of course :-)