In CI build, npm run e2e tests fails without printing any logs and operation fails after 60mins

[aishwaryasureshkumar]

Build 0.0.0.278
Phase 1
Job
Initialize Job
Get Sources
npm install
npm run e2e tests
Publish Test Results *\protractor-test-results.xml **\TESTS-*.xml
Post Job Cleanup
Report build status

2018-06-15T00:02:44.9059862Z Task : npm
2018-06-15T00:02:44.9059862Z Description : Install and publish npm packages, or run an npm command. Supports npmjs.com and authenticated registries like Package Management.
2018-06-15T00:02:44.9059862Z Version : 1.0.15
2018-06-15T00:02:44.9059862Z Author : Microsoft Corporation
2018-06-15T00:02:44.9059862Z Help : More Information
2018-06-15T00:02:44.9059862Z ==============================================================================
2018-06-15T00:02:45.5778644Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" --version"
2018-06-15T00:02:46.9059922Z 5.6.0
2018-06-15T00:02:49.5153674Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" config list"
2018-06-15T00:02:50.7497494Z npm info it worked if it ends with ok
2018-06-15T00:02:50.7497494Z npm verb cli [ 'C:\Program Files\nodejs\node.exe',
2018-06-15T00:02:50.7497494Z ; cli configs
2018-06-15T00:02:50.7497494Z npm verb cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
2018-06-15T00:02:50.7497494Z metrics-registry = "https://registry.npmjs.org/"
2018-06-15T00:02:50.7497494Z scope = ""
2018-06-15T00:02:50.7497494Z user-agent = "npm/5.6.0 node/v8.9.4 win32 x64"
2018-06-15T00:02:50.7497494Z
2018-06-15T00:02:50.7497494Z ; environment configs
2018-06-15T00:02:50.7497494Z loglevel = "verbose"
2018-06-15T00:02:50.7497494Z userconfig = "E:\Agents\On-Premise\vsts-agent-win7-x64-2.124.0\_work\27\npm\15314.npmrc"
2018-06-15T00:02:50.7497494Z
2018-06-15T00:02:50.7497494Z ; node bin location = C:\Program Files\nodejs\node.exe
2018-06-15T00:02:50.7497494Z ; cwd = E:\Agents\On-Premise\vsts-agent-win7-x64-2.124.0_work\27\s
2018-06-15T00:02:50.7497494Z npm verb cli 'prefix',
2018-06-15T00:02:50.7497494Z ; HOME = C:\Users\WebSolutionsBldAgent
2018-06-15T00:02:50.7497494Z npm verb cli '-g' ]
2018-06-15T00:02:50.7497494Z ; "npm config ls -l" to show all defaults.
2018-06-15T00:02:50.7497494Z npm info using npm@5.6.0
2018-06-15T00:02:50.7497494Z
2018-06-15T00:02:50.7497494Z npm info using node@v8.9.4
2018-06-15T00:02:50.7497494Z npm verb exit [ 0, true ]
2018-06-15T00:02:50.7497494Z npm info ok
2018-06-15T00:02:50.7497494Z npm info it worked if it ends with ok
2018-06-15T00:02:50.7497494Z npm verb cli [ 'C:\Program Files\nodejs\node.exe',
2018-06-15T00:02:50.7497494Z npm verb cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
2018-06-15T00:02:50.7497494Z npm verb cli 'config',
2018-06-15T00:02:50.7497494Z npm verb cli 'list' ]
2018-06-15T00:02:50.7497494Z npm info using npm@5.6.0
2018-06-15T00:02:50.7497494Z npm info using node@v8.9.4
2018-06-15T00:02:50.7497494Z npm verb exit [ 0, true ]
2018-06-15T00:02:50.7497494Z npm info ok
2018-06-15T00:02:50.7497494Z [command]C:\windows\system32\cmd.exe /D /S /C ""C:\Program Files\nodejs\npm.cmd" run e2e"
2018-06-15T00:32:16.6164031Z ##[error]The operation was canceled.
2018-06-15T00:32:16.6164031Z ##[section]Async Command Start: Telemetry
2018-06-15T00:32:16.6164031Z ##[section]Async Command End: Telemetry
2018-06-15T00:32:16.6164031Z ##[section]Finishing: npm run e2e tests

[dreuxl]

Hi

look like you are launching . using the pkg from a windows machine?
If yes unfortunately, this is not. yet supported. please see #16 for more infos.

Thanks

[aishwaryasureshkumar]

Hey i don't understand why did you close my issue. my scripts are running well on local windows machine but in tfs build its not showing actual error and it fails with operation failed error.

[dreuxl]

ok sorry about that. It s weird that it s working on your local windows machine, it should not, because of the open issue we have with windows.
Maybe on your local, the retry is not invoked fully because your tests are passing first shot ?

[aishwaryasureshkumar]

@dreuxl I just wanted to confirm did you understnd my issue

[dreuxl]

I have to say with the output / description you provided, I m not quite sure:

• what you try to achieve, which Command you launch.
• where protractor-retry is coming in the picture
• I just recognized some windows stuff and just warned you that, regardless of what you try to achieve that we don't support yet windows. to spare you times.

[aishwaryasureshkumar]

I wanted to run my e2e tests.
protractor-retry is not coming in to picture here

[dreuxl]

ok, so why are u filing an issue against this repo/pkg?