-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Azure macOS job is failing + "pip search" throttling #9030
Comments
That, and it looks like our CI pipelines are hitting the newly introduced rate limits for PyPI's XMRPC API. :( Context: pypi/warehouse#4321 (comment) |
#9051 fixes the search issues. And, also surfaces that the underlying issue with the MacOS build affects all the tests, not just the build-env ones. :( |
I spent a fair bit of time looking into this, and I can't really find out what the heck is going on and why we're seeing those files. I'm experimenting with #9053, but opinions and thoughts on how to workaround this w/o access to scripttest are welcome. :) |
I recall @pradyunsg made the observation under a PR, but I can’t locate it now. (Edit: Found it #9017 (comment))
The specific failure is
(The list of files change depending on the test case.)
I did some research, it seems like
com.apple.dyld
is a storage called shared dyld cache and is a cache mechanism used by Apple’s dynamic linker (dyld3). All information I’ve found so far are about iOS, but it shouldn’t be surprising if Apple port that to macOS. This post from 2018 talks about the mechanism in more detail.I’m not sure why the Azure images use this mechanism (my machine running Catelina doesn’t seem to have them), but it seems like we should be safe to just ignore the whole
com.apple.dyld
directory when we check for temporary files?The text was updated successfully, but these errors were encountered: