This repository has been archived by the owner on Nov 2, 2021. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 19
W46 2017 11 13 2017 11 18 DevOp Status
Yu Chun Yen (Mark) edited this page Nov 21, 2017
·
1 revision
- Daily Build:
- Issue 1: Disk full
- Checked and cleaned data before 11/10
- Issue 1: Disk full
- Dashboard:
- Issue 1: New dashboard online
- New Dashboard's curves fluctuation:
- Window7
- Amazon - Type in search field
- Output images on win7-asus-r-6 are correct.
- The input latency for Chrome and Firefox range from 11s to 33s (about 3 pictures). However, the input latency for Chrome ranges mostly around 11s to 22s. On the other hand, the input latency for Firefox ranges mostly around 22s to 33s. Therefore, two lines crossed in the range of 11s to 33s depending on the numbers of 11s/33s points.
- Facebook - Type in composer box
- Output images on win7-asus-r-6 are correct.
- The medium of input latency for Chrome and Firefox both increased 11s from 11/13 to 11/14. Since Firefox and Chrome both slow down, this phenomenon might cause by Facebook.
- Amazon - Type in search field
- Window10
- Amazon - Select search suggestion
- Output images on win10-hp-r1-3 are correct.
- The range of input latency is 5s to 22s (and sometimes 33s) for Firefox. However, there is no point higher than 11s today. This might cause the curve of Firefox to drop. On the other hands, Chrome has a very stable performance averaging at around 5s.
- Facebook - Click open chat tab emoji
- Output images on win10-hp-r1-5 and win10-hp-r1-12 are correct.
- Chrome's medium somehow drops from 44s to 11s. There are total six measurements. Five are below 11s and one is 221s. In my opinion, our testing is correct; however, there are only six measurements for each build. This causes the medium curves to be affected more easily.
- Google Search - Select search suggestion
- Output images on win10-hp-r1-5 are correct.
- Firefox's medium somehow increased from 22s to 33s (one picture). The fluctuation of curves become more obvious because the graph changed to show by build instead of by date.
- Youtube - Select search suggestion
- Output images on win10-hp-r1-9 are correct.
- The fluctuation of curves become more obvious because the graph changed to show by build instead of by date.
- Amazon - Select search suggestion
- Summary:
- The previous dashboard displayed the data by date; however, new dashboard displayed by Firefox's build. The previous dashboard had 6 ~ 20 testing result in one column, but now less than 6. These two changes caused the fluctuation of curves to be more sensitive since now we only have 6 points in one column.
- Window7
- Google slide cases - icon change:
- Sol: Updated new reference icon.