New issue
Advanced search Search tips

Issue 673400 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Mar 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 3
Type: Bug

Blocked on:
issue 673202



Sign in to add a comment

Pages seem aggressively cached

Project Member Reported by rsesek@chromium.org, Dec 12 2016

Issue description

Chrome Version: (copy from chrome://version)
OS: (e.g. Win7, OSX 10.9.5, etc...)

What steps will reproduce the problem?
(1) Use luci-milo build link (https://luci-milo.appspot.com/buildbot/tryserver.chromium.mac/mac_chromium_rel_ng/352509)
(2) Refresh the page to see how much progress it's making through various test suites
(3) Looks like progress is not being made
(4) Check actual build link (https://build.chromium.org/p/tryserver.chromium.mac/builders/mac_chromium_rel_ng/builds/352509) and see that it's further along than what luci-milo page has

It seems like the results displayed by luci-milo are either aggressively cached server-side (Cmd+Shift+R doesn't cause an update) or do not receive updates as frequently as the build links.

What is the expected result?
Results on luci-milo that more closely track real-time.

What happens instead?
Results on luci-milo seem to lag by several minutes the actual state of the build.

Please use labels and text to provide additional information.


For graphics-related bugs, please copy/paste the contents of the about:gpu
page at the end of this report.

 

Comment 1 by hinoka@chromium.org, Dec 13 2016

Blockedon: 673202
Thanks for the report.  Milo should lag behind buildbot no more than 30 seconds.  If you're seeing lags for minutes at a time, that means the buildbot process is lagging behind.  This is probably related to wider buildbot performance issues (currently being investigated)

Comment 2 by rsesek@chromium.org, Dec 14 2016

Makes sense that it could be related to the buildbot performance issue, but I definitely was seeing a lag of more than just 30 seconds.

Comment 3 by no...@chromium.org, Mar 10 2017

Status: WontFix (was: Untriaged)
There is caching Milo's buildbot build page, it reads the data straight from the datastore https://cs.chromium.org/chromium/infra/go/src/github.com/luci/luci-go/milo/appengine/buildbot/build.go?q=build+file:%5Einfra/go/src/github%5C.com/luci/luci-go/milo/appengine/buildbot/+package:%5Echromium$&l=518

Not sure if there ever was. 

Most likely there was a lag between events happening on Buildbot side and pubsub events are being sent from Buildbot to Milo

Closing because there is no caching and the root cause ( bug 673202 ) is fixed.

Comment 4 by no...@chromium.org, Mar 10 2017

s/There is caching/There is no caching/

Comment 5 by hinoka@chromium.org, Mar 10 2017

There has been a lot of fixes put in since last Dec on reporting performance.  It's expected to be about 45s behind on average, but no more than that excluding brief spikes.

Sign in to add a comment