| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
fix(gate): align session and object id test expectations Signed-off-by: mhsong2 <songminhui2@huawei.com> | 10 天前 | |
fisrt commit init code | 8 个月前 | |
fix(build): complete fixes for brpc/gflags adaptation + remove deprecated tests Fixes for datasystem PR #1122 (brpc dual-mode) integration: 1. bazel/datasystem_sdk.bzl: add libprotoc.so.25.5.0 to cc_library srcs. 2. api/java/BUILD.bazel: - Use real filename libgflags.so.2.2.2 in LIB_REQUIRED. - Add libprotoc.so.25.5.0 to LIB_REQUIRED. 3. api/java/.../jni/LoadUtil.java: - Add libgflags.so.2.2.2 and libprotoc.so.25.5.0 to EXTRACT_ONLY_LIBS. - Add libgflags.so.2.2.2 to SYMLINK_MAP. - Add libprotoc.so.25.5.0 to LOADING_SEQUENCE. 4. test: remove all deprecated MSetTx test cases (C++ 9 + Python 2 + Java 4 + Go 2). Signed-off-by: OuGongChang <ougongchang@huawei.com> | 11 天前 | |
test(sandbox): Prove off-cluster yrcli paths from built wheels Off-cluster verification was easy to run with a stale yrcli or the wrong Python interpreter when PATH, conda, and system Python all provided different entrypoints. Make the verification scripts create a clean uv venv from the freshly built output wheels by default, then run pytest and yrcli through that interpreter. The Docker AIO image build also needs the k8s control-plane start scripts staged under output before the build context is assembled, so the verification script can rebuild from a clean tree. FaaS coverage now bootstraps the required Python language runtime before deploying a user function, keeps plain-HTTP Docker AIO tests from inheriting HTTPS-only YR_INSECURE settings, and verifies deploy/query/invoke/delete instead of skipping unavailable functions. The ObjectRef and instance-argument off-cluster cases stay in the suite because Docker AIO verification now proves they are supported. FunctionName now preserves single-segment system runtime functions such as 0-system-faasExecutorPython3.10 instead of formatting them as None@None. Function API URLs intentionally keep the existing raw path construction because the frontend routes expect the current function-name shape. Constraint: Verification must exercise the generated wheels instead of the source tree or a preexisting yrcli executable. Rejected: Rely on PATH discovery for yrcli | it can pick a stale executable with a broken shebang or mismatched Python. Rejected: Quote function names in CLI URLs | existing frontend routes consume raw function path segments, and function names do not need quote escaping here. Confidence: high Scope-risk: moderate Directive: Keep off-cluster verification pinned to the freshly built wheels unless intentionally testing source-tree imports. Tested: docker exec -u "1000:1000" -e HOME=/home/wyc compile bash -lc "cd /home/wyc/code/sandbox && bash build.sh -P -p python3.10 -j 8" Tested: YR_ENABLE_TLS=false YR_LOG_LEVEL=INFO YR_OFF_CLUSTER_TEST_TIMEOUT=900 bash test/st/run_off_cluster_test.sh -a 127.0.0.1:38888 -p /usr/bin/python3.10 -- -q -rs Tested: python3 -m py_compile api/python/yr/cli/scripts.py test/st/python/test_off_cluster.py Tested: /tmp/yr-offcluster-venv/bin/python -m pytest -q api/python/yr/tests/test_cli_scripts.py Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 1 个月前 | |
sync code | 7 个月前 | |
fix(st): verify reverse tunnel from sandbox Signed-off-by: mhsong2 <songminhui2@huawei.com> | 10 天前 | |
fix(ci): support runtime manager packaging Signed-off-by: mhsong2 <songminhui2@huawei.com> | 2 天前 | |
ci(sandbox): Use downloaded wheels for k8s smoke venv Buildkite K8S smoke downloads the release and SDK wheels into artifacts/release, but the shared off-cluster runner defaulted to output. After switching the runner to create a uv venv by default, the K8S job failed before tests started because output/openyuanrong_sdk*.whl does not exist in that job workspace. Allow the off-cluster runner to take YR_OFF_CLUSTER_WHEEL_DIR and point the K8S smoke step at its downloaded release artifacts so the same uv-venv path can work both locally and in Buildkite. Constraint: Buildkite K8S smoke consumes artifacts from previous steps instead of a local output directory. Rejected: Pass --no-uv-venv from the K8S smoke step | it would bypass the new clean-venv verification path and keep duplicate install behavior. Confidence: high Scope-risk: narrow Directive: Keep CI smoke wheel lookup explicit when the wheels come from Buildkite artifacts rather than local build output. Tested: bash -n test/st/run_off_cluster_test.sh .buildkite/test_sandbox_k8s.sh Tested: git diff --check Tested: YR_OFF_CLUSTER_WHEEL_DIR=<temp wheel dir> YR_ENABLE_TLS=false YR_LOG_LEVEL=INFO YR_OFF_CLUSTER_TEST_TIMEOUT=180 bash test/st/run_off_cluster_test.sh -a 127.0.0.1:38888 -p /usr/bin/python3.10 -- -q -k test_get_empty_list -rs Signed-off-by: yuchaow <wangyuchao12@huawei.com> | 1 个月前 | |
fisrt commit init code | 8 个月前 | |
fix(ci): support runtime manager packaging Signed-off-by: mhsong2 <songminhui2@huawei.com> | 2 天前 | |
fisrt commit init code | 8 个月前 |
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
| 10 天前 | ||
| 8 个月前 | ||
| 11 天前 | ||
| 1 个月前 | ||
| 7 个月前 | ||
| 10 天前 | ||
| 2 天前 | ||
| 1 个月前 | ||
| 8 个月前 | ||
| 2 天前 | ||
| 8 个月前 |