-
Notifications
You must be signed in to change notification settings - Fork 31
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
[hermit][open-source] Add an extremely basic test script #25
base: main
Are you sure you want to change the base?
Conversation
Summary: While we wait to port our full buck testing setup to the OSS build, it's best to get at least a few integration tests running. This diff uses a bash script for the purpose, though the next step would be to replace it with Rust code, possibly using libtest directly. Test Plan: Reviewers: Subscribers: Tasks: Tags:
Looks like perf counters are not enabled on the hosted Github Actions Runners. There is a way we can host our own or can try checking out Circle Ci too |
Well, that sounds more involved. In the short term we could just disable RCB counters for these basic "hermit strict" tests. I don't think any require them. |
Summary: The VMs running github actions do not expose perf counters, as seen here: https://github.com/facebookexperimental/hermit/actions/runs/3560943420/jobs/5981398423 WARNING: --preemption-timout requires hardware perf counters which is not supported on this host, resetting preemption-timeout to 0 Therefore, we run only a limited subset of tests under hermit run *without* RCB-based preemption of threads (i.e. busy-wait breaking). Test Plan: Reviewers: Subscribers: Tasks: Tags:
@rrnewton has imported this pull request. If you are a Meta employee, you can view this diff on Phabricator. |
@rrnewton has updated the pull request. You must reimport the pull request before landing. |
Summary:
While we wait to port our full buck testing setup to the OSS build, it's best to get at least a few integration tests running.
This diff uses a bash script for the purpose, though the next step would be to replace it with Rust code, possibly using libtest directly.
Test Plan:
Reviewers:
Subscribers:
Tasks:
Tags: