On Mon, Jan 14, 2019 at 8:35 PM Volker Braun <vbraun.n...@gmail.com> wrote: > > So I take it you volunteer to maintain the py3 buildbot configuration?
No, I do not. It's not my buildbot and I don't have control over that infrastructure as your follow-up message makes clear: > The buildbot physically moved this week, it might take some more time to set > up all networking Making suggestions for how best to handle an issue is not a volunteer to handle that issue, especially if isn't practical to do so, and suggesting otherwise is a kind of passive aggressiveness. If you disagree you can just openly disagree, though I believe my suggestion is one that requires the least work for everyone involved (since it's merely a question of what arguments to pass to perform the tests). > On Monday, January 14, 2019 at 11:45:20 AM UTC+1, E. Madison Bray wrote: >> >> In fact I'd argue it doesn't even require a Makefile target, >> as the relevant buildbot(s) for Python 3 can be configured to run that >> command (though having a list checked into the repository is useful, >> whether it's positive (list of known passing) or negative (list of >> known failures). > > -- > You received this message because you are subscribed to the Google Groups > "sage-release" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to sage-release+unsubscr...@googlegroups.com. > To post to this group, send email to sage-release@googlegroups.com. > Visit this group at https://groups.google.com/group/sage-release. > For more options, visit https://groups.google.com/d/optout. -- You received this message because you are subscribed to the Google Groups "sage-release" group. To unsubscribe from this group and stop receiving emails from it, send an email to sage-release+unsubscr...@googlegroups.com. To post to this group, send email to sage-release@googlegroups.com. Visit this group at https://groups.google.com/group/sage-release. For more options, visit https://groups.google.com/d/optout.
