-
-
Notifications
You must be signed in to change notification settings - Fork 517
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
tuist test
doesn't use cached binaries
#5034
Comments
I presume that what I am looking for in the console is the following line: [tvOSFramework] Compiling tvOSFramework_vers.c A fix would mean this does not appear in the test command output. Is that correct? |
Work in progress on this is on the branch bugfix/tuist-test-use-cached-binaries |
@ronanociosoig have you been able to make progress on this work? |
@Alex-Ozun you're asking, because you want to give it a shot? If not, I can take a look |
@leszko11 Please feel free to work on it |
Say no more 🏃🏼 |
Hey, folks 👋 Just a quick update that I already have a functioning prototype for this, so this feature should get in |
What happened?
When using
tuist test
command the cached binaries are ignored.We should leverage the tuist cache to speedup the tests execution.
How do we reproduce it?
app_with_tests
fixturetuist cache warm
tuist test
Error log
Cached targets are built from source even if the cache was already warmed
macOS version
12.3
Tuist version
3.15.0
Xcode version
14.2.0
The text was updated successfully, but these errors were encountered: