You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I build pegasus through command ./run.sh build -c --test, and try to run pegasus function test through command ./run.sh test -m pegasus_function_test. When the test run not-on-travis tests, I found that function test can not support control commands, such as clear_onebox etc, the error is just like:
Note: Google Test filter = recovery_test.*
[==========] Running 1 test from 1 test case.
[----------] Global test environment set-up.
[----------] 1 test from recovery_test
[ RUN ] recovery_test.recovery
============
start global_env()
meta1 pid: 0
meta1 dir:
project root: .
working dir: = true, partitioned = false, ...
D2022-07-25 14:58:11.605 (1658732291605899729 9335) unknown.io-thrd.09335: get ip address from network interface(enp0s31f6), addr(10.231.57.161), input interface("")
get ip:
Error: unknow option "clear_onebox"
cp: 无法获取'src/server/config.min.ini' 的文件状态(stat): 没有那个文件或目录
sed: 无法读取 config-server-test-recovery.ini: 没有那个文件或目录
sed: 无法读取 config-server-test-recovery.ini: 没有那个文件或目录
sed: 无法读取 config-server-test-recovery.ini: 没有那个文件或目录
sed: 无法读取 config-server-test-recovery.ini: 没有那个文件或目录
Error: unknow option "start_onebox"
......
It seems that there are something wrong with global_env initialization, I revert master for an old version and rerun the test, global_env is just like:
I build pegasus through command
./run.sh build -c --test
, and try to run pegasus function test through command./run.sh test -m pegasus_function_test
. When the test run not-on-travis tests, I found that function test can not support control commands, such as clear_onebox etc, the error is just like:It seems that there are something wrong with
global_env
initialization, I revert master for an old version and rerun the test, global_env is just like:I compare the master and old version, guess it may be caused by #1062, hoping it to be fixed.
The text was updated successfully, but these errors were encountered: