Re: [python-committers] AppVeyor and Travis-CI

[Terry Reedy]

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 time I tried to 
use a rebuild button, there was some sort of login/registration 
procedure.  Since then, it just works when I am logged in to github.


Thank you for the image.  I did not know that the unlabeled symbols at 
the end of each line for the three sub-builds was a rerun button for the 
one sub-build.  Good to know to only re-run what is needed.


TJR


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Eric V. Smith]

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 it means either a) you're not logged into Travis, b) 
somehow it's not picking up your permissions correctly.


Alex

On Tue, May 15, 2018 at 11:36 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
options"
menu and no "re-run". The next time something fails I'll look again.

On 5/15/18 11:23 AM, Brett Cannon wrote:
> 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 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 — Waiting for status to be reported".
> There's no
> obvious way to get it to actually report the status, or to
restart.
> There is no "Details" button listed on the PR page.
>
> For Travis-CI, Miss Isslington sent me an email that says
"Backport
> status check is done, and it's a failure ❌ ." The Travis-CI
log file
> ends with a timeout:
>
>
 ==
> FAIL: test_stdin_broken_pipe
>  (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
>
 --
> Traceback (most recent call last):
>File
>
 
"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",
>
> line 214, in test_stdin_broken_pipe
>  self.loop.run_until_complete, coro)
> AssertionError: (,  'ConnectionResetError'>) not raised by run_until_complete
>
 --
>
> I'm sure this is all due to the heavy load the systems are
under. I
> can't find a way to kick both of these off again. I couldn't
find
> anything in the devguide, but if I missed it please let me know.
>
> Thanks.
> Eric
> ___
> python-committers mailing list
> python-committers@python.org

>
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org 
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/



--
"I disapprove of what you say, but I will defend to the death your 
right to say it." -- Evelyn Beatrice Hall (summarizing Voltaire)

"The people's good is the highest law." -- Cicero
GPG Key fingerprint: D1B3 ADC0 E023 8CA6



___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Terry Reedy]

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://bugs.python.org/issue33532

(I just created these two issues.)


Those are the two test files that failed, though I believe there were 
more test methods that failed in test_asyncio.



2018-05-16 2:22 GMT-04:00 Victor Stinner :

It seems like the job has been rescheduled.


I later restarted just the Travis test, so as to not toss the OK 
Appveyor test and have to wait another 4 hours to get it to pass again.


 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?


No.  However, it happened again on my next 3.6 only patch.  I restarted 
just Travis and it passed.  The failure rate the last 24 hours has been 
about 1/3.



2018-05-15 16:36 GMT-04:00 Terry Reedy :

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_importlib

The failures repeated on retest.  Can someone turn off the bad test methods?

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Victor Stinner]

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 these two issues.)

Victor

2018-05-16 2:22 GMT-04:00 Victor Stinner :
> 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
>> 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_importlib
>>
>> The failures repeated on retest.  Can someone turn off the bad test methods?
>>
>> tjr
>>
>> ___
>> python-committers mailing list
>> python-committers@python.org
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Victor Stinner]

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
> 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_importlib
>
> The failures repeated on retest.  Can someone turn off the bad test methods?
>
> tjr
>
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Terry Reedy]

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_importlib

The failures repeated on retest.  Can someone turn off the bad test methods?

tjr
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Guido van Rossum]

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 options" menu
> and no "re-run". The next time something fails I'll look again.
>
> On 5/15/18 11:23 AM, Brett Cannon wrote:
>
>> 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 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 — Waiting for status to be reported".
>> There's no
>> obvious way to get it to actually report the status, or to restart.
>> There is no "Details" button listed on the PR page.
>>
>> For Travis-CI, Miss Isslington sent me an email that says "Backport
>> status check is done, and it's a failure ❌ ." The Travis-CI log file
>> ends with a timeout:
>>
>> 
>> ==
>> FAIL: test_stdin_broken_pipe
>> (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
>> 
>> --
>> Traceback (most recent call last):
>>File
>> "/home/travis/build/python/cpython/Lib/test/test_asyncio/tes
>> t_subprocess.py",
>>
>> line 214, in test_stdin_broken_pipe
>>  self.loop.run_until_complete, coro)
>> AssertionError: (, > 'ConnectionResetError'>) not raised by run_until_complete
>> 
>> --
>>
>> I'm sure this is all due to the heavy load the systems are under. I
>> can't find a way to kick both of these off again. I couldn't find
>> anything in the devguide, but if I missed it please let me know.
>>
>> Thanks.
>> Eric
>> ___
>> python-committers mailing list
>> python-committers@python.org 
>> https://mail.python.org/mailman/listinfo/python-committers
>> Code of Conduct: https://www.python.org/psf/codeofconduct/
>>
>> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>



-- 
--Guido van Rossum (python.org/~guido)
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Brett Cannon]

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 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 — Waiting for status to be reported". There's no
> obvious way to get it to actually report the status, or to restart.
> There is no "Details" button listed on the PR page.
>
> For Travis-CI, Miss Isslington sent me an email that says "Backport
> status check is done, and it's a failure ❌ ." The Travis-CI log file
> ends with a timeout:
>
> ==
> FAIL: test_stdin_broken_pipe
> (test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
> --
> Traceback (most recent call last):
>File
> "/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",
>
> line 214, in test_stdin_broken_pipe
>  self.loop.run_until_complete, coro)
> AssertionError: (,  'ConnectionResetError'>) not raised by run_until_complete
> --
>
> I'm sure this is all due to the heavy load the systems are under. I
> can't find a way to kick both of these off again. I couldn't find
> anything in the devguide, but if I missed it please let me know.
>
> Thanks.
> Eric
> ___
> python-committers mailing list
> python-committers@python.org
> https://mail.python.org/mailman/listinfo/python-committers
> Code of Conduct: https://www.python.org/psf/codeofconduct/
>
___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Eric V. Smith]

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 Cannon wrote:

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 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 — Waiting for status to be reported".
There's no
obvious way to get it to actually report the status, or to restart.
There is no "Details" button listed on the PR page.

For Travis-CI, Miss Isslington sent me an email that says "Backport
status check is done, and it's a failure ❌ ." The Travis-CI log file
ends with a timeout:

==
FAIL: test_stdin_broken_pipe
(test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)
--
Traceback (most recent call last):
   File

"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py",

line 214, in test_stdin_broken_pipe
 self.loop.run_until_complete, coro)
AssertionError: (, ) not raised by run_until_complete
--

I'm sure this is all due to the heavy load the systems are under. I
can't find a way to kick both of these off again. I couldn't find
anything in the devguide, but if I missed it please let me know.

Thanks.
Eric
___
python-committers mailing list
python-committers@python.org 
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/


___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/

Re: [python-committers] AppVeyor and Travis-CI

[Terry Reedy]

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/cpython/pull/6844

AppVeyor says "Expected — Waiting for status to be reported". There's no 
obvious way to get it to actually report the status, or to restart. 
There is no "Details" button listed on the PR page.


For Travis-CI, Miss Isslington sent me an email that says "Backport 
status check is done, and it's a failure ❌ ." The Travis-CI log file 
ends with a timeout:


==
FAIL: test_stdin_broken_pipe 
(test.test_asyncio.test_subprocess.SubprocessSafeWatcherTests)

--
Traceback (most recent call last):
   File 
"/home/travis/build/python/cpython/Lib/test/test_asyncio/test_subprocess.py", 
line 214, in test_stdin_broken_pipe

     self.loop.run_until_complete, coro)
AssertionError: (, 'ConnectionResetError'>) not raised by run_until_complete

--

I'm sure this is all due to the heavy load the systems are under. I 
can't find a way to kick both of these off again. I couldn't find 
anything in the devguide, but if I missed it please let me know.


I have triggered retesting by editing the blurb.  It may be that 
touching by adding and deleting a space was enough, or maybe I had to 
actually change something.


But retesting right now, with tests failing, is useless.  I just 
submitting a trivial change and got the same unrelated failures for 
importlib, multiprocessing, and asyncio.


Warning -- files was modified by test_importlib
  Before: []
  After:  ['core']

ERROR: test_ignore (test.test_multiprocessing_forkserver.TestIgnoreEINTR)
--
Traceback (most recent call last):
  File 
"/home/travis/build/python/cpython/Lib/test/_test_multiprocessing.py", 
line 4359, in test_ignore

os.kill(p.pid, signal.SIGUSR1)
ProcessLookupError: [Errno 3] No such process
--
Ran 310 tests in 93.862s
FAILED (errors=1, skipped=27)
test test_multiprocessing_forkserver failed

and the same or similar multiple failures for asyncio

Both our tests ended with

FAILED (failures=2, skipped=14)
test test_asyncio failed
2 tests failed again:
test_asyncio test_multiprocessing_forkserver
Total duration: 14 min 29 sec
Tests result: FAILURE

and we cannot merge.

___
python-committers mailing list
python-committers@python.org
https://mail.python.org/mailman/listinfo/python-committers
Code of Conduct: https://www.python.org/psf/codeofconduct/