Michael (XIAO Xufeng) f54cab62a2 ci: fix one ut issue when using Wrover-B module with newer ver of PSRAM ... The workaround for PSRAM that will occupy an SPI bus is enabled only when: 1. used on 32MBit ver 0 PSRAM. 2. work at 80MHz. The test used to only check 32MBit by the config option, but for PSRAM on Wrover-B module seems to use a newer version of 32MBit PSRAM. So it expects the workaround to be enabled, but actually not. This commit split the unit test into two parts: 1. check all SPI buses are available, for all configs except psram_hspi and psram_vspi, run on regular runners (including Wrover and Wrover-B). a hidden option is enabled so that the compiler knows it's not building psram_hspi or psram_vspi. 2. check the specified bus are acquired, for config psram_hspi and psram_vspi. This only run on special runner (legacy Wrover module).		2019-11-08 08:25:35 +00:00
..
assign-test.yml	CI: use include to split large CI config file	2019-07-03 16:59:50 +08:00
build.yml	tools: update Windows installer build script	2019-10-18 11:10:41 +02:00
check.yml	Handle deprecated values in sdkconfig.defaults	2019-10-03 10:13:42 +02:00
deploy.yml	CI: use include to split large CI config file	2019-07-03 16:59:50 +08:00
host-test.yml	Fix error code collision and CI check	2019-09-03 08:07:16 +02:00
target-test.yml	ci: fix one ut issue when using Wrover-B module with newer ver of PSRAM	2019-11-08 08:25:35 +00:00