This issue tracker has been migrated to GitHub ,
and is currently read-only.
For more information,
see the GitHub FAQs in the Python's Developer Guide.
| Author | loewis |
|---|---|
| Recipients | loewis, nnorwitz, trent |
| Date | 2008年04月11日.06:31:22 |
| SpamBayes Score | 0.004876933 |
| Marked as misclassified | No |
| Message-id | <1207895484.64.0.813690522002.issue2611@psf.upfronthosting.co.za> |
| In-reply-to |
| Content | |
|---|---|
I think this will be fairly difficult to set up. If the clean buildstep had been executed, you would have to rerun configure and compile before you can run any tests. Also, how would you communicate what specific test you want to run? A "builder" (a lane in the waterfall) has a fixed sequence of build steps, where one is "test", and a step can be described with a shell command. The test step simply invokes "make buildbottest". I don't know whether it's possible to pass per-build parameters to each step (except perhaps to the svn step); you could ask for that on the buildbot mailing list. The simplest solution to achieve the desired effect is to create a branch in subversion where the buildbottest target does something different, and then ask the slave in question to build that branch. In any case, no, I won't be able to look into this further anytime soon. |
|
| History | |||
|---|---|---|---|
| Date | User | Action | Args |
| 2008年04月11日 06:31:25 | loewis | set | spambayes_score: 0.00487693 -> 0.004876933 recipients: + loewis, nnorwitz, trent |
| 2008年04月11日 06:31:24 | loewis | set | spambayes_score: 0.00487693 -> 0.00487693 messageid: <1207895484.64.0.813690522002.issue2611@psf.upfronthosting.co.za> |
| 2008年04月11日 06:31:23 | loewis | link | issue2611 messages |
| 2008年04月11日 06:31:22 | loewis | create | |