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

A symlink always pointing to the most recent experiment's artifact directory should exist #619

Open
erichaagdev opened this issue May 20, 2024 · 0 comments

Comments

@erichaagdev
Copy link
Member

erichaagdev commented May 20, 2024

For each experiment, there exists a latest symlink that always points to the most recent experiment's artifact directory. For example:

.data/
├─ 01-validate-incremental-building/
│  ├─ 20231030T095641-653fc429/
│  ├─ 20240311T121101-65ef3b25/
│  ├─ latest/
├─ 03-validate-local-build-caching-different-locations/
│  ├─ 20240311T121415-65ef3be7/
│  ├─ latest/

We should additionally add a symlink directly beneath .data that always points to the most recent experiment's artifact directory across all experiments. For example:

.data/
├─ latest/
├─ 01-validate-incremental-building/
│  ├─ 20231030T095641-653fc429/
│  ├─ 20240311T121101-65ef3b25/
│  ├─ latest/
├─ 03-validate-local-build-caching-different-locations/
│  ├─ 20240311T121415-65ef3be7/
│  ├─ latest/

If 03-validate-local-build-caching-different-locations/20240311T121415-65ef3be7 was the most recently run experiment across all experiments, then .data/latest/ would be a symlink of .data/03-validate-local-build-caching-different-locations/20240311T121415-65ef3be7/.

This is convenient when you know you know what you want to inspect is the most recent experiment's artifacts. This can also help simplify automation scenarios when you want to grab the receipt file of the latest experiment run because you do not need to know the name of the script to grab the receipt.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant