Skip to content
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

9358 archer0001 sendbuffer #946

Closed

Conversation

archer0001
Copy link

https://twistedmatrix.com/trac/ticket/9358

Tested as a side effect of other reactor tests.

Additionally updated build script to work with both visual studio and mingw builds, maintaining default behaivor of using mingw.

Updated send and accept to no longer attach the buffer to the completion
event, saving memory.  Current tests pass.
@archer0001
Copy link
Author

I'm unsure why the AppVeyor build is failing. I installed all test deps and 64 bit python 3.6 in a test VM. Running trial twisted.web.tests yields a successful test.

@@ -225,7 +225,7 @@ cdef class CompletionPort:

obj = None
if ov:
obj, ignored = <object>ov.attached
obj, _ = <object>ov.attached
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

is this change required?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not really. I can remove that change if you feel it's unnecessary.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That change is generating a big diff and the tests in this PR are failing :) ...so I don't know if this has any wild/crazy link with the test failures :)

As long as the tests are green I am ok with this cleanup :)

@@ -0,0 +1 @@
twisted.internet.iocpreactor.send no longer attaches send buffer to completion event, saving memory.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is twisted.internet.iocpreactor.send a real thing :)
twisted.internet.iocpreactor is a package and I don't see any send there
https://github.com/twisted/twisted/blob/twisted-17.9.0/src/twisted/internet/iocpreactor/__init__.py

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I need to update the newsfragment. It should be twisted.internet.iocpreactor.iocpsupport.send.

@adiroiban
Copy link
Member

I'm unsure why the AppVeyor build is failing. I installed all test deps and 64 bit python 3.6 in a test VM. Running trial twisted.web.tests yields a successful test.

Yes. I don't know. It seems that the error is constant on Appveyor

Unfortunately, due to lack of manpower (to implement the required infrastructure) we don't yet run all Buildbot tests for branches which are outside of the main Twisted repo.

I have triggered the tests on Builbot...to see what we get: https://buildbot.twistedmatrix.com/boxes-unsupported?branch=9358-archer0001-sendbuffer

https://buildbot.twistedmatrix.com/builders/windows7-32-py3.6/builds/81/steps/iocp/logs/problems

The test also fail on the Buildot.

But this might be related to #948

so we should first fix http://twistedmatrix.com/trac/ticket/9353 and then come back to this cleanup?

What do you think?

Thanks!

Copy link
Member

@adiroiban adiroiban left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for working on this.

Tested as a side effect of other reactor tests.

I think that the failure that we see here might be cause by https://twistedmatrix.com/trac/ticket/9353


Can we try to fix https://twistedmatrix.com/trac/ticket/9353 first and after that merge this?


I have no idea why the failure is triggered here.

Maybe include part of this code in https://twistedmatrix.com/trac/ticket/9353 so that we can see a test failing an Appveyour, and then after you apply your fix we can see that the test pass.

Does that make sense?

Thanks again!

@archer0001
Copy link
Author

Yup, I'm completely fine with resolving 9353 before hitting this.

@adiroiban adiroiban self-assigned this Mar 11, 2018
@glyph
Copy link
Member

glyph commented Sep 19, 2019

There are merge conflicts and I can't auto-resolve them (possibly because of the age of this PR) but this would certainly still be good to get fixed. 9353 (or its equivalent) has been resolved, and our current Windows build situation is much more reliable, so now might be a good time to try!

@glyph glyph closed this Sep 19, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants