New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Test Pilot Homepage lacks the CSS formatting #3136

Closed
SoftVision-PaulOiegas opened this Issue Dec 6, 2017 · 4 comments

Comments

Projects
None yet
4 participants
@SoftVision-PaulOiegas

SoftVision-PaulOiegas commented Dec 6, 2017

[Affected versions]:

  • Firefox 57.0.1 and above

[Affected Platforms]:

  • All Windows
  • All Mac OS
  • All Linux

[Prerequisites]:

  • Following 5 prefs have been set or added on a new profile: "extensions.legacy.enabled = true" "xpinstall.signatures.required = false" "testpilot.env = dev" "extensions.webapi.testing = true" "extensions.install.requireBuiltInCerts = false".

[Steps to reproduce]:

  1. Open Firefox browser and navigate to https://testpilot.dev.mozaws.net page.
  2. Observe how the page elements are rendered.

[Expected result]:

  • The Test Pilot Homepage is correctly rendered.

[Actual result]:

  • The Test Pilot Homepage entirely lacks the CSS formatting.

[Notes]:

  • The /experiments and other pages are correctly working.
  • Strangely, Voice Fill experiment is not displayed on the Homepage when this occurs.
  • When this occurs, the environment setup notes page is bypassed.
  • See attached screenshot:
    txp no css
@pdehaan

This comment has been minimized.

Show comment
Hide comment
@pdehaan

pdehaan Dec 6, 2017

Contributor

Here's what I see in my Firefox Nightly DevTools (and Browser Console):

firefox_test_pilot_-_dev

browser_console_-2


And here's what I see in Google Chrome's DevTools:

firefox_test_pilot_-_dev2

Contributor

pdehaan commented Dec 6, 2017

Here's what I see in my Firefox Nightly DevTools (and Browser Console):

firefox_test_pilot_-_dev

browser_console_-2


And here's what I see in Google Chrome's DevTools:

firefox_test_pilot_-_dev2

@lmorchard

This comment has been minimized.

Show comment
Hide comment
@lmorchard

lmorchard Dec 6, 2017

Member

Yeah, this sounds like the usual unresolved issue we've been having with dev deployments colliding - the HTML gets references to one set of JS & CSS with hashes in the URLs, meanwhile a different set actually deploys and so there are 404s

Member

lmorchard commented Dec 6, 2017

Yeah, this sounds like the usual unresolved issue we've been having with dev deployments colliding - the HTML gets references to one set of JS & CSS with hashes in the URLs, meanwhile a different set actually deploys and so there are 404s

@lmorchard

This comment has been minimized.

Show comment
Hide comment
@lmorchard

lmorchard Dec 6, 2017

Member

And it looks like a recent dev deploy fixed this. Expecting this will keep occurring, since we haven't been able to figure out what the cause is. We've put checks in place to wait for cache invalidation, serialize deployments, etc and nothing has solved it

Member

lmorchard commented Dec 6, 2017

And it looks like a recent dev deploy fixed this. Expecting this will keep occurring, since we haven't been able to figure out what the cause is. We've put checks in place to wait for cache invalidation, serialize deployments, etc and nothing has solved it

@lmorchard lmorchard closed this Dec 6, 2017

@SoftVision-PaulOiegas

This comment has been minimized.

Show comment
Hide comment
@SoftVision-PaulOiegas

SoftVision-PaulOiegas Dec 6, 2017

Would be helpful for us if you guys could double check at the end of your day that dev is loading properly after merges are performed on it. Otherwise we end up with 8 hours of work where we cannot test the Homepage. And that's a hell of a lost time... Especially when we are close to a new release.

SoftVision-PaulOiegas commented Dec 6, 2017

Would be helpful for us if you guys could double check at the end of your day that dev is loading properly after merges are performed on it. Otherwise we end up with 8 hours of work where we cannot test the Homepage. And that's a hell of a lost time... Especially when we are close to a new release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment