-
-
Notifications
You must be signed in to change notification settings - Fork 335
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Intermittent test failure in test_subprocess.py:test_signals: SIGINT causes startup failure in child Python and unexpected return value #1170
Comments
Seen again on Linux Python 3.6 in Azure Pipelines: https://dev.azure.com/python-trio/trio/_build/results?buildId=1461&view=logs&jobId=9a864fd9-6c8f-52ca-79ce-2aa6dca1a1de&j=9a864fd9-6c8f-52ca-79ce-2aa6dca1a1de&t=14435553-4bd6-5ab0-e7af-caf830f382a2
Originally posted by @pquentin in #851 (comment) |
I just noticed the note in #200 that mentions that we should select "Retain log" on Azure Pipelines. However I only see "Toggle timestamps". |
You have to go out to the run overview page, where all the jobs are listed.
And it looks like you also have to be logged in to an account with
permissions on our org, which unfortunately is totally independent of
github accounts... you need an "azure devops" account or something like
that.
…On Fri, Jan 31, 2020 at 2:19 AM Quentin Pradet ***@***.***> wrote:
I just noticed the note in #200
<#200> that mentions that we
should select "Retain log" on Azure Pipelines. However I only see "Toggle
timestamps".
[image: Capture d’écran 2020-01-31 à 14 17 20]
<https://user-images.githubusercontent.com/42327/73531680-67484880-4434-11ea-8767-29caff9dd705.png>
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#1170?email_source=notifications&email_token=AAEU42EDRM6S3XV4553DMBTRAP3KJA5CNFSM4IIN4UX2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEKOGDOI#issuecomment-580673977>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAEU42DCSJAQPHF3Q4ZTFXDRAP3KJANCNFSM4IIN4UXQ>
.
--
Nathaniel J. Smith -- https://vorpus.org <http://vorpus.org>
|
Observed here: https://dev.azure.com/python-trio/trio/_build/results?buildId=827&view=logs&jobId=300ae31b-e5d9-5bcb-b319-aee10d9d83f3
In this test we're sending SIGINT to a child process, and the child process happens to be Python, and apparently Python's startup logic is flaky if a SIGINT arrives at the wrong time.
I think the simplest fix would be to make the test use a different signal, one that Python doesn't catch? Maybe SIGKILL + SIGTERM, if we're worried about making sure that
send_signal
isn't accidentally doing the same thing askill
orterminate
?The text was updated successfully, but these errors were encountered: