Summary: | OSBuildFetcher should respect maxRevision while finding OS builds to report. | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | dewei_zhu | ||||
Component: | New Bugs | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | NEW --- | ||||||
Severity: | Normal | CC: | dewei_zhu, rniwa | ||||
Priority: | P2 | ||||||
Version: | WebKit Nightly Build | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
Attachments: |
|
Description
dewei_zhu
2018-05-23 16:26:38 PDT
Created attachment 341148 [details]
Patch
Comment on attachment 341148 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=341148&action=review > Websites/perf.webkit.org/tools/js/os-build-fetcher.js:101 > - .filter((commit) => commit['order'] > minOrder); > + .filter((commit) => commit['order'] > minOrder && commit['order'] < maxOrder); It seems that minOrder & maxOrder should be inclusive. Comment on attachment 341148 [details] Patch View in context: https://bugs.webkit.org/attachment.cgi?id=341148&action=review >> Websites/perf.webkit.org/tools/js/os-build-fetcher.js:101 >> + .filter((commit) => commit['order'] > minOrder && commit['order'] < maxOrder); > > It seems that minOrder & maxOrder should be inclusive. For minOrder, it should be exclusive as it is from 'last-reported' api and we don't want to report 'last-reported' again. For maxOrder, it could be both either way. |