You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The continuous builds on Windows are running half an hour apart, so this does not reproduce on the automatic builds. However, Windows builds are running on the same physical machine.
It has happened to me both yesterday, and today, that I triggered x64 and ia32 builds at the same time. The following test has broken either the 32 bit or the 64 bit builds:
2018-01-31T09:48:30.0106346Z 3867 passing (28s)
2018-01-31T09:48:30.0106346Z 1 failing
2018-01-31T09:48:30.0106346Z
2018-01-31T09:48:30.0116333Z 1) Keytar loads and is functional:
2018-01-31T09:48:30.0116333Z AssertionError: null == 'bar'
2018-01-31T09:48:30.0116333Z at Object.<anonymous> (file:///D:/work/agent2/1/s/out-build/vs/platform/credentials/test/node/keytar.test.js:64:32)
2018-01-31T09:48:30.0116333Z at step (file:///D:/work/agent2/1/s/out-build/vs/platform/credentials/test/node/keytar.test.js:31:23)
2018-01-31T09:48:30.0116333Z at Object.next (file:///D:/work/agent2/1/s/out-build/vs/platform/credentials/test/node/keytar.test.js:12:53)
2018-01-31T09:48:30.0116333Z at fulfilled (file:///D:/work/agent2/1/s/out-build/vs/platform/credentials/test/node/keytar.test.js:3:58)
2018-01-31T09:48:30.0116333Z at <anonymous>
After a brief discussion with @joaomoreno, the working theory is that these tests share the same underlying password storage and they interfere with each other.
Please fix the test to use unique names or remove the test such that it is possible to have both Windows builds running in parallel.
The text was updated successfully, but these errors were encountered:
The continuous builds on Windows are running half an hour apart, so this does not reproduce on the automatic builds. However, Windows builds are running on the same physical machine.
It has happened to me both yesterday, and today, that I triggered x64 and ia32 builds at the same time. The following test has broken either the 32 bit or the 64 bit builds:
https://monacotools.visualstudio.com/Monaco/_build/index?buildId=35629
https://monacotools.visualstudio.com/Monaco/_build/index?buildId=35655
After a brief discussion with @joaomoreno, the working theory is that these tests share the same underlying password storage and they interfere with each other.
Please fix the test to use unique names or remove the test such that it is possible to have both Windows builds running in parallel.
The text was updated successfully, but these errors were encountered: