AWSY 'Windows 10 64bit' not running since August 1st 2021?

[HenkPoley]

https://awsy.netlify.app/win10/memory/overview?numDays=60

Probably also means nobody is looking at them 😅

[Archaeopteryx]

The migration of AWSY to Azure broke this. @jmaher @MasterWayZ Can you take a look if

firefox-performance-dashboards/src/awsy.js

Line 114 in 02c1870

platforms: ['windows10-64-shippable'],

needs update with the 2004 added to the platform name?

[davehunt]

The migration of AWSY to Azure broke this. @jmaher @MasterWayZ Can you take a look if

firefox-performance-dashboards/src/awsy.js

Line 114 in 02c1870

platforms: ['windows10-64-shippable'],

needs update with the 2004 added to the platform name?

It looks like with 2004 in the platform name we have data from July 31 to August 19. After that, only Fission data is available. See https://treeherder.mozilla.org/perfherder/graphs?highlightAlerts=1&highlightChangelogData=1&series=autoland,1959131,1,4&series=autoland,1959123,1,4&series=autoland,3773866,1,4&series=autoland,3806455,1,4&timerange=5184000

[davehunt]

Probably also means nobody is looking at them 😅

We monitor these results and open regressions using Perfherder. It's quite possible that nobody is looking at AWFY, but this doesn't mean we've taken our eye off the results.

[jmaher]

regarding windows 10 x64 (from looking at mozilla-central)- July 31st - We switched to a new version of windows (v.1803 -> v.2004): https://hg.mozilla.org/mozilla-central/rev/ef5b594ec1af0ac78cefebf80130addb08019a6f August 2nd - We stopped running the 'sy' tp5 test: https://hg.mozilla.org/mozilla-central/rev/6894193a38f13821498470bb3d83efb8de5c52ba August 6th - We ran 'ab' in fission (now all tests run in both normal and fission): https://hg.mozilla.org/mozilla-central/rev/11db8586ad4296efca00ab8c1a30e9dc3b3f91c9 * NOTE: here is where we scheduled SY(ab) on m-c only and not on autoland Those are all the scheduling changes I see, is there anything we should adjust from an in-tree scheduling/reporting point of view? For the dashboard, I assume you just need to change the platform name of windows to include 2004 - this is a trend that we are trying to include the OS version in the platform name.

…

-Joel

On Tue, Aug 31, 2021 at 9:25 AM Dave Hunt ***@***.***> wrote: Probably also means nobody is looking at them 😅 We monitor these results and open regressions using Perfherder. It's quite possible that nobody is looking at AWFY, but this doesn't mean we've taken our eye off the results. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#433 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAAPI7CGTRBRG3NUAKET5T3T7T7BNANCNFSM5CLFTVQA> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[davehunt]

I've opened #440, which adds '2004' to the platform names on Windows, defaults to WebRender, and removes tp5 results. Looking at the deploy preview the only remaining discrepency is the base tests show no non-Fission results on autoland (these are now only running on mozilla-central). @jmaher can we restore these?

[jmaher]

we would need to follow up in the original bug that changed the behavior (https://bugzilla.mozilla.org/show_bug.cgi?id=1714585), I don't see any reason not to do this from a capacity point of view.

[davehunt]

we would need to follow up in the original bug that changed the behavior (https://bugzilla.mozilla.org/show_bug.cgi?id=1714585), I don't see any reason not to do this from a capacity point of view.

I've opened https://bugzilla.mozilla.org/show_bug.cgi?id=1729338.

[davehunt]

I believe this is resolved.