Add 'test' section to README#5
Conversation
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20952925324 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
❌ CLA Signature Required@liujinye-sys Some contributors need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20952968363 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20952988500 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20953053309 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20957960718 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
2 similar comments
|
/check-cla |
|
/check-cla |
❌ CLA Signature Still Required\n\n@liujinye-sys Some contributors still need to sign the CLA:\n\n-
|
|
/check-cla |
❌ CLA Signature Still Required\n\n@liujinye-sys Some contributors still need to sign the CLA:\n\n-
|
❌ CLA Signature Required\n\n@liujinye-sys Some contributors need to sign the CLA:\n\n-
|
|
/check-cla |
❌ CLA Signature Still Required\n\n@liujinye-sys Some contributors still need to sign the CLA:\n\n-
|
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20960396177 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20960613484 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
❌ CLA Signature Required@liujinye-sys Some contributors need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20960637445 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20960680137 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
❌ CLA Signature Required@liujinye-sys Some contributors need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20960956505 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20961031672 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
❌ CLA Signature Required@liujinye-sys Some contributors need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20961032416 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
❌ CLA Signature Required@liujinye-sys Some contributors need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20961227722 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
|
/check-cla |
❌ CLA Signature Still Required@liujinye-sys Some contributors still need to sign the CLA:
Please:
📋 View detailed check results: Action Run #20961248339 💡 Tip: All contributors must sign the CLA before the PR can be merged. |
liujinye-sys
force-pushed
the
dev
branch
2 times, most recently
from
2e1fc59 to
f44bd73
Compare
1 participant
Note: Please adhere to Contributing Guidelines.
Summary
Update this section with information on why change is necessary,
what it exactly does and how, if new feature shows up, provide
references (dependencies, similar problems and solutions), etc.
Impact
Update this section, where applicable, on how change affects users,
build process, hardware, documentation, security, compatibility, etc.
Testing
Update this section with details on how did you verify the change,
what Host was used for build (OS, CPU, compiler, ..), what Target was
used for verification (arch, board:config, ..), etc. Providing build
and runtime logs from before and after change is highly appreciated.