Seriously? Ok, what can I do to help make the pull tester more obvious, useful, etc? Two ways come to mind:
1) a greasemonkey script that integrates results into the pull request parts of the github website. Relatively easy to do, but only works for those that both have the greasemonkey plugin installed in their browser and install the to-be-written script. 2) update the pull request with a failure annotation. Hard to do well, easy to do badly. The key trick is keeping the number of annotations to a minimum. A note on each failure is obviously bad. Pull tester results: http://d.puremagic.com/test-results/pull.ghtml?runid=37324 Trunk tester: http://d.puremagic.com/test-results/test_data.ghtml?dataid=142816 Sigh, Brad On 1/22/2012 6:15 PM, GitHub wrote: > Branch: refs/heads/master > Home: https://github.com/D-Programming-Language/phobos > Commit: 21ceafeec2e39b77293a9bfc5acd8be0d59318d6 > > https://github.com/D-Programming-Language/phobos/commit/21ceafeec2e39b77293a9bfc5acd8be0d59318d6 > Author: Jonathan M Davis <[email protected]> > Date: 2012-01-22 (Sun, 22 Jan 2012) > > Changed paths: > M std/__fileinit.d > > Log Message: > ----------- > Merge pull request #401 from Numpsy/usewfuncs > > 64bit Windows always supports the W functions, so no need to check for them > > > > > > > _______________________________________________ > phobos mailing list > [email protected] > http://lists.puremagic.com/mailman/listinfo/phobos _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
