-
Notifications
You must be signed in to change notification settings - Fork 19
feat: store intermediate_recipe.yaml in debugdir #410
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
base: main
Are you sure you want to change the base?
feat: store intermediate_recipe.yaml in debugdir #410
Conversation
I think we should always write this file to |
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.
I think this is an important feature. Would you be able to write a simple test that this file is created?
Also, can you write this in the documentation? In some way so users can find this file while debugging pixi build stuff.
); | ||
|
||
// Save intermediate recipe in the debug dir | ||
let debug_path = directories.work_dir.join("intermediate_recipe.yaml"); |
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.
Can this recipe still change? If not, why not call this recipe.yaml
?
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.
After thinking (Initially, I didn't agree with renaming), I think we can name it recipe.yaml
} | ||
|
||
#[tokio::test] | ||
async fn test_conda_build_v1() { |
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.
new test for both building and intermediate recipe
Overview
How to test this:
After running
pixi build
/pixi lock
, you should seeintermediate_recipe.yaml
inthe work folder like this:It is added for both v0/v1 protocol methods