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

Azure macOS job is failing + "pip search" throttling #9030

Closed
uranusjr opened this issue Oct 21, 2020 · 4 comments · Fixed by #9057
Closed

Azure macOS job is failing + "pip search" throttling #9030

uranusjr opened this issue Oct 21, 2020 · 4 comments · Fixed by #9057
Labels
C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes

Comments

@uranusjr
Copy link
Member

uranusjr commented Oct 21, 2020

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

E       AssertionError: temp files not expected
-- created: -------------------
  tmp/com.apple.dyld
          sh-B4B247918EFC62F0DED3F9B92246A6C10C7FECE20649ECEA30D36D86DEF79029.closure  (39976 bytes)
          uname-8487F8338686B8B010BF7BAEFA1A50C27FCA318D2FED3E6B363D8D561583F290.closure  (36168 bytes)

(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?

@uranusjr uranusjr added C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes labels Oct 22, 2020
@pradyunsg pradyunsg changed the title Azure macOS job is failing Azure macOS job is failing + CI "pip search" throttling Oct 25, 2020
@pradyunsg
Copy link
Member

pradyunsg commented Oct 25, 2020

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)

@pradyunsg
Copy link
Member

#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. :(

@pradyunsg
Copy link
Member

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. :)

@pradyunsg pradyunsg changed the title Azure macOS job is failing + CI "pip search" throttling Azure macOS job is failing + "pip search" throttling Oct 26, 2020
@pradyunsg pradyunsg pinned this issue Oct 26, 2020
@pradyunsg
Copy link
Member

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
C: automation Automated checks, CI etc type: maintenance Related to Development and Maintenance Processes
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants