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

fix: different cache path leads to cache miss #1695

Merged
merged 1 commit into from Jun 2, 2023
Merged

Conversation

skjnldsv
Copy link
Member

@skjnldsv skjnldsv commented Jun 2, 2023

@skjnldsv skjnldsv force-pushed the feat/cache-test branch 5 times, most recently from a66fc76 to 16a0f64 Compare June 2, 2023 07:04
Signed-off-by: John Molakvoæ <skjnldsv@protonmail.com>
@skjnldsv skjnldsv changed the title testing: try fixing cache step on self-hosted fix: different cache path leads to cache miss Jun 2, 2023
with:
key: cypress-context-${{ github.run_id }}
path: /home/runner/work/viewer
path: ./
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is the important part, we need to have the same path

Comment on lines +72 to +79
- name: Set up node ${{ needs.init.outputs.nodeVersion }}
uses: actions/setup-node@64ed1c7eab4cce3362f8c340dee64e5eaeef8f7c # v3.6.0
with:
cache: 'npm'
node-version: ${{ needs.init.outputs.nodeVersion }}

- name: Set up npm ${{ needs.init.outputs.npmVersion }}
run: npm i -g npm@"${{ needs.init.outputs.npmVersion }}"
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also important, restoring the context does NOT restore the npm/node version 🙈
Meaning we've been running two different versions this whole time....

@skjnldsv skjnldsv self-assigned this Jun 2, 2023
@skjnldsv skjnldsv added bug Something isn't working 3. to review Waiting for reviews labels Jun 2, 2023
@skjnldsv
Copy link
Member Author

skjnldsv commented Jun 2, 2023

/backport to stable27

@backportbot-nextcloud backportbot-nextcloud bot added the backport-request Pending backport by the backport-bot label Jun 2, 2023
@skjnldsv skjnldsv requested a review from artonge June 2, 2023 07:50
@juliushaertl juliushaertl merged commit 5852a91 into master Jun 2, 2023
26 checks passed
@juliushaertl juliushaertl deleted the feat/cache-test branch June 2, 2023 08:34
@backportbot-nextcloud backportbot-nextcloud bot removed the backport-request Pending backport by the backport-bot label Jun 2, 2023
@skjnldsv
Copy link
Member Author

skjnldsv commented Jun 9, 2023

/backport to stable26

@backportbot-nextcloud backportbot-nextcloud bot added the backport-request Pending backport by the backport-bot label Jun 9, 2023
@skjnldsv
Copy link
Member Author

skjnldsv commented Jun 9, 2023

/backport to stable25

@backportbot-nextcloud
Copy link

The backport to stable26 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable26
git pull origin stable26

# Create the new backport branch
git checkout -b fix/foo-stable26

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable26

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

@backportbot-nextcloud
Copy link

The backport to stable25 failed. Please do this backport manually.

# Switch to the target branch and update it
git checkout stable25
git pull origin stable25

# Create the new backport branch
git checkout -b fix/foo-stable25

# Cherry pick the change from the commit sha1 of the change against the default branch
# This might cause conflicts. Resolve them.
git cherry-pick abc123

# Push the cherry pick commit to the remote repository and open a pull request
git push origin fix/foo-stable25

More info at https://docs.nextcloud.com/server/latest/developer_manual/getting_started/development_process.html#manual-backport

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
3. to review Waiting for reviews backport-request Pending backport by the backport-bot bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants