2018-06-04 18:31 GMT+02:00 Victor Stinner :
> Quick update a few days later.
> (...)
> Except Windows 7 which has issues with test_asyncio and
> multiprocessing tests because this buildbot is slow, it seems like
> most CIs are now stable.
The bug wasn't specific to this buildbot, it was a very
2018-06-07 4:45 GMT+02:00 Mariatta Wijaya :
> Are there APIs we can use to check the status of builbots?
Buildbots offer different ways to send notifications: emails and IRC
bot for example.
If you want to *poll* for recent builds, I don't know. I would suggest
to use notifications (push) rather
On Wed, Jun 6, 2018 at 9:45 PM, Mariatta Wijaya
wrote:
> Are there APIs we can use to check the status of builbots?
> Maybe we can have the our bots check for the buildbot status in backport
> PRs.
There is a REST API for buildbot; I have no idea how usable/useful it
is though (but I think the
Are there APIs we can use to check the status of builbots?
Maybe we can have the our bots check for the buildbot status in backport
PRs.
On Wed, May 30, 2018, 2:33 AM Victor Stinner wrote:
>
> Buildbots only send email notifications to buildbot-sta...@python.org
> when the state changes from
Activating Travis CI GitHub app is being tracked in
https://github.com/python/core-workflow/issues/255
Let's not press the button until after the 3.7 release.
On Wed, Jun 6, 2018, 3:57 PM INADA Naoki wrote:
>
> 2018年6月7日(木) 2:44 Brett Cannon :
>
>>
>> On Wed, 6 Jun 2018 at 09:27 INADA
2018年6月7日(木) 2:44 Brett Cannon :
>
> On Wed, 6 Jun 2018 at 09:27 INADA Naoki wrote:
>
>> First I was also
>>> confused between travis-ci.com and travis-ci.org ... The documentation
>>> shows an example with .com, but Python organization uses .org.
>>>
>>> Victor
>>>
>>
>> .org is legacy.
>>
On Wed, 6 Jun 2018 at 09:27 INADA Naoki wrote:
> First I was also
>> confused between travis-ci.com and travis-ci.org ... The documentation
>> shows an example with .com, but Python organization uses .org.
>>
>> Victor
>>
>
> .org is legacy.
>
> Open source projects can migrate to new .com.
>
>
> First I was also
> confused between travis-ci.com and travis-ci.org ... The documentation
> shows an example with .com, but Python organization uses .org.
>
> Victor
>
.org is legacy.
Open source projects can migrate to new .com.
Maybe, ssh is .com only feature.
On 06.06.2018 18:10, Victor Stinner wrote:
2018-06-04 21:37 GMT+02:00 Ivan Pozdeev :
https://docs.travis-ci.com/user/running-build-in-debug-mode/ is the official
doc on how to debug a Travis CI build via ssh.
Did you already try it? The doc mentions a "[Debug]" button, but I
cannot see it
2018-06-04 21:37 GMT+02:00 Ivan Pozdeev :
> https://docs.travis-ci.com/user/running-build-in-debug-mode/ is the official
> doc on how to debug a Travis CI build via ssh.
Did you already try it? The doc mentions a "[Debug]" button, but I
cannot see it whereas I'm logged in in the Python
No, replying only to you wasn't intended.
https://docs.travis-ci.com/user/running-build-in-debug-mode/ is the
official doc on how to debug a Travis CI build via ssh.
On 04.06.2018 22:31, Victor Stinner wrote:
FYI you only replied to me in private. Is it on purpose?
I'm interested if I can
2018-05-30 11:33 GMT+02:00 Victor Stinner :
> I fixed a few tests which failed randomly. There are still a few, but
> the most annoying have been fixed.
Quick update a few days later.
For an unknown reason,
test_multiprocessing_forkserver.TestIgnoreEINTR.test_ignore() started
to fail very
Hi,
I fixed a few tests which failed randomly. There are still a few, but
the most annoying have been fixed. I will continue to keep an eye on
our CIs: Travis CI, AppVeyor and buildbots. Sometimes, even when I
report a regression, the author doesn't fix the bug. But when a test
fails on Travis CI
13 matches
Mail list logo
