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

Azure CI sample configuration Caching post-job is flaky and gives error on tests success #347

Open
LolliDepp opened this issue Jan 10, 2020 · 1 comment

Comments

@LolliDepp
Copy link

LolliDepp commented Jan 10, 2020

I have been using the same setup as the sample for Azure CI provided here.
When I finally managed to get all my tests to pass in CI, the "Post-job: Cache Cypress bins" step has started to fail.

When I have no errors in tests, the Cache task fails, and these are the logs:

2020-01-10T17:06:50.0113914Z ##[section]Starting: Cache Cypress bins
2020-01-10T17:06:50.0193903Z ==============================================================================
2020-01-10T17:06:50.0193948Z Task         : Cache (Beta)
2020-01-10T17:06:50.0193975Z Description  : Cache files between runs
2020-01-10T17:06:50.0193996Z Version      : 1.2.0
2020-01-10T17:06:50.0194017Z Author       : Microsoft Corporation
2020-01-10T17:06:50.0194042Z Help         : https://aka.ms/pipeline-caching-docs
2020-01-10T17:06:50.0194142Z ==============================================================================
2020-01-10T17:06:50.2238310Z Resolving key:
2020-01-10T17:06:50.2349172Z  - cypress           [string]
2020-01-10T17:06:50.2349974Z  - Windows_NT        [string]
2020-01-10T17:06:50.2666611Z  - package-lock.json [file] --> 63A80EC9E3A4E0A34E40189651B6B5B6EB7B784D1FEB36DD90E42B6CC7170141
2020-01-10T17:06:50.2691627Z Resolved to: cypress|Windows_NT|hrtsPiTYC1pcs0pjVg63hUkQVRMtMwr3usRTXv5b13w=
2020-01-10T17:06:51.0380288Z Information, ApplicationInsightsTelemetrySender will correlate events with X-TFS-Session ccc5c3d1-1bb9-4861-90e5-fabad7a03c2a
2020-01-10T17:06:51.0556914Z Information, Getting a pipeline cache artifact with one of the following fingerprints:
2020-01-10T17:06:51.0557793Z Information, Fingerprint: `cypress|Windows_NT|hrtsPiTYC1pcs0pjVg63hUkQVRMtMwr3usRTXv5b13w=`
2020-01-10T17:06:52.0752523Z Information, There is a cache miss.
2020-01-10T17:06:52.1123659Z tar: could not chdir to 'D:\home\vsts\.cache\Cypress'
2020-01-10T17:06:52.1123706Z 
2020-01-10T17:06:53.0655135Z Information, ApplicationInsightsTelemetrySender correlated 1 events with X-TFS-Session ccc5c3d1-1bb9-4861-90e5-fabad7a03c2a
2020-01-10T17:06:53.0700349Z ##[error]Process returned non-zero exit code: 1
2020-01-10T17:06:53.0852310Z ##[section]Finishing: Cache Cypress bins

When at least one of my tests fail, the Cache task succeeds.

The only visibly difference seems to be I can see "test failure" logs being written to ...\AppData\Roaming\npm-cache\_logs\2020-01-10T14_29_25_544Z-debug.log in case I do have a failure.

I've tried with Cache v2, and with Cache v1 Beta (same as the example), but no differences.
Error logs are identical with the 2 versions.
With both, it only fails if tests suceed

@Coding-Means-Always-Learning

Hello @LolliDepp ,
I am having the same problem.

This does not seem to be occurring in a Linux agent
As we are required to use Windows agent I am seeing the exact issues you are referring

Did you had any luck in resolving this

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

No branches or pull requests

2 participants