Skip to content
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

GPII-1716: Windows font-size #115

Open
wants to merge 15 commits into
base: master
Choose a base branch
from
Open

GPII-1716: Windows font-size #115

wants to merge 15 commits into from

Conversation

stegru
Copy link
Member

@stegru stegru commented Mar 9, 2017

Font-size support for windows, via the SystemParametersInfo.

The changes here are to allow the fWinIni parameter to be defined in the solutions registry.

@gpii-bot
Copy link

gpii-bot commented Mar 9, 2017

CI job failed. Please visit http://lists.gpii.net/pipermail/ci/ for more details.

1 similar comment
@gpii-bot
Copy link

CI job failed. Please visit http://lists.gpii.net/pipermail/ci/ for more details.

@stegru
Copy link
Member Author

stegru commented Mar 14, 2017

ok to test

if (typeof(flags) === "string") {
var or = flags.indexOf("&") < 0;
op = or ? "or" : "and";
flags = flags.split(/ *[&|,]+ */);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we permit comma here as well?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Don't know.

if (fluid.isArrayable(flags)) {
togo = gpii.windows.combineFlags(flags, allFlags, op);
} else {
fluid.log("windows.resolveFlags was passed an unknown type of flags");
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This should be fail

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

done

@@ -206,12 +209,16 @@ gpii.windows.spi.applySettings = function (payload) {
// Wait for sethc.exe to end before making the SPI call
gpii.windows.spi.waitForSpi()
.then(function () {
// SPIF_SENDCHANGE broadcasts several messages and has the potential to block, so call it in a child
// process.
var sendChange = (fWinIni & gpii.windows.API_constants.SpiFlags.SPIF_SENDCHANGE) ===
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems a bit more brief and equally effective to skip the === check

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree.

var or = op !== "and" && op !== "&";

var combine = or
? function (left, right) { return left | right; }
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The legendary Do IIIIIIT block!

@amb26
Copy link
Member

amb26 commented Jun 21, 2017

Can we get the CI to pass for this?

@gpii-bot
Copy link

CI job failed. Please visit http://lists.gpii.net/pipermail/ci/ for more details.

@javihernandez
Copy link
Member

ok to test

@gpii-bot
Copy link

CI job failed. Please visit http://lists.gpii.net/pipermail/ci/ for more details.

@gpii-bot
Copy link

CI job failed. Please visit http://lists.gpii.net/pipermail/ci/ for more details.

@gpii-bot
Copy link

gpii-bot commented Aug 7, 2017

CI job passed.

# Conflicts:
#	gpii/node_modules/WindowsUtilities/WindowsUtilities.js
#	package.json
@gpii-bot
Copy link

gpii-bot commented Sep 8, 2017

CI job passed: https://ci.gpii.net/job/windows-tests/261/

@gpii-bot
Copy link

CI job passed: https://ci.gpii.net/job/windows-tests/300/

@gpii-bot
Copy link

CI job passed: https://ci.gpii.net/job/windows-tests/391/

@gpii-bot
Copy link

gpii-bot commented Apr 5, 2018

CI job passed: https://ci.gpii.net/job/windows-tests/450/

@stegru
Copy link
Member Author

stegru commented Apr 13, 2018

ok to test

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/460/

@gpii-bot
Copy link

gpii-bot commented May 7, 2018

CI job failed: https://ci.gpii.net/job/windows-tests/483/

@gpii-bot
Copy link

gpii-bot commented May 7, 2018

CI job failed: https://ci.gpii.net/job/windows-tests/484/

@stegru
Copy link
Member Author

stegru commented May 7, 2018

ok to test

==> default: Mounting shared folders...
    default: /vagrant => /home/jenkins-gpii/workspace/windows-tests
Vagrant can't use the requested machine because it is locked! This
means that another Vagrant process is currently reading or modifying
the machine. Please wait for that Vagrant process to end and try
again. Details about the machine are shown below:

Name: default
Provider: virtualbox
Build step 'Execute shell' marked build as failure
Finished: FAILURE

@gpii-bot
Copy link

gpii-bot commented May 7, 2018

CI job failed: https://ci.gpii.net/job/windows-tests/485/

@stegru
Copy link
Member Author

stegru commented May 7, 2018

ok to test

�[KProgress: 90%There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["import", "/home/jenkins-gpii/.vagrant.d/boxes/inclusivedesign-VAGRANTSLASH-windows10-eval-x64-Apps/2018.03.20/virtualbox/box.ovf", "--vsys", "0", "--vmname", "windows10-eval-x64-Apps-v20180320_1525721153816_93954", "--vsys", "0", "--unit", "12", "--disk", "/home/jenkins-gpii/VirtualBox VMs/windows10-eval-x64-Apps-v20180320_1525721153816_93954/windows10-eval-x64-Apps-v20180320-disk001.vmdk"]

Stderr: 0%...10%...20%...30%...40%...50%...60%...70%...80%...90%...100%
Interpreting /home/jenkins-gpii/.vagrant.d/boxes/inclusivedesign-VAGRANTSLASH-windows10-eval-x64-Apps/2018.03.20/virtualbox/box.ovf...
OK.
0%...
Progress state: VBOX_E_FILE_ERROR
VBoxManage: error: Appliance import failed
VBoxManage: error: Could not create the imported medium '/home/jenkins-gpii/VirtualBox VMs/windows10-eval-x64-Apps-v20180320_1525721153816_93954/windows10-eval-x64-Apps-v20180320-disk001.vmdk'.
VBoxManage: error: VMDK: could not create new file '/home/jenkins-gpii/VirtualBox VMs/windows10-eval-x64-Apps-v20180320_1525721153816_93954/windows10-eval-x64-Apps-v20180320-disk001.vmdk' (VERR_ALREADY_EXISTS)
VBoxManage: error: Details: code VBOX_E_FILE_ERROR (0x80bb0004), component ApplianceWrap, interface IAppliance
VBoxManage: error: Context: "RTEXITCODE handleImportAppliance(HandlerArg*)" at line 886 of file VBoxManageAppliance.cpp
Build step 'Execute shell' marked build as failure
Finished: FAILURE

@gpii-bot
Copy link

gpii-bot commented May 7, 2018

CI job failed: https://ci.gpii.net/job/windows-tests/486/

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/545/

@stegru
Copy link
Member Author

stegru commented Jun 21, 2018

ok to test

Error occurred during logout: Timed out waiting for the SPI call to complete (see GPII-2001)

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/549/

@stegru
Copy link
Member Author

stegru commented Jun 21, 2018

ok to test

Unrelated (but slightly worrying) failure about narrator.

09:09:08.890:  jq: FAIL: Module "gpii.tests.windows.registeredAT" Test name "Testing real AT" - Message: Narrator must be running
09:09:08.890:  jq: Source:     at pok (\\vboxsvr\vagrant\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:112:15)
    at Object.assertTrue (\\vboxsvr\vagrant\node_modules\infusion\tests\test-core\jqUnit\js\jqUnit.js:145:13)
    at Array.<anonymous> (\\vboxsvr\vagrant\gpii\node_modules\registeredAT\test\testRegisteredAT.js:276:16)
    at Object.that.complete 

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/550/

@stegru
Copy link
Member Author

stegru commented Jun 21, 2018

2nd time today GPII-2001 has affected a test. Unable to repro on a local VM.

12:39:01.678:  jq: FAIL: Module "gpii.tests.acceptance.windows.builtIn.config tests" Test name "Testing os_common - magnifier and keyboard both running on startup" - Message: Successful login message returned {"isError":true,"message":"Error occurred during login:
 Timed out waiting for the SPI call to complete (see GPII-2001)"}

ok to test

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/551/

@stegru
Copy link
Member Author

stegru commented Jun 22, 2018

ok to test

@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/552/

A slower poll caused the WM_SETTINGCHANGE(?) broadcast from SPI_SETNONCLIENTMETRICS to delay.
@gpii-bot
Copy link

CI job failed: https://ci.gpii.net/job/windows-tests/553/

@stegru
Copy link
Member Author

stegru commented Jun 24, 2018

ok to test

npm ERR! code EINTEGRITY
npm ERR! sha1-0Ng2s0OqbbiMDez+rnHmJ11BQg4= integrity checksum failed when using sha1: wanted sha1-0Ng2s0OqbbiMDez+rnHmJ11BQg4= but got sha1-Rwfn1jU+Ym4KaswUYEmObrJPYYk=. (8026857 bytes)

npm ERR! A complete log of this run can be found in:
npm ERR!     C:\Users\vagrant\AppData\Roaming\npm-cache\_logs\2018-06-24T15_48_39_592Z-debug.log
Installation process returned error code: 1
At C:\tmp\Provisioning.psm1:44 char:5
+     throw "Installation process returned error code: $($exitCode)"
+     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : OperationStopped: (Installation pr...d error code: 1:String) [], RuntimeException
    + FullyQualifiedErrorId : Installation process returned error code: 1

Build step 'Execute shell' marked build as failure
Finished: FAILURE

@gpii-bot
Copy link

CI job passed: https://ci.gpii.net/job/windows-tests/554/

@stegru
Copy link
Member Author

stegru commented Jun 24, 2018

ok to test - again, to ensure it wasn't a fluke.

@gpii-bot
Copy link

CI job passed: https://ci.gpii.net/job/windows-tests/555/

@amb26
Copy link
Member

amb26 commented Oct 4, 2018

Shall we dust this one off? It looks harmless enough

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants