On Wednesday, July 18, 2018 at 8:13:12 AM UTC+10, Volker Braun wrote:
>
> I do appreciate your hard work in making Cygwin work. But IMHO thats a
> rather high-risk upgrade with little reward. Nobody stops you from merging
> that ticket when building cygwin binaries. And realistically we don't h
https://trac.sagemath.org/ticket/25379
Purportetly fixes this randomly occuring bug:
sage -t --long src/sage/coding/code_constructions.py
**
File "src/sage/coding/code_constructions.py", line 624, in
sage.coding.code_constructi
The buildbot master config isn't public since it includes the worker
passwords. Though I think the worst case means somebody can submit
incorrect build results. Still, there wasn't much need to make the config
public. If you want to have it I'm happy to send you an archive. More
interesting are
I do appreciate your hard work in making Cygwin work. But IMHO thats a
rather high-risk upgrade with little reward. Nobody stops you from merging
that ticket when building cygwin binaries. And realistically we don't have
anyone developing on Cygwin only at this point.
[ ] I want to delay all
Volker, be reasonable. You should know that there have been unique
challenges involved in getting a buildbot set up for Windows, not the
least of which being simply the availability of dedicated hardware.
In the meantime, I *am* the buildbot for Windows; I build and test
each tagged release myself
Does anyone know where it lives? Is there a repository for it? I was
thinking it should be under github.com/sagemath but nothing stands
out.
I would like to try to set up a buildbot, but it's unclear exactly
*how* to do that when I don't even know what the builder
configurations are (knowing how
+1 for me too.
Sébastien
--
You received this message because you are subscribed to the Google Groups
"sage-devel" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to sage-devel+unsubscr...@googlegroups.com.
To post to this group, send email to sage-devel@
