NameDateSize

..01-Oct-2018103

bad-syscall/H01-Oct-20185

c11-condvar/H01-Oct-20184

c11-mutex/H01-Oct-20184

c11-thread/H01-Oct-20184

channel/H01-Oct-20184

clock/H01-Oct-20184

cookies/H01-Oct-20184

echo/H01-Oct-201810

elf-tls/H01-Oct-20184

event-pair/H01-Oct-20184

fifo/H01-Oct-20184

futex/H01-Oct-20184

handle-close/H01-Oct-20184

handle-info/H01-Oct-20184

handle-transfer/H01-Oct-20184

handle-wait/H01-Oct-20184

interrupt/H01-Oct-20183

job/H01-Oct-20183

main.cH A D01-Oct-20183 KiB

memory-mapping/H01-Oct-20184

object-child/H01-Oct-20184

object-info/H01-Oct-20184

port/H01-Oct-20184

process/H01-Oct-20184

profile/H01-Oct-20183

pthread/H01-Oct-20184

pthread-barrier/H01-Oct-20184

pthread-tls/H01-Oct-20184

README.mdH A D01-Oct-2018806

resource/H01-Oct-20183

rules.mkH A D01-Oct-20181.2 KiB

socket/H01-Oct-20184

stack/H01-Oct-20184

sync-completion/H01-Oct-20185

threads/H01-Oct-20187

time/H01-Oct-20184

vmar/H01-Oct-20184

vmo-signal/H01-Oct-20184

zxr-mutex/H01-Oct-20184

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