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.

Sign up for GitHub

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

Jump to bottom

Use a different path for the Kernel cache if possible #2036

Merged
merged 5 commits into from
Dec 26, 2019
Merged

Use a different path for the Kernel cache if possible #2036

merged 5 commits into from
Dec 26, 2019

Commits on Dec 26, 2019

  1. Added test to verify cache issue

    @sergeyklay
    sergeyklay committed Dec 26, 2019
    Configuration menu
    Copy the full SHA
    e087fbb View commit details
    Browse the repository at this point in the history

  2. Use a different path for the Kernel cache if possible 

    This patch fixes a cache collision issue. The issue is after creating the
cache and filling it with a project-specific configuration, there is no
way to invalidate it. Any next project will use the same cache and the
same Kernel configuration (if any).
    @sergeyklay
    sergeyklay committed Dec 26, 2019
    Configuration menu
    Copy the full SHA
    673da46 View commit details
    Browse the repository at this point in the history

  3. Small CS fix

    @sergeyklay
    sergeyklay committed Dec 26, 2019
    Configuration menu
    Copy the full SHA
    9b1c705 View commit details
    Browse the repository at this point in the history

  4. Update change log

    @sergeyklay
    sergeyklay committed Dec 26, 2019
    Configuration menu
    Copy the full SHA
    30ec466 View commit details
    Browse the repository at this point in the history

  5. Minor cleanup and update change log

    @sergeyklay
    sergeyklay committed Dec 26, 2019
    Configuration menu
    Copy the full SHA
    964eaf0 View commit details
    Browse the repository at this point in the history