fine, I don't mean CI failed due to this PR 馃槀 just saw after PR merged, CI down.

_Originally posted by @juzhiyuan in https://github.com/apache/apisix-dashboard/issues/1396#issuecomment-770201476_
FYI, this failure began since this morning, and 100% reproducible.
I just ran the local test file balancer_ test.go There is no problem with it. This problem occurred this morning, making PR CI unable to pass. I also implemented 'go test -v', and there is no problem.
In addition, in the development process, I also feel that there are many CI test cases, and the error information is very vague. When there are errors in the test cases, it also makes it more difficult for us to locate the problem. Of course, it takes a lot of time to improve this thing.
@juzhiyuan Hi,PR #1395 has fixed the problem. The reason for the problem is apisix has modified luajit. @nic-chen has fixed the problem.
@juzhiyuan Hi,PR #1395 has fixed the problem. The reason for the problem is apisix has modified luajit. @nic-chen has fixed the problem.
@Jaycean yep, while we would better see the CI result triggered by https://github.com/apache/apisix-dashboard/commit/94d952f9a43a9d6507b2966b58791f789e5b74a6 push event before close this issue.
https://github.com/apache/apisix-dashboard/runs/1804604649#step:4:703
failed due to luasec.
https://github.com/apache/apisix-dashboard/runs/1804604649#step:4:703
failed due to luasec.
@juzhiyuan yep, this may be caused by the lua path, related to https://github.com/apache/apisix/pull/3335 authored by @fukiki . We are trying to fix this. 馃槃
@juzhiyuan Hi,The problem has been solved. Since APISIX has modified Luajit to cause dependency environment problems, the dockfile has been modified to fix it. As mentioned in PR, pulling the dockerfile file of remote apifix should open a new issue discussion.This issue can be closed.
thanks @Jaycean