-
Notifications
You must be signed in to change notification settings - Fork 264
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
i#2051: in frontend, check for execute not read of DR root dir #2389
i#2051: in frontend, check for execute not read of DR root dir #2389
Conversation
Adds a new static function file_is_executable in frontend.c Fixes DynamoRIO#2051
Thank you @jwysowski for the PR! LGTM! |
Perhaps, @derekbruening could also take a look since he raised the issue and maybe has an alternative fix in mind? |
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.
LGTM. Thank you for the patch!
Hmm, so why aren't the GA CI jobs running? B/c this is a PR from a forked repo? I thought the yaml had the right triggers for that and we even tested it on the DR repo. |
@abhinav92003 any ideas? This repo has the same triggers as the DR repo workflows:
|
DynamoRIO CI trigger for fork repo PRs can be seen in dynamorio/PR#4634. I tried doing it again in dynamorio/PR#4771, and it still works. Though let me try syncing my forked repo to latest DR and re-try. |
Huh, I wonder if there's sthg different in drmemory repo: though the .yml looks identical. There aren't any other settings beyond the .yml right (and what branches are marked as required)? I can do a test try for drmemory repo later today. |
My fork test for drmemory repo is running the tests: #2390. |
This seems relevant: https://github.community/t/run-a-github-action-on-pull-request-for-pr-opened-from-a-forked-repo/16054 Particularly,
|
@jwysowski On the |
Actions weren't enabled in my forked repository. |
After enabling them, please re-trigger CI on this branch. The way to do that would probably be either using the |
Ok, now everything is fine |
@jwysowski Thanks for the path. @abhinav92003 Thank you for investigating the issue regarding the CI. |
Adds a new static function file_is_executable in frontend.c
Fixes #2051