Skip to content

Problem with Next.js Actions cache? #5353

Description

@targos

See #5352
No cache was found on Windows (but it was found on Linux): https://github.com/nodejs/nodejs.org/actions/runs/4873873254/jobs/8694059608

Activity

  1. targos commented on May 3, 2023

    @targos
    MemberAuthor

    That said, it doesn't seem like the cache helps a lot. My PR only added a page, but the build took 3m35s on Linux with cache and 3m50s on Windows without cache.

  2. AugustinMauroy commented on May 3, 2023

    @AugustinMauroy
    Member

    don't worry on redesign branch we use turbo and it's great

  3. ovflowd commented on May 3, 2023

    @ovflowd
    Member

    @targos I guess even by restoring the cache, Next.js did not use that cache (for some reason). But yes, on the major/website-redesign we made a lot of changes that should speed up the build process.

    Also the cache is done by a combination of branch-name, package-lock and other factors.

  4. AugustinMauroy commented on May 4, 2023

    @AugustinMauroy
    Member

    @targos We just update CI normally it's good

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions