February 2022 - Compass-ci - mailweb.openeuler.org

Re: [PATCH v4 compass-ci] data-api: add es search api
by weijihui 14 Feb '22

14 Feb '22

On Fri, Feb 11, 2022 at 06:53:02PM +0800, Wu Fengguang wrote: >>+# "cci_authorization": { >>+# "my_token": "16132550-...", >>+# "my_account": "auto-submit" >>+# } > >>+# "cci_authorization": { >>+# "my_token": "16132550-...", >>+# "my_account": "auto-submit" >>+# } > >s/cci_authorization/cci_credentials/ > ok Thanks, Jihui >Thanks, >Fengguang

1 0

Re: [PATCH v4 compass-ci] data-api: add es search api
by weijihui 14 Feb '22

14 Feb '22

On Fri, Feb 11, 2022 at 06:51:34PM +0800, Wu Fengguang wrote: >On Thu, Feb 10, 2022 at 09:25:37PM +0800, Wei Jihui wrote: >>From: Wei Jihui <weijihuiall(a)163.com> >> >>1. /data_api/es/:index/_search is es search by dsl > >>2. /data_api/es/:index/_search_by_sql is es search by sql > >建议用 > /data_api/_opendistro/_sql 但是现在用的不是这个接口，用的是https://github.com/NLPchina/elasticsearch-sql Thanks, Jihui > >:index 有可能数据重复，此时不可信。 > >因为真正起作用的是 select 语句里的from， >必需解析后得到index，再基于它做认证。 > >Thanks, >Fengguang >

1 0

Re: [meeting] stats rules
by Wu Fengguang 14 Feb '22

14 Feb '22

># stats > > global stats pattern > > *.(log|message|element): > type: string - .log 出自下面的TODO - .log 命名不够清楚，是不是改成.logfile；类似的.message .element也可以改长一点 - .xxx 后缀有很小的可能与正常id混淆，改成#logfile#或者类似明显不同寻常的后缀，区分度较好，会比较安全和明显 Thanks, Fengguang --- [TODO] virttest stats TODO1 ===== (1/1) type_specific.io-github-autotest-libvirt.libvirt_usb_hotplug_device.attach_device.one_count.storage: FAIL: failed to attach device.\nDetail: command: '/bin/virsh attach-device avocado-vt-vm1 /tmp/lkp/xml_utils_temp_7xma5yyz.xml'\nexit_status: 1\nduration: 0.029788970947265625\ninterrupted: False\npid: 30074\nencoding: 'UTF-8'\nstdout: '\n'\nstderr: "error: Failed to a... (49.09 s) ==> libvirt_usb_hotplug_device.attach_device.one_count.storage.fail: 1 (for bisect) feature3.casexxx.fail: 1 TODO2 ===== for bisect report email feature3.casexxx.message => (1/1) type_specific.io-github-autotest-libvirt.libvirt_usb_hotplug_device.attach_device.one_count.storage: FAIL: failed to attach device.\nDetail: command: '/bin/virsh attach-device avocado-vt-vm1 /tmp/lkp/xml_utils_temp_7xma5yyz.xml'\nexit_status: 1\nduration: 0.029788970947265625\ninterrupted: False\npid: 30074\nencoding: 'UTF-8'\nstdout: '\n'\nstderr: "error: Failed to a... (49.09 s) TODO3 ===== for email/web report feature3.casexxx.log => job-2020-12-08T20.08-3bf7720/job.log (in result_root/) JOB LOG : /root/avocado/job-results/job-2020-12-08T20.08-3bf7720/job.log TODO4 ===== featureXXX.result.ok => featureXXX.nr_pass featureXXX.result.all => featureXXX.nr_total featureXXX.result.rate => featureXXX.pass_rate (perhaps not that useful, since the total pass_rate looks more useful, which can only be calculated by the framework across multi-jobs) RESULTS : PASS 0 | ERROR 0 | FAIL 1 | SKIP 0 | WARN 0 | INTERRUPT 0 | CANCEL 0 => stats => libvirt_usb_hotplug_device.nr_pass: 0 (if 0, may not print this line) libvirt_usb_hotplug_device.nr_fail: 1 (for account report) libvirt_usb_hotplug_device.nr_error: 0 libvirt_usb_hotplug_device.nr_warn: 0 libvirt_usb_hotplug_device.nr_total: 1 Thanks, Fengguang

1 0

[meeting] stats rules
by Lu Weitao 14 Feb '22

14 Feb '22

# type fail 0/1 counter N perf 自然数，float text [string]/string datetime? epoch? number? is array or scalar? is kpi? is negative corelation? perf split to throughput, latency, power? # per-script definition etc/failure ~/lkp-tests/etc/event-counter-prefixes ~/lkp-tests/etc/independent-counter-prefixes 1|index-perf-all.yaml 2|index-perf.yaml 3|perf-metrics-patterns 4|perf-metrics-prefixes 5|perf-metrics-threshold.yaml are all global what if a user to add one single test case and script? best to only define it in a self maintained dir with yaml description tests/unixbench + tests/unixbench.yaml os_depends: ubuntu: unixbench input.params: # will be indexed by ES nr_task: description: #type: int # for lint and catch early typo at submit time unit: default: test: input.env: # won't be indexed by ES output.stats: score match by name by regex by prefix type: record: by regex start_time .*\.message result_root/stats.json result_root/record.json # stats global stats pattern *.(log|message|element): type: string script stats pattern buildinfo\..*: type: hash example proc-vmstat pattern nr_.*: type perf pg.*: counter xxx yyy zzz: counter etc/event-counter-prefixes:proc-vmstat.nr_promoted etc/event-counter-prefixes:proc-vmstat.nr_promote_fail etc/event-counter-prefixes:proc-vmstat.nr_promote_ratelimit etc/event-counter-prefixes:proc-vmstat.nr_promote_isolate_fail etc/event-counter-prefixes:proc-vmstat.allocstall etc/event-counter-prefixes:proc-vmstat.compact_ etc/event-counter-prefixes:proc-vmstat.htlb_buddy_alloc_ etc/event-counter-prefixes:proc-vmstat.kswapd_ etc/event-counter-prefixes:proc-vmstat.nr_dirtied etc/event-counter-prefixes:proc-vmstat.nr_vmscan_immediate_reclaim etc/event-counter-prefixes:proc-vmstat.nr_written etc/event-counter-prefixes:proc-vmstat.numa_ etc/event-counter-prefixes:proc-vmstat.pageoutrun etc/event-counter-prefixes:proc-vmstat.pg etc/event-counter-prefixes:proc-vmstat.pswp etc/event-counter-prefixes:proc-vmstat.slabs_scanned etc/event-counter-prefixes:proc-vmstat.thp_ etc/event-counter-prefixes:proc-vmstat.unevictable_pgs_ etc/event-counter-prefixes:proc-vmstat.zone_reclaim_failed problem: this is not clean namespace split log.xxx: xxx: solution1: move log out of stats? job.stats.buildinfo.hash from $(stats stdout), $script.yaml job.record.buildinfo.env from $script.record.yaml also job.stats.xxx.message: string/[] stats only has number types? # stats namespace change implement

1 0

[todo] auto submit cci-makepkg for all tests
by Cao Xueliang 14 Feb '22

14 Feb '22

# auto submit cci-makepkg before run test suite example: - job.yaml --- '#! rpmbuild.yaml': suite: rpmbuild category: functional rpmbuild: repo_addr: https://vault.centos.org/6.10/os/Source/SPackages/ed-1.1-3.3.el6.src.rpm arch: aarch64 custom_repo_name: unstable/compatible/6 mount_repo_addr: https://api.compass-ci.openeuler.org:20018/rpm/testing/openeuler-20.03-LTS-… 1/compat-centos6/standard_\$basearch/\$basearch mount_repo_name: compatible-6 docker_image: openeuler:20.03-LTS-SP1 ``` - generate cci-makepkg.yaml # detect $LKP_SRC/pkg/rpmbuild/PKGBUILD first # detect /srv/initrd/pkg/container/openeuler/aarch64/20.03-LTS-SP1/rpmbuild/latest.cgz ``` suite: cci-makepkg category: functional cci-makepkg: benchmark: rpmbuild # from rpmbuild.yaml os: # from rpmbuild.yaml os_arch: # from rpmbuild.yaml os_mount: # from rpmbuild.yaml ``` - submit cci-makepkg.yaml & rpmbuild.yaml - if cci-makepkg job success and exists latest.cgz then submit rpmbuild.yaml - if cci-makepkg job not success then echo error & no need submit rpmbuild.yaml

1 0

Re: [PATCH v3 compass-ci] data-api: add es search api
by Wu Fengguang 11 Feb '22

11 Feb '22

On Wed, Feb 09, 2022 at 09:23:20PM +0800, weijihui wrote: >On Wed, Feb 09, 2022 at 01:21:14PM +0800, Wu Fengguang wrote: >>On Tue, Feb 08, 2022 at 03:10:57PM +0800, Wei Jihui wrote: >>>From: Wei Jihui <weijihuiall(a)163.com> >>> >>>1. /data_api/es/:index/es_search is es search by dsl >> >>是这样的吧： >> >> es_search => _search > >yes > >> >>>2. /data_api/es/:index/es_search_by_sql is es search by sql >> >>我看你后面用了 >> >> >+# curl -X POST localhost:10005/data_api/es/jobs/_search_by_sql >> >>然后调用的是 >> >> >+ @client.perform_request('GET', '_nlpcn/sql', {}, search_sql) >> >>但我们应该最终调用这个吧: >> >> https://github.com/opendistro-for-elasticsearch/sql >> >> POST https://<host>:<port>/_opendistro/_sql >> { >> "query": "SELECT * FROM my-index LIMIT 50" >> } >> >>相应的API是不是相应的写成 >> >> /data_api/_opendistro/_sql > >这个接口需要安装的插件没有我们用的es版本 >目前用的这个接口 >_nlpcn/sql 可以计划下升级到 _opendistro 和与之匹配的ES。 API层面，可以先用 _opendistro 免得折腾。 >> >>>-# curl -X POST localhost:10005/es_find -H 'Content-Type: application/json' -d '{ >>>+# curl -X POST localhost:10005/data_api/es/jobs/_search -H 'Content-Type: application/json' -d '{ >>> # "query": {"size":10, "sort": [{"start_time": {"order": "desc"}}]}, >>>-# "index": "jobs", >>>-# "my_token": "16132550-...", >>>-# "my_account": "auto-submit", >>>-# "query_type": "eql" # can be omitted in this scenario >>>+# "cci_authorization": { >> >>这个貌似不错： >> >> credentials > >cci_credentials? Yes. Thanks, Fengguang

1 0

Re: [PATCH todo 1/2] add todo for docker improvement
by Luan Shengde 11 Feb '22

11 Feb '22

pls ignore this mail Thanks, Luan Shengde On Fri, Feb 11, 2022 at 05:05:52PM +0800, Luan Shengde wrote: >Signed-off-by: Luan Shengde <shdluan(a)163.com> >--- > .../todo/20220216-5d:docker-improvement.md | 35 +++++++++++++++++++ > 1 file changed, 35 insertions(+) > create mode 100644 people/LuanShengde/todo/20220216-5d:docker-improvement.md > >diff --git a/people/LuanShengde/todo/20220216-5d:docker-improvement.md b/people/LuanShengde/todo/20220216-5d:docker-improvement.md >new file mode 100644 >index 00000000..416c749d >--- /dev/null >+++ b/people/LuanShengde/todo/20220216-5d:docker-improvement.md >@@ -0,0 +1,35 @@ >+# docker improvement >+ >+## handle download failure and check dir besides /lkp and /opt >+ >+original: >+ curl_cmd: %x(curl -sS --create-dirs -o #{path}/#{name} #{url} && gzip -dc #{path}/#{name} | cpio -idu -D #{path}) >+ download cgz file and unpack it in one line >+ >+improvement: >+ curl_cmd: split download cgz file, check dir and unpack the cgz file into standalone lines. >+ system('wget -t 3 -T 20 -O #{path}/#{name} #{url} 2> /dev/null') >+ use system to call the linux command, it will retusn true/false >+ - true: execute success >+ - false: execute in failure >+ raise error if download in failure >+ >+ %x(gzip -dc path/cgz_file | cpio -idt) >+ use %x(command) can get the output of the command, extract the file list of the cgz file >+ check files from the file list and check if the file/dir is besides the /lkp or /opt >+ >+ if no files/dirs besides /lkp or /opt >+ %x(gzip -dc path/cgz_file | cpio -idu -D path) >+ >+ if exist files/dirs besides /lkp or /opt >+ save the cgz to opt >+ unpack the cgz file in container >+ >+ --- >+ maybe can ignore check the cgz file if it containers files/dirs besides /lkp or /opt >+ just unpack all the cgz file in the container >+ --- >+ >+## /usr/local/bin/busybox should be ro >+ >+## cancel mount unnecessary dir >-- >2.23.0 >

1 0

Re: [PATCH v2 compass-ci] assign-account-tool: update email content
by Luan Shengde 11 Feb '22

11 Feb '22

On Thu, Feb 10, 2022 at 09:53:48PM +0800, Wei Jihui wrote: >On Thu, Feb 10, 2022 at 03:58:43PM +0800, Luan Shengde wrote: >>From: Luan Shengde <shdluan(a)163.com> >> >>for only login with public key is allow now, update the email content. >> >>Signed-off-by: Luan Shengde <shdluan(a)163.com> >>--- >> .../assign-account/build-send-account-email.rb | 13 ++++++++++--- >> container/assign-account/build-update-email.rb | 13 +++++++++++-- >> 2 files changed, 21 insertions(+), 5 deletions(-) >> >>diff --git a/container/assign-account/build-send-account-email.rb b/container/assign-account/build-send-account-email.rb >>index 3c414041..f30de78b 100755 >>--- a/container/assign-account/build-send-account-email.rb >>+++ b/container/assign-account/build-send-account-email.rb >>@@ -16,10 +16,17 @@ def build_message(email, account_info) >> Login command: >> ssh -p #{account_info['jumper_port']} #{account_info['my_login_name']}@#{account_info['jumper_host']} >> >>- Account password: >>- #{account_info['my_password']} >>+ You can directly use the public key you offered to login the account-ver server. >> >>- You can use your pub_key to login if you have offered one. >>+ Case your private key for the public key you offered has changed and lead to login failures, you can contact our technical support staff for help: >>+ >>+ name: Zhang Dewan >>+ phone: 18969058870 >>+ email: zhangdewan1(a)compass-ci.org >>+ >>+ name: Luan Shengde >>+ phone: 15109218229 >>+ email: luanshengde(a)compass-ci.org >> >> Suggest: >> If you use the password to login, change it in time. >>diff --git a/container/assign-account/build-update-email.rb b/container/assign-account/build-update-email.rb >>index 40d6b3b3..0a298ac8 100755 >>--- a/container/assign-account/build-update-email.rb >>+++ b/container/assign-account/build-update-email.rb >>@@ -18,8 +18,17 @@ def build_update_message(email, account_info, conf_info) >> Login command: >> ssh -p #{account_info['jumper_port']} #{account_info['my_login_name']}@#{account_info['jumper_host']} >> >>- Account password: >>- #{account_info['my_password']} >>+ You can directly use the public key you offered to loging the jumper server. > > loging --> login? > > Thanks, > Jihui OK, I will fix it Thanks, Luan Shengde > > >>+ >>+ Case your private key for the public key you offered has changed and lead to login failures, you can contact our technical support staff for help: >>+ >>+ name: Zhang Dewan >>+ phone: 18969058870 >>+ email: zhangdewan1(a)compass-ci.org >>+ >>+ name: Luan Shengde >>+ phone: 15109218229 >>+ email: luanshengde(a)compass-ci.org >> >> regards >> compass-ci >>-- >>2.23.0 >>

1 0

Re: [PATCH v2 compass-ci] assign-account-tool: update email content
by weijihui 10 Feb '22

10 Feb '22

On Thu, Feb 10, 2022 at 03:58:43PM +0800, Luan Shengde wrote: >From: Luan Shengde <shdluan(a)163.com> > >for only login with public key is allow now, update the email content. > >Signed-off-by: Luan Shengde <shdluan(a)163.com> >--- > .../assign-account/build-send-account-email.rb | 13 ++++++++++--- > container/assign-account/build-update-email.rb | 13 +++++++++++-- > 2 files changed, 21 insertions(+), 5 deletions(-) > >diff --git a/container/assign-account/build-send-account-email.rb b/container/assign-account/build-send-account-email.rb >index 3c414041..f30de78b 100755 >--- a/container/assign-account/build-send-account-email.rb >+++ b/container/assign-account/build-send-account-email.rb >@@ -16,10 +16,17 @@ def build_message(email, account_info) > Login command: > ssh -p #{account_info['jumper_port']} #{account_info['my_login_name']}@#{account_info['jumper_host']} > >- Account password: >- #{account_info['my_password']} >+ You can directly use the public key you offered to login the account-ver server. > >- You can use your pub_key to login if you have offered one. >+ Case your private key for the public key you offered has changed and lead to login failures, you can contact our technical support staff for help: >+ >+ name: Zhang Dewan >+ phone: 18969058870 >+ email: zhangdewan1(a)compass-ci.org >+ >+ name: Luan Shengde >+ phone: 15109218229 >+ email: luanshengde(a)compass-ci.org > > Suggest: > If you use the password to login, change it in time. >diff --git a/container/assign-account/build-update-email.rb b/container/assign-account/build-update-email.rb >index 40d6b3b3..0a298ac8 100755 >--- a/container/assign-account/build-update-email.rb >+++ b/container/assign-account/build-update-email.rb >@@ -18,8 +18,17 @@ def build_update_message(email, account_info, conf_info) > Login command: > ssh -p #{account_info['jumper_port']} #{account_info['my_login_name']}@#{account_info['jumper_host']} > >- Account password: >- #{account_info['my_password']} >+ You can directly use the public key you offered to loging the jumper server. loging --> login? Thanks, Jihui >+ >+ Case your private key for the public key you offered has changed and lead to login failures, you can contact our technical support staff for help: >+ >+ name: Zhang Dewan >+ phone: 18969058870 >+ email: zhangdewan1(a)compass-ci.org >+ >+ name: Luan Shengde >+ phone: 15109218229 >+ email: luanshengde(a)compass-ci.org > > regards > compass-ci >-- >2.23.0 >

1 0

Re: reproducible-build TODO list
by weijihui 10 Feb '22

10 Feb '22

On Wed, Feb 09, 2022 at 10:35:20AM +0800, Lu Weitao wrote: >On Tue, Feb 08, 2022 at 08:20:37PM +0800, Wei Jihui wrote: >>On Mon, Feb 07, 2022 at 03:14:42PM +0800, Lu Weitao wrote: >>>## TODO list >>>- TODO1.1: script support set env for build env --- compass-ci jihui >> >>what should i do for this? >> > >user submit rpmbuild.yaml will with some build params like: >fs: >kernel: >reproducible_build_env: > hostname: > datetime: >rpmbuild: > new_param: > >we should make sure these params take effect in testbox no need reproducible_build_env, just write it like runtime. runtime: 1d hostname: cc datetime: bb Thanks, Jihui > > > >--------- >Thanks, >Lu Weitao > >- > >>Thanks, >>Jihui >> >> >>> >>>- TODO1.2: script record buildinfo file in testbox --- IT/compass-ci >>> - based on debian buildinfo >>> - TODO1.3: 输出用户指定的息into buildinfo? >>> new lib/buildinfo.sh --- IT >>> func1() >>> func2() >>> func3() >>> save to $result_root/buildinfo.yaml >>> >>> modify rpmbuild script to call the above funcs. --- compass-ci wangyong >>> >>>- TODO1.4: extract-stats servic 提取buildinfo --- compass-ci weitao >>> >>>- TODO2: 比较构建结果是否相同 --- compass-ci weitao >>> compass ci >>> >>> reuse data API es-find >>> compare in client side >>> >>> 格式和进一步优化: IT >>> client: ask use python? >>> >>>- TODO3: 基于已构建的job的buildinfo 重复构建 ---- IT >>> >>>- TODO4 toolset --- IT/compass-ci >>> option1: compass ci local 1-key deploy in 1VM (most simple for us) -- 暂不采纳 >>> option2: simple toolset run in native host, run only container, no VM -- 已采纳---IT >>> option3: submit self-made build container (test option2 regularly) to run remote in compass ci --compass-ci wangyong >>> >>> >>> >>>--------- >>>Thanks, >>>Lu Weitao >>>

1 0