playground: fix metafile location

[dveeden]

What problem does this PR solve?

close #2611

What is changed and how it works?

1. The path for the tiup_process_meta was not build correctly.
2. This caused other tools like tiup status and tiup clean to consider the datadir to be abandoned and delete it.
3. Deleting the datadir for a running playground caused components to stop/crash

Check List

Tests

• Unit test
• Integration test
• Manual test (add detailed scripts or steps below)
• No code

Code changes

• Has exported function/method change
• Has exported variable/fields change
• Has interface methods change
• Has persistent data change

Side effects

• Possible performance regression
• Increased code complexity
• Breaking backward compatibility

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release notes:

playground: Fix the location to which the metadata file was written. 

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign xhebox for approval. For more information see the Code Review Process.
Please ensure that each of them provides their approval before proceeding.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[dveeden]

/cc @xhebox

[codecov-commenter]

Codecov Report

❌ Patch coverage is 80.00000% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 41.30%. Comparing base (3ec3c6f) to head (98963ad).

Files with missing lines	Patch %	Lines
pkg/localdata/profile.go	80.00%	0 Missing and 1 partial ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2638      +/-   ##
==========================================
+ Coverage   41.24%   41.30%   +0.06%     
==========================================
  Files         363      363              
  Lines       37532    37533       +1     
==========================================
+ Hits        15479    15502      +23     
+ Misses      20132    20104      -28     
- Partials     1921     1927       +6     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[dveeden]

/test all

[ti-chi-bot]

@dveeden: No presubmit jobs available for pingcap/tiup@master

Details

In response to this:

/test all

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[dveeden]

/retest all

[ti-chi-bot]

@dveeden: No presubmit jobs available for pingcap/tiup@master

Details

In response to this:

/retest all

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[wuhuizuo]

/retest all

@dveeden use /retest without any args.

prow will help to rerun the failed GitHub action jobs.

[wuhuizuo]

/retest

[dveeden]

@wuhuizuo I wanted to re-run the successful actions to re-try the upload to codecov. But that's now being fixed in #2639

Note that the integrate-dm test seem to always fail (both this branch and master)

[xhebox]

@wuhuizuo I wanted to re-run the successful actions to re-try the upload to codecov. But that's now being fixed in #2639

Note that the integrate-dm test seem to always fail (both this branch and master)

Yeah, DM tests failed recently. And I dont know why exactly.

[dveeden]

Looks like "integrate-dm" failed due to this:

Error: read manifest from mirror(https://tiup-mirrors.pingcap.com/) failed: manifest timestamp.json has expired at: 2025-07-26T11:18:30+08:00

This is what I get

$ TZ="Asia/Shanghai" date
Tue 11 Nov 14:57:10 CST 2025
$ curl -s https://tiup-mirrors.pingcap.com/timestamp.json | jq '.signed.expires'
"2025-12-11T14:26:26+08:00"

So it looks already expired?

[dveeden]

/retest

[xhebox]

So it looks already expired?

CDN issues. It sometimes happens on your PC, too. Just retry.

[dveeden]

So it looks already expired?

CDN issues. It sometimes happens on your PC, too. Just retry.

Yes I did. That works. I think this PR is now ready to be reviewed/merged.