platform: disable feishu in ESP32-S3 QEMU to fix CI#73
Merged
Conversation
Feishu was enabled in the S3 QEMU defaults but CI lacks valid credentials, causing endless token retry spam. More importantly, CONFIG_RTCLAW_FEISHU_ENABLE gates out the AI boot test thread (TLS memory conflict guard), so the online CI test waiting for '[boot] AI>' always times out. Disable feishu for S3 QEMU to match C3 QEMU and unblock CI. Signed-off-by: Chao Liu <chao.liu.zevorn@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
sdkconfig.defaultshadCONFIG_RTCLAW_FEISHU_ENABLE=y, but CI has no valid feishu credentialstoken response missing tenant_access_tokenevery 10sclaw_init.c:80-81), so[boot] AI>never appears →test_ai_boot_responsetimes out after 360sTest plan
online (esp32s3-qemu)CI job passesonline (esp32c3-qemu)CI job still passes (no change)