CircleCI-Public / cimg-php

The CircleCI PHP Docker image. Based on the `cimg/base` image.
https://circleci.com/developer/images/image/cimg/php
MIT License
12 stars 16 forks source link

Bug Report: <BUG> Docker image with PHP 8.3.11 may cause persist to workspace step to fail #268

Closed byrond closed 2 months ago

byrond commented 2 months ago

Note: We also welcome PRs to fix bugs! This helps us take action faster where a bug has been identified!

For our official CircleCI Docker Convenience Image support policy, please see CircleCI docs.

This policy outlines the release, update, and deprecation policy for CircleCI Docker Convenience Images.


Describe the bug When our builds began using the latest container images with PHP 8.3.11 (with browsers), they started failing with:

Error archiving workspace files: Error archiving files to tarball /tmp/workspace-layer... : tar: project/docroot: file changed as we read it : exit status 1

Rolling back to the previous version of the container (with PHP 8.3.10) fixed the issue.

To Reproduce Add the persist_to_workspace step to the end of the workflow and include the project directory in the paths.

Expected behavior Workspace persists without errors.

Workarounds Pin jobs using workspace persistence to cimg/php:8.3.10-browsers

Screenshots and Build Links If possible, add screenshots and links to jobs to help explain your problem.

Additional context Builds test a Drupal site using Behat, and the call to behat is the final step before saving artifacts and persisting the workspace.

byrond commented 2 months ago

I'm currently trying to reproduce this on a public repo that we can share.

byrond commented 2 months ago

I cannot reproduce this on our public toolchain repo: https://app.circleci.com/pipelines/github/palantirnet/the-build/601/workflows/6d3b7eed-318a-4135-b6e1-4a4c112d9796/jobs/610

https://github.com/palantirnet/the-build/commit/ee70f8d2d06adab994974fe5a3c1d8a871b7e150

There are not nearly as many tests run on this simple repo, though. Our client's project takes almost 30 minutes to complete the Behat step.

byrond commented 2 months ago

Since I can't give a clear method to reproduce this outside our client's project, I'll close this bug report and reopen later if we find concrete evidence the new Docker container image is causing this error. Hopefully, if someone else has this problem and can more easily reproduce the error, they will discover this and reopen the issue.