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.

Sign up for GitHub

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

Jump to bottom

Paths for scripts #359

Closed
mernst opened this issue Sep 20, 2024 · 1 comment · Fixed by #370
Closed

Paths for scripts #359

mernst opened this issue Sep 20, 2024 · 1 comment · Fixed by #370

Comments

@mernst
Copy link
Collaborator

mernst commented Sep 20, 2024

The README at https://github.com/plume-lib/merging says:

Put directory .../merging/src/main/sh/ on your PATH, adjusting "..." according to where you cloned this repository. (Or, use the absolute pathname in uses of *.sh files below.)

The experimental infrastructure does not seem to do this. At least, what I observed is that it picks up the scripts from my own PATH rather than from the submodule. This leads to different results when I run it compared to when CI runs it.
@benedikt-schesch
Copy link
Owner

@mernst has this been fixed in one of the PRs?

@mernst mernst linked a pull request Sep 22, 2024 that will close this issue
Use absolute pathnames instead of depending on PATH #370
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use absolute pathnames instead of depending on PATH mernst/AST-Merging-Evaluation
2 participants
@mernst @benedikt-schesch