Name | Date | Size | ||
---|---|---|---|---|
.. | 01-Oct-2018 | 103 | ||
bad-syscall/ | H | 01-Oct-2018 | 5 | |
c11-condvar/ | H | 01-Oct-2018 | 4 | |
c11-mutex/ | H | 01-Oct-2018 | 4 | |
c11-thread/ | H | 01-Oct-2018 | 4 | |
channel/ | H | 01-Oct-2018 | 4 | |
clock/ | H | 01-Oct-2018 | 4 | |
cookies/ | H | 01-Oct-2018 | 4 | |
echo/ | H | 01-Oct-2018 | 10 | |
elf-tls/ | H | 01-Oct-2018 | 4 | |
event-pair/ | H | 01-Oct-2018 | 4 | |
fifo/ | H | 01-Oct-2018 | 4 | |
futex/ | H | 01-Oct-2018 | 4 | |
handle-close/ | H | 01-Oct-2018 | 4 | |
handle-info/ | H | 01-Oct-2018 | 4 | |
handle-transfer/ | H | 01-Oct-2018 | 4 | |
handle-wait/ | H | 01-Oct-2018 | 4 | |
interrupt/ | H | 01-Oct-2018 | 3 | |
job/ | H | 01-Oct-2018 | 3 | |
main.c | H A D | 01-Oct-2018 | 3 KiB | |
memory-mapping/ | H | 01-Oct-2018 | 4 | |
object-child/ | H | 01-Oct-2018 | 4 | |
object-info/ | H | 01-Oct-2018 | 4 | |
port/ | H | 01-Oct-2018 | 4 | |
process/ | H | 01-Oct-2018 | 4 | |
profile/ | H | 01-Oct-2018 | 3 | |
pthread/ | H | 01-Oct-2018 | 4 | |
pthread-barrier/ | H | 01-Oct-2018 | 4 | |
pthread-tls/ | H | 01-Oct-2018 | 4 | |
README.md | H A D | 01-Oct-2018 | 806 | |
resource/ | H | 01-Oct-2018 | 3 | |
rules.mk | H A D | 01-Oct-2018 | 1.2 KiB | |
socket/ | H | 01-Oct-2018 | 4 | |
stack/ | H | 01-Oct-2018 | 4 | |
sync-completion/ | H | 01-Oct-2018 | 5 | |
threads/ | H | 01-Oct-2018 | 7 | |
time/ | H | 01-Oct-2018 | 4 | |
vmar/ | H | 01-Oct-2018 | 4 | |
vmo-signal/ | H | 01-Oct-2018 | 4 | |
zxr-mutex/ | H | 01-Oct-2018 | 4 |
README.md
1# utest/core 2 3The "core" tests exist for one main purpose: 4To test basic functionality when things like devmgr aren't working. 5 6If the kernel is told to run core-tests instead of devmgr, these tests 7will run without any userspace device manager, device drivers, io plumbing, 8etc. 9 10## Example usage 11 12``` 13./scripts/run-zircon-x64 -c userboot=bin/core-tests 14./scripts/run-zircon-arm64 -c userboot=bin/core-tests 15``` 16 17## Notes 18 19The tests here are for "core" functionality (channels, etc.), but 20not all "core" functionality can go here. For example, you can't 21start a process in your test with launchpad because core tests are for 22when that functionality isn't working. Core tests can't use fdio and 23launchpad uses fdio. 24 25Since these tests can't use fdio core/main.c stubs out the needed 26functions from fdio. 27