Bug 183964 - Add a field to analysis test group indicating whether this test group needs automatical bisection.
Summary: Add a field to analysis test group indicating whether this test group needs a...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: New Bugs (show other bugs)
Version: WebKit Nightly Build
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-03-23 16:49 PDT by dewei_zhu
Modified: 2018-07-02 17:10 PDT (History)
2 users (show)

See Also:


Attachments
Patch (22.93 KB, patch)
2018-03-23 17:02 PDT, dewei_zhu
rniwa: review-
Details | Formatted Diff | Diff

Note You need to log in before you can comment on or make changes to this bug.
Description dewei_zhu 2018-03-23 16:49:50 PDT
Add a field to analysis test group indicating whether this test group needs automatical bisection.
Comment 1 dewei_zhu 2018-03-23 17:02:38 PDT
Created attachment 336443 [details]
Patch
Comment 2 Ryosuke Niwa 2018-03-26 11:29:30 PDT
Comment on attachment 336443 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=336443&action=review

> Websites/perf.webkit.org/init-database.sql:281
> +    testgroup_auto_bisect boolean NOT NULL DEFAULT FALSE,

I don't think "auto_bisect" is a good name since perf dashboard itself won't automatically bisect this range.
In general, I find that matching database schema naming with a UI facing feature is problematic.
That can lead to a very narrowly scoped database design.

I'm not even certain boolean makes sense here. I could imagine there could be multiple things
change-detection scripts may want to do with this test group like confirming, bisecting, re-testing, etc...
It seems also plausible that change detection scripts need to store some extra states / info per test group.

I really don't think we should be making this database schema change until we have UI & change detection scripts change ready.
Comment 3 dewei_zhu 2018-03-26 13:02:00 PDT
Comment on attachment 336443 [details]
Patch

View in context: https://bugs.webkit.org/attachment.cgi?id=336443&action=review

>> Websites/perf.webkit.org/init-database.sql:281
>> +    testgroup_auto_bisect boolean NOT NULL DEFAULT FALSE,
> 
> I don't think "auto_bisect" is a good name since perf dashboard itself won't automatically bisect this range.
> In general, I find that matching database schema naming with a UI facing feature is problematic.
> That can lead to a very narrowly scoped database design.
> 
> I'm not even certain boolean makes sense here. I could imagine there could be multiple things
> change-detection scripts may want to do with this test group like confirming, bisecting, re-testing, etc...
> It seems also plausible that change detection scripts need to store some extra states / info per test group.
> 
> I really don't think we should be making this database schema change until we have UI & change detection scripts change ready.

Sounds reasonable. The bisect button change is https://bugs.webkit.org/show_bug.cgi?id=183888
Comment 4 Ryosuke Niwa 2018-07-02 16:58:03 PDT
Comment on attachment 336443 [details]
Patch

Again, we shouldn't be making these database schema only changes.
The frontend & backend code logics need to come in along with the database change.
Comment 5 dewei_zhu 2018-07-02 17:10:30 PDT
I didn't work on this recently. As we discussed, this change need to be more complicated and I will include all the changes associate with schema change next time I update the patch.