Skip to content

sendpacketselement_filestreamwithoptions_success fails with timeout in net6.0 builds #63523

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.

Sign up for GitHub

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

Jump to bottom
Closed
runfoapp bot opened this issue Jan 7, 2022 · 5 comments
Closed

sendpacketselement_filestreamwithoptions_success fails with timeout in net6.0 builds #63523

runfoapp bot opened this issue Jan 7, 2022 · 5 comments
Assignees
@antonfirsov
Labels
area-System.Net.Sockets blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Milestone
6.0.x

Comments

@runfoapp
Copy link

runfoapp bot commented Jan 7, 2022 •
edited
Loading

Runfo Tracking Issue: sendpacketselement_filestreamwithoptions_success fails with timeout

Build Definition Kind Run Name

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 0 0
@ghost
Copy link

ghost commented Jan 7, 2022

I couldn't figure out the best area label to add to this issue. If you have write-permissions please help me learn by adding exactly one area label.

@ghost ghost added the untriaged New issue has not been triaged by the area owner label Jan 7, 2022
@ericstj ericstj mentioned this issue Jan 7, 2022
Merged
@ghost
Copy link

ghost commented Jan 8, 2022

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Runfo Tracking Issue: sendpacketselement_filestreamwithoptions_success fails with timeout

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1541374 runtime PR 62193 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539556 runtime PR 63450 net6.0-windows-Debug-x86-CoreCLR_release-Windows.7.Amd64.Open console.log runclient.py
1539523 runtime PR 63423 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539133 runtime PR 63454 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539088 runtime PR 63450 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1538184 runtime PR 62922 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1535437 runtime PR 62916 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
1 7 7
Author: runfoapp[bot]
Assignees: -
Labels:

area-System.Net.Http, untriaged
Milestone: -

@ericstj ericstj added the blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms' label Jan 10, 2022
@ericstj ericstj changed the title sendpacketselement_filestreamwithoptions_success fails with timeout sendpacketselement_filestreamwithoptions_success fails with timeout in net6.0 builds Jan 10, 2022
@runfoapp runfoapp bot mentioned this issue Jan 10, 2022
Closed
@ghost
Copy link

ghost commented Jan 11, 2022

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

Issue Details

Runfo Tracking Issue: sendpacketselement_filestreamwithoptions_success fails with timeout

Build Definition Kind Run Name Console Core Dump Test Results Run Client
1542332 runtime PR 63526 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1542116 runtime PR 63520 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1541587 runtime PR 63514 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1541374 runtime PR 62193 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539556 runtime PR 63450 net6.0-windows-Debug-x86-CoreCLR_release-Windows.7.Amd64.Open console.log runclient.py
1539523 runtime PR 63423 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539133 runtime PR 63454 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1539088 runtime PR 63450 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1538184 runtime PR 62922 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py
1535437 runtime PR 62916 net6.0-windows-Debug-x64-CoreCLR_release-Windows.11.Amd64.ClientPre.Open console.log runclient.py

Build Result Summary

Day Hit Count Week Hit Count Month Hit Count
0 10 10
Author: runfoapp[bot]
Assignees: -
Labels:

area-System.Net.Sockets, blocking-clean-ci, untriaged
Milestone: -

@karelz
Copy link
Member

karelz commented Jan 11, 2022 •
edited
Loading

Triage: Disable it in 6.0 branch for now. Or serialize the tests to avoid weird machine timings interfering.

@karelz karelz removed the untriaged New issue has not been triaged by the area owner label Jan 11, 2022
@karelz karelz added this to the 6.0.x milestone Jan 11, 2022
@antonfirsov antonfirsov mentioned this issue Jan 17, 2022
Merged
@ghost ghost added the in-pr There is an active PR which will close this issue when it is merged label Jan 17, 2022
@ghost ghost removed the in-pr There is an active PR which will close this issue when it is merged label Jan 25, 2022
@ghost ghost locked as resolved and limited conversation to collaborators Mar 10, 2022
@karelz
Copy link
Member

karelz commented Apr 8, 2022

Fixed in 7.0 (main) in PR #63702 and in 6.0.3 in PR #63888.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@antonfirsov antonfirsov

Labels
area-System.Net.Sockets blocking-clean-ci Blocking PR or rolling runs of 'runtime' or 'runtime-extra-platforms'
Projects
None yet
Milestone
6.0.x
Development

No branches or pull requests
4 participants
@karelz @danmoseley @antonfirsov @ericstj