-
Notifications
You must be signed in to change notification settings - Fork 459
per-context cram test builds multiple contexts #13231
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
6585859 to
718e57f
Compare
| version: 0.0.1 | ||
|
|
||
| $ dune build @@_build/foo/pkg-install | ||
| building from foo |
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.
What is strange is that I don't observe this behaviour myself in #13237. @rgrinberg any idea what the difference is? There, in each context, context_name is reported as default.
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.
What if instead of dune exec you dune build _build/<context>/target and then execute the binaries? Maybe the issue is that dune exec is not passing the context to the build properly?
Signed-off-by: Sudha Parimala <sudharg247@gmail.com>
Signed-off-by: Sudha Parimala <sudharg247@gmail.com>
Signed-off-by: Sudha Parimala <sudharg247@gmail.com>
718e57f to
66f51f9
Compare
|
The benchmark failure seems unrelated; merging. Thanks for the reviews. |
Making the test build from multiple contexts as discussed in #13217. This is a minimal change compared to #13127.