-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Pipeline Caching failures should not fail the build #10917
Comments
I'm hoping the workaround of using If you think that's the general solution, I recommend adding it to the examples in the docs. |
Thanks for reporting. We need to investigate why you are getting a Also linking to #10907 since we should also consider replicating the step's |
It was a one off error affecting 2 builds during the same time period. I can give you more details if it would help? |
Earlier in the logs you should see a line like this:
If you can share your session GUID we can look directly at the telemetry. |
Information, DedupManifestArtifactClient will correlate http requests with X-TFS-Session a39b617b-566f-4c42-a5d2-ad03bb0994be It happened a lot today at various times. It also happened once on a build pipeline artifact (same error) |
@willsmythe @johnterickson any progress on why it happens? I've switched to 7z compressing node_modules before caching which obv. reduces the number of files massively and takes the payload from 800mb to 200mb and that seems to have stopped the errors occurring. I had one build that hadn't yet rebased on the new pipeline and that still failed, heres the logs
|
@lukeapage We've increased the capacity of the scale unit you were seeing this on. You should stop seeing this in an hour or two. |
Capacity increased and throttled no longer observed. Do reactivate if you see this error again. |
@johnterickson this issue was also about defaulting continue on error to true for cache tasks, do you want to reopen for that or is it handled elsewhere/ you don’t want to do it? |
@willsmythe to confirm, you are support of cache steps being continueOnError? |
@lukeapage - We are going to have the users decide whether they want to continue on error of the cache task or not; closing this issue. Thanks. |
Seeing this too on azure hosted agents (system independent) https://dev.azure.com/renovatebot/renovate/_build/results?buildId=1157
|
Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name: CacheBeta
Environment
Server - Azure Pipelines or TFS on-premises?
If using TFS on-premises, provide the version:
If using Azure Pipelines, provide the account name, team project name, build definition name/build number:
Agent - Hosted or Private:
If using Hosted agent, provide agent queue name:
If using private agent, provide the OS of the machine running the agent and the agent version:
Issue Description
When we get a failure on the pipeline which has happened quite a lot recently, it should use save that the cache was not restored (and not try to save it again).
Task logs
The text was updated successfully, but these errors were encountered: