Re: [PR] CAMEL-20482: use min/max depth during markerfile cleanup [camel]
davsclaus merged PR #13366: URL: https://github.com/apache/camel/pull/13366 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] CAMEL-20482: use min/max depth during markerfile cleanup [camel]
davsclaus commented on PR #13366: URL: https://github.com/apache/camel/pull/13366#issuecomment-1973743573 Yes the GH tests can sometimes bit a little bit flaky on those file tests in camel-core -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] CAMEL-20482: use min/max depth during markerfile cleanup [camel]
sjhiggs commented on PR #13366: URL: https://github.com/apache/camel/pull/13366#issuecomment-1973643243 The build log shows a failure in `FileConsumerFailureHandledTest`, which does not fail in my local environment. Is there anything more for me to check on my end? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [PR] CAMEL-20482: use min/max depth during markerfile cleanup [camel]
github-actions[bot] commented on PR #13366: URL: https://github.com/apache/camel/pull/13366#issuecomment-1973322750 :star2: Thank you for your contribution to the Apache Camel project! :star2: :robot: CI automation will test this PR automatically. :camel: Apache Camel Committers, please review the following items: * First-time contributors **require MANUAL approval** for the GitHub Actions to run * You can use the command `/component-test (camel-)component-name1 (camel-)component-name2..` to request a test from the test bot. * You can label PRs using `build-all`, `build-dependents`, `skip-tests` and `test-dependents` to fine-tune the checks executed by this PR. * Build and test logs are available in the Summary page. **Only** [Apache Camel committers](https://camel.apache.org/community/team/#committers) have access to the summary. * :warning: Be careful when sharing logs. Review their contents before sharing them publicly. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[PR] CAMEL-20482: use min/max depth during markerfile cleanup [camel]
sjhiggs opened a new pull request, #13366: URL: https://github.com/apache/camel/pull/13366 # Description Honors min/max depth when cleaning up camel lock files. This resolves an issue where users have a large number of directories and files in subdirectories that do not need to be scanned when cleaning up marker files. # Target - [x] I checked that the commit is targeting the correct branch (note that Camel 3 uses `camel-3.x`, whereas Camel 4 uses the `main` branch) # Tracking - [x] If this is a large change, bug fix, or code improvement, I checked there is a [JIRA issue](https://issues.apache.org/jira/browse/CAMEL) filed for the change (usually before you start working on it). # Apache Camel coding standards and style - [ ] I checked that each commit in the pull request has a meaningful subject line and body. - [x] I have run `mvn clean install -DskipTests` locally and I have committed all auto-generated changes -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
