On 5/15/2018 12:20 PM, Alex Gaynor wrote:
FWIW, attached is an image pointing out the re-run button. If you're not
seeing those it means either a) you're not logged into Travis, b)
somehow it's not picking up your permissions correctly.
Is there anything in the devguide about this? The first
That's very helpful, thanks. The issue was that I wasn't logged on to
Travis. I didn't know that was a thing.
I'll check and see if this info is in the devguide.
Eric
On 5/15/18 12:20 PM, Alex Gaynor wrote:
FWIW, attached is an image pointing out the re-run button. If you're
not seeing those
On 5/16/2018 2:31 AM, Victor Stinner wrote:
Oh, maybe I saw them. Are you talking about:
"test_multiprocessing_forkserver: TestIgnoreEINTR.test_ignore() fails
on Travis CI"
https://bugs.python.org/issue33531
"test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI"
https://b
Oh, maybe I saw them. Are you talking about:
"test_multiprocessing_forkserver: TestIgnoreEINTR.test_ignore() fails
on Travis CI"
https://bugs.python.org/issue33531
"test_asyncio: test_subprocess test_stdin_broken_pipe() failure on Travis CI"
https://bugs.python.org/issue33532
(I just created the
It seems like the job has been rescheduled. I cannot see the failure
("394 tests OK"). Would you mind to open a bug report?
Do you only see these failures in the 3.6 branch?
Victor
2018-05-15 16:36 GMT-04:00 Terry Reedy :
> I am getting repeated bogus failures, completely unrelated to a trivial
I am getting repeated bogus failures, completely unrelated to a trivial
patch, more often than not, on Travis-CI
For instance,
https://travis-ci.org/python/cpython/jobs/379349709
2 tests failed:
test_asyncio test_multiprocessing_forkserver
1 test altered the execution environment:
test_im
IIUC you have to close and reopen the PR.
On Tue, May 15, 2018 at 11:35 AM, Eric V. Smith wrote:
> Thanks. You mean close and re-open the bpo issue?
>
> In the past I saw a Travis "re-run" button, but now I don't. I expected to
> see it on the Travis page, but last night I only saw a "More optio
You can always close and then open an issue to re-trigger CI. As for Travis
specifically, you should have the proper permissions to forcibly re-run
the builds.
On Mon, 14 May 2018 at 21:50 Eric V. Smith wrote:
> I accidentally checked in some test files, and they got backported to
> 3.7. I push
Thanks. You mean close and re-open the bpo issue?
In the past I saw a Travis "re-run" button, but now I don't. I expected
to see it on the Travis page, but last night I only saw a "More options"
menu and no "re-run". The next time something fails I'll look again.
On 5/15/18 11:23 AM, Brett Ca
On 5/14/2018 9:49 PM, Eric V. Smith wrote:
I accidentally checked in some test files, and they got backported to
3.7. I pushed a commit to delete them, and it was committed to master.
But in the 3.7 backport, something has gone wrong with AppVeyor and
Travis-CI.
https://github.com/python/cpy
I accidentally checked in some test files, and they got backported to
3.7. I pushed a commit to delete them, and it was committed to master.
But in the 3.7 backport, something has gone wrong with AppVeyor and
Travis-CI.
https://github.com/python/cpython/pull/6844
AppVeyor says "Expected — Wa
11 matches
Mail list logo
