John Hopkins has made some changes to Windows build platform in order to facilitate maintenance and deployment with Microsoft's GPO tools (bug 918414). These builders are currently only building on the cedar branch, but we'd like to start using them everywhere once we've verified that the builds generated under this new configuration are still valid. Can we please ask QA to perform whatever smoketests or functional tests they think are appropriate on the Windows builds from the cedar branch so we can validate or new builder configuration? https://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-cedar/

The new win64-rev2 Windows build platform is now being used to build all project branches (except inbound). Given that, I'll select an fx-team branch build for testing and link to it here (selecting fx-team so as not to include Releng/ATeam work in progress that's on cedar).

Please smoke test the Windows builds at these locations: http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-win32/1382011034/ http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-win32-pgo/1382014851/ http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-win32-debug/1382011034/ And, because fx-team does not have nightlies enabled, also the Windows builds from 'cedar' here: ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-cedar/ ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-cedar-l10n/

I think a full pass with our Mozmill automation and maybe a quick manual spotcheck would be sufficient. Henrik, Tracy, what do you think?

John, how soon do you need results? QA can definitely test these builds but given current priorities it might take a couple of weeks.

By the way, I think it would have been sufficient to just add qawanted to bug 918414 and cc me as QA Contact. Let's continue the requested work here in this bug, but keep this in mind for future reference. Thanks.

(In reply to John Hopkins (:jhopkins) from comment #2) > Please smoke test the Windows builds at these locations: > > http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team- > win32/1382011034/ > http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team- > win32-pgo/1382014851/ > http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team- > win32-debug/1382011034/ On which Windows versions you want to have this tested? We have XP, Vista, 7 (32/64), 8 (32/64), and 8.1 (32/64). > And, because fx-team does not have nightlies enabled, also the Windows > builds from 'cedar' here: > > ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-cedar/ > ftp://ftp.mozilla.org/pub/mozilla.org/firefox/nightly/latest-cedar-l10n/ Sure. No problem.

> John, how soon do you need results? I was hoping to have test results in the next week or less to give us ample "soak time" on try/central/inbound before moving to aurora/beta/release/esr and getting to beta earlier in the next beta cycle (merge day Oct. 28). > On which Windows versions you want to have this tested? Windows XP, 7, and 8. > I think a full pass with our Mozmill automation and maybe a quick manual spotcheck would be sufficient. I agree.

Coop, essentially we just want make sure these builds don't fall over, correct? A Mozmill run would cover the bulk of that. But we should probably do a manual check of the installers.

(In reply to [:tracy] Tracy Walker - QA Mentor from comment #8) > Coop, essentially we just want make sure these builds don't fall over, > correct? Right. jhopkins should have more specific detail if required.

Tracy: we want a sanity check that the new Windows build machine image hasn't introduced problems with the build (for example, some sort of binary compatibility problem, linking issue, etc.).

:whimboo is running mozmill tests and :tracy is doing manual spot checks. tracy's testing will be done today.

(In reply to John Hopkins (:jhopkins) from comment #11) > :whimboo is running mozmill tests and :tracy is doing manual spot checks. > tracy's testing will be done today. Was there something specific you needed from me or was this an erroneous need-info request?

Apologies - that needinfo was in error.

I wanted to run those tests now but sadly I run into issues by triggering those jobs. As of now we cannot run tests for project branches! Sorry for that. It will even not work for manually triggered ondemand tests. Given that we highly want this feature so we could also test Australis builds soon, I filed the following issue: https://github.com/mozilla/mozmill-ci/issues/337 Tracy, what would be left to test here?

Quick install and sanity check on Win XP (old hardware): fx-team-win32: PASS fx-team-win32-pgo: PASS fx-team-win32-debug: FAIL - The application failed to start because MSVCR100D.dll was not found latest-cedar: PASS latest-cedar-l10n(es-ES): PASS Win 7 (VM): fx-team-win32: PASS fx-team-win32-pgo: PASS fx-team-win32-debug: FAIL - The application failed to start because MSVCR100D.dll is missing from your computer latest-cedar: PASS latest-cedar-l10n(es-ES): PASS Win 8 (Surface Pro): fx-team-win32: PASS fx-team-win32-pgo: PASS fx-team-win32-debug: FAIL latest-cedar: PASS latest-cedar-l10n(de): PASS From irc discussion, I believe these spot checks will suffice.

for Win 8 fx-team-win32-debug: FAIL messages on attempt to start the Nightly: Server execution failed (OK) clicked Server execution failed (OK) clicked The item you selected is unavailable. It might have been moved, renamed or removed. Do you want to remove it from the list? (Yes) (No) clicked No Server execution failed (OK) clicked Server execution failed (OK) clicked Server execution failed (OK) clicked no more messages.

MSVCR100D.dll is a debug version of MSVCR100.dll. Debug dll's are non-restributable[1] so I believe it makes sense that the dll is missing on a machine without Visual Studio. I reproduced the debug build runtime error on a local Windows 7 VM and also reproduced on an older September 14 fx-team debug build[2] which was created before fx-team was switched to use the new build machine image, therefore the missing dll error is not specific to the new build machine image. [1] http://msdn.microsoft.com/en-us/library/vstudio/aa985618.aspx [2] http://ftp.mozilla.org/pub/mozilla.org/firefox/tinderbox-builds/fx-team-win32-debug/1379121786/

Win 7 (VM): fx-team-win32-debug: PASS Tracy - Is this enough, or do you still need XP covered also?

(In reply to John Hopkins (:jhopkins) from comment #17) > MSVCR100D.dll is a debug version of MSVCR100.dll. Debug dll's are > non-restributable[1] so I believe it makes sense that the dll is missing on > a machine without Visual Studio. Right. Please also see bug 711036 which has still not being fixed.

(In reply to Matt Wobensmith from comment #18) > Win 7 (VM): > fx-team-win32-debug: PASS > > > Tracy - Is this enough, or do you still need XP covered also? I'm assuming you have a debug environment to get the PASS result. So that's fine, Matt. Thank you

Confirmed with :tracy in IRC that we're all done here; Having the correct debug environment solved the issues.

Yes, good to go. Sorry I didn't make that clear in previous comment

jhopkins, are automated tests still necessary here? Sorry, that we weren't able yet to run them through Mozmill. But support for project branches in our CI hasn't been landed yet, but it will go to production this week. If further tests are needed here please let me know. Thanks.