On Sunday, January 22, 2012 18:33:04 Brad Roberts wrote: > 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
I checked the autotester first. It was passing. My guess is that it was the version _before_ the most recent update to that pull request that had passed, and it hadn't gotten the chance to build again, but I don't know. I'm looking into it now. - Jonathan M Davis _______________________________________________ phobos mailing list [email protected] http://lists.puremagic.com/mailman/listinfo/phobos
