On Fri, Sep 4, 2009 at 8:02 PM, Minh Nguyen<[email protected]> wrote:
>
> Hi John,
>
> On Sat, Sep 5, 2009 at 1:34 AM, John Cremona<[email protected]> wrote:
>>
>> The following tests failed:
>>
>> sage -t "devel/sage/sage/server/notebook/notebook.py"
>> sage -t "devel/sage/sage/server/notebook/worksheet.py"
>
> These are the same failures as those reported at the sage-devel thread
>
> http://groups.google.com/group/sage-devel/browse_thread/thread/5370af4b74c5ca3c
>
> These issues are being tracked at ticket #6884
>
> http://trac.sagemath.org/sage_trac/ticket/6884
We should write a little 1-line script that anybody can run that:
(1) downloads, builds and tests whatever the latest sage alpha is.
(2) posts the result (=testlong.log and install.log) online
somewhere once the test is done.
(3) Then another script that goes through all the uploaded files and
summarizes all issues.
Here's my simplistic (1):
rm buildbot; wget
http://sage.math.washington.edu/home/wstein/buildbot; chmod +x
buildbot; ./buildbot
This works for me, since I update the script "buildbot" whenever there
is a new release.
Regarding (2), probably email is the way to go, but maybe something
else???. We could setup a sage-release-data google group or ?
Any thoughts?
This could help a lot, I think. Then instead of asking people to
manually go through build results, try to summarize them in various
ways, check that they aren't posting existing problems, etc., they
just type
./bb
and donate their computer's resources, but not their own time.
William
--~--~---------~--~----~------------~-------~--~----~
To post to this group, send an email to [email protected]
To unsubscribe from this group, send an email to
[email protected]
For more options, visit this group at http://groups.google.com/group/sage-devel
URLs: http://www.sagemath.org
-~----------~----~----~----~------~----~------~--~---
