13:53:34 RRSAgent has joined #wot-pf 13:53:34 logging to https://www.w3.org/2022/06/10-wot-pf-irc 13:57:29 meeting: WoT Testfest - Day 5 13:57:35 present+ Kaz_Ashimura 13:57:39 chair: McCool 14:01:41 ktoumura has joined #wot-pf 14:01:49 McCool has joined #wot-pf 14:01:52 present+ Michael_McCool, Elodie_Thieblin, Kunihiko_Toumura, Tomoaki_Mizushima 14:02:50 present+ Fady_Salama 14:02:54 Mizushima has joined #wot-pf 14:03:53 JKRhb has joined #wot-pf 14:04:51 present+ Ege_Korkan 14:04:59 zakim, who is on the call? 14:04:59 Present: Kaz_Ashimura, Michael_McCool, Elodie_Thieblin, Kunihiko_Toumura, Tomoaki_Mizushima, Fady_Salama, Ege_Korkan 14:05:09 present+ Jan_Romann 14:06:55 Fady has joined #wot-pf 14:09:47 scribenick: Fady 14:09:56 topic: PRs 14:10:32 PR 317 - Add manual.csv files for dart_wot 14:10:46 i/PR 317/subtopic: PR 317/ 14:10:58 -> https://github.com/w3c/wot-testing/pull/317 PR 317 - Add manual.csv files for dart_wot 14:10:59 mm: We will merge this 14:11:10 (merged) 14:11:23 subtopic: PR 344 14:11:36 -> https://github.com/w3c/wot-testing/pull/344 PR 344 - editdor addional feature tests 14:11:59 mm: need Sebastian 14:14:00 (McCool gets the latest resources from the wot-testing repo) 14:15:17 dezell has joined #wot-pf 14:15:33 present+ David_Ezell 14:15:57 (and then checks the results for dart-wot) 14:16:17 s/dart-wot/dart-wot implementation/ 14:16:25 rrsagent, make log public 14:16:31 rrsagent, draft minutes 14:16:31 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 14:17:21 i/McCool gets/topic: Latest status/ 14:18:28 (and then regenerates the TD implementation report11.html) 14:18:51 mm: I updated my script to pass anything that has 2 or more implementations 14:19:12 ... I also updated it to highlight any thing at risk as yellow 14:20:43 rrsagent, draft minutes 14:20:43 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 14:21:15 q+ 14:21:47 ... It seems that testing problems have been fixed 14:22:40 kaz: even optional features need 2 implementations 14:22:46 ... you can also see that optional assertions are now at risk even if one implementation is available 14:23:29 Ege: It is weird that vocab assertions are optional 14:23:48 s/kaz: even optional features need 2 implementations// 14:23:54 mm: The vocab itself is mandatory, but using them is optional 14:23:55 i/It is weird/kaz: even optional features need 2 implementations/ 14:24:15 present+ Sebastian_Kaebisch 14:25:01 q? 14:25:04 ack k 14:25:06 q+ 14:25:48 action: McCool to check the vocabulary assertions 14:25:58 topic: PRs (revisited) 14:26:06 subtopic: PR 344 14:26:23 -> https://github.com/w3c/wot-testing/pull/344 PR 344 - editdor addional feature tests 14:26:55 s/subtopic: PR 344/subtopic: PR 344 (revisited)/ 14:26:56 ack k 14:27:57 mm: That PR is blocked because it fails the tests 14:28:25 i/That PR/(related to the ediTDor implementation)/ 14:29:01 Ege: I did some fixing for the tm:extend assertion and maybe running the action again will fix it 14:29:13 mm: which files had problems? 14:29:52 ek: will check the detail later 14:30:12 topic: Regenerate the TD implementation report again 14:31:05 mm: I generate a file that includes all the files at risk 14:31:16 mm: would like to record who would be able to do what to cover missing results 14:31:30 ... and now I would like to look at them and record who will close which gaps 14:31:42 s/mm: would like to record who would be able to do what to cover missing results// 14:32:04 subtopic: Automatic results 14:32:08 q? 14:32:23 s/Automatic results/Automated Validation Results/ 14:33:01 td-action-names 14:33:38 sk: 1.0 feature to be covered already 14:34:00 q+ 14:34:09 mm: will doublecheck 14:34:48 kaz: we need to look into the 1.0 results in general. right? 14:34:52 mm: yeah 14:35:35 ... right now only Intel, Huawei, Panasonic and SmartThings there 14:35:42 ... missing input from Siemens 14:36:08 ... wondering if any other old results to be considered 14:36:16 (in addition to Siemens) 14:37:01 action: McCool (and somebody) to check old 1.0 results 14:37:27 mm: Sebastian, do you want to look into that? 14:37:52 ... myself will look into it but would be better to have one more reviewer 14:38:25 ... probably overlooked something 14:38:31 ack k 14:39:13 ... one issue is that Simens' result was based on node-wot and overlapped with it 14:39:51 kaz: maybe we need to have an additional flag to identify the code base *after* merging the results 14:41:17 mm: We need to think about how to count in older examples and implementations 14:41:21 action: group to consider how to deal with results from multiple implementations which are based on one specific code base 14:41:28 ack k 14:41:31 q+ Ege 14:41:33 ack E 14:42:10 q+ 14:42:25 ack k 14:42:39 ek: need to fix playground as well 14:42:47 kaz: let's think about how to deal with that later 14:42:58 s/later/later based on the action item above/ 14:43:16 rrsagent, draft minutes 14:43:16 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 14:44:28 (some errors are fixed by PR 348) 14:44:57 -> https://github.com/w3c/wot-testing/pull/348 PR 348 - fix tm:extends in Siemens TDs 14:45:29 q+ 14:46:59 sk: would suggest we record features marked as "at-risk" and continue to work on them 14:48:11 mm: working on additional capability to identify the features at-risk and list them for the TD spec 14:48:36 kaz: there is one more PR (PR 340). should we look into that? 14:48:40 mm: still working on that 14:48:48 ack k 14:49:10 q+ 14:50:29 kaz: as Sebastian also mentioned, let's identify the features at-risk at the moment, and think about how to deal with them as the next step 14:50:44 topic: Updated TD implementation report 14:51:45 (McCool regenerates the TD implementation report, report11.html) 14:53:16 kaz: should we record the features at-risk here on the minutes? 14:53:40 mm: can record the detail on a dedicated CSV file on wot-testing 14:53:43 kaz: ok 14:53:57 ... and we can add a link from these minutes to that file 14:54:23 ack k 14:54:31 rrsagent, draft minutes 14:54:31 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 14:54:48 (McCool creates a file, todo.csv) 14:56:23 q+ 14:57:06 ack k 15:00:40 q+ 15:01:42 kaz: we're getting out of time 15:01:51 ... so let's record the features at-risk now 15:02:31 ... and ask you, Sebastian, Ege and the other implementers to check the tools and results (TD and CSV) based on that (=todo.csv) 15:03:38 https://github.com/w3c/wot-thing-description/blob/main/testing/todo.csv 15:04:59 -> https://github.com/w3c/wot-thing-description/pull/1533 wot-thing-description PR 1533 - Update June 2022 impl report has been also merged 15:05:48 kaz: tx 15:06:42 ... let's continue the discussion on how to deal with the results next week 15:06:57 ek: note that we need to think about Architecture as well 15:07:24 kaz: yes, the Testfest this week was targeted only to TD and Discovery 15:07:37 ... and we need to think about how to deal with Architecture and Profile as well 15:07:45 ... let's continue the discussion next week 15:08:10 sk: before closing the call, would like to appreciate all the efforts of everybody including the tooling by Fady and Ege 15:08:13 [adjourned] 15:08:17 rrsagent, draft minutes 15:08:17 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 15:13:09 i/mm: need Seba/scribenick: kaz/ 15:13:17 i/I updated/scribenick: Fady/ 15:13:28 i/even optional/scribenick: kaz/ 15:13:41 i/It is weird/scribenick: Fady/ 15:14:00 i/which files had/scribenick: kaz/ 15:14:15 i/I generate a file/scribenick: Fady/ 15:14:28 s/I generate a file/I've generated a file/ 15:14:35 i/td-action-names/scribenick: kaz/ 15:14:48 i/We need to think about/scribenick: Fady/ 15:14:57 i/need to fix playground/scribenick: kaz/ 15:15:06 rrsagent, draft minutes 15:15:06 I have made the request to generate https://www.w3.org/2022/06/10-wot-pf-minutes.html kaz 17:44:38 JKRhb has joined #wot-pf 20:17:14 Zakim has left #wot-pf