-
Notifications
You must be signed in to change notification settings - Fork 56
Create vfs-overlay.yaml on demand #931
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
Conversation
`vfs-overlay.yaml` refers to paths from the `swift` source directory, which may not be available in subsequent jobs, causing build issues. These changes make the path in `vfs-overlay.yaml` easily changeable for subsequent jobs, fixing the issue.
I'm not sure that I understand the need for this. Why not simply create the VFS Overlay from scratch if needed? |
I didn't want to modify the scripts too much. I changed this to create the vfs-overlay from scratch. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Other than what @jeffdav says about the path handling, LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Double check that path thing...
vfs-overlay.yaml
created as part of thestdlib
step refers to paths from theswift
source directory, which may not be available in subsequent jobs, causing build issues. These changes generate avfs-overlay.yaml
file on demand for jobs that need it, to work around the issue.