-
Notifications
You must be signed in to change notification settings - Fork 9.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
tests: hash more files for devtools test cache #11417
Conversation
Oh, I do expect this to fail now because of #11414 (comment) |
.github/workflows/devtools.yml
Outdated
${{ env.DEVTOOLS_PATH }} | ||
${{ env.BLINK_TOOLS_PATH }} | ||
${{ github.workspace }}/lighthouse/.tmp/chromium-web-tests/content-shells | ||
key: ${{ runner.os }}-${{ hashFiles('lighthouse/.github/workflows/devtools.yml', 'lighthouse/dist/lighthouse-dt-bundle.js', 'lighthouse/lighthouse-core/test/chromium-web-tests/download-*') }} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lighthouse/dist/lighthouse-dt-bundle.js
won't this mean it won't use the cache on basically any change to core?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shoot, good point. I will use the build bundle, devtools entry, and devtools reports files instead.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, probably! 😁
Current CI failure is that is cuz it wants #11418 landed |
For changes like #11411 . GitHub actions cache will keep stuff around for a week, so we need a way to invalidate it when the devtools bundle changes.