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
test_events_watched_outside_test_are_ignored fails with PermissionError #112
Comments
Hey! Hehe, I am trying to pack this python package into Gentoo too! :) My gentoo bug is https://bugs.gentoo.org/669272 What is your gentoo bug or pull request? So we do not do the same job twice. I am also having the same issue. If I discover anything worthwhile I'll post here. |
Ah, thanks for the information :) |
Hi,
Thanks for the report.
According to the man, EPERM on epoll_ctl happens when:
"The target file fd does not support epoll. This error can occur if fd
refers to, for example, a regular file or a directory."
In this case, it seems to be because we are trying to register a FileMock
obect, but the loop in a test case is patched to support this.
Can you tell me which exact version of Python you are using and in which
order the tests are running (especially, which tests run before this one)?
Also, are you running the test suite in a sandboxed environment (as in "the
test suite is executed in the packaging script")?
Le ven. 16 nov. 2018 à 08:19, Michael Seifert <notifications@github.com> a
écrit :
… Ah, thanks for the information :)
I did not open a Gentoo bug or pull request, because I do not want to be a
maintainer of the package (yet). I added it to my overlay:
https://github.com/digitalernachschub/gentoo-overlay/blob/master/dev-python/asynctest/asynctest-0.12.2.ebuild
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#112 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAL7GDyeVHRK_EjaPTZSWT-55Pre96KDks5uvmbogaJpZM4YdhPI>
.
--
Martin <http://www.martiusweb.net> Richard
www.martiusweb.net
|
Hi! :) Thanks to you for willing to have a look! So the list of tests in the order of execution is the following:
The command line that kicks in the tests is I am afraid it fails on all python versions. At least in my case I confirm it to fail with the same error message for python of versions:
The tests are being executed within portage sandbox. I am not very strong about what it actually means. Also, I did try to disable all such 'sandboxing' concepts within Portage (portage is a gentoo package manager) but the test failure persisted. I do accept there's a chance that I did not disable all the sandboxing features of portage since I am just learning inners of portage. |
Also, in case it helps - I tried to pack the bleeding edge, i.e. current master of asynctest into Gentoo and the outcome was the same - the same test was failing. So at the moment I am targeting 0.12.2 version. Though I am fine to switch back to the current master snapshot if that's necessary. |
Same here on Fedora rawhide. |
Interestingly enough, if I enter the build container using |
I am currently trying to package asynctest-0.12.2 for Gentoo Linux and I am running into a test error:
I acquired the source tarball from PyPI and executed the test with the command
PYTHONPATH=. python3.6 -m unittest --verbose test
. All other tests run successfully.Am I doing something wrong or can you reproduce the issue, too?
The text was updated successfully, but these errors were encountered: