simon28li
simon28li
> I would recommend updating to GCC 10.3 as its replacing 10.2. There could be some bugs in the version. Its so bad,I still reported the same error when I...
@skoren @Brent-Saylor-Canopy Hi，I also encountered the same problem on the arm machine. It is a pity that I do not have relevant development experience. Will I consider a plan to...
> Just tested 1.5.1. `invasive` still is failing. Here is the result: I have the same problem, but the specific error information is inconsistent. error msg 1: worktree::config.. 1: worktree::merge......
1.16.1: pytest fails in `tests/test_sentry.py::TestSentry::test_failure_capture` and pytest warnings
hi, when I was testing version 1.6.2 recently, the same use case also failed, but the error message was not consistent. What is the reason for this? The error message...
@dang I encountered the same problem in version 4.0. I observed that this test file has not been updated for a long time. Is it out of date and not...
> vearch-startup-all.log 没找到这个文件，是在什么位置？ ``` [root@simon28li bin]# tree . ├── datas │ ├── member │ │ ├── snap │ │ │ └── db │ │ └── wal │ │ ├── 0.tmp...
另外，在执行测试的时候 启动服务的终端会报这个错 ``` [root@simon28li bin]# ./vearch -conf ../../config/config.toml all 2024/12/13 10:21:31 server.go:184: INFO : server pid:3234392 2024/12/13 10:22:33 client.go:764: ERROR: rpcx: client protocol error:wrong magic number: 72 2024/12/13 10:22:33 client.go:764:...
> 看看panic和error日志里面的内容，贴一下吧 ``` [root@simon28li logs]# cat ALL.ERROR.log ERROR 2024-12-13 10:43:59,273 rpc_client.go:130 call StatsHandlerExecute err: wrong magic number: 72 ERROR 2024-12-13 10:43:59,274 rpc_client.go:130 call StatsHandlerExecute err: wrong magic number: 72 ERROR...
Hi, is there any progress on this issue? I've had this problem, but it's not on every machine. Is it caused by environmental issues?
> > Looks like the library unit test got broken when we actually implemented parsers for xfs in [257394e](https://github.com/linux-test-project/ltp/commit/257394e4e356f5e9aad37715370a0fc5e3dc20bf). > > +1 good catch! > > > [@pevik](https://github.com/pevik) I suppose...