apupier commented on PR #11603:
URL: https://github.com/apache/camel/pull/11603#issuecomment-1740848554
> > argh, it is no more passing on Windows. Investigating if it is after a
rebase locally or flaky or ??
>
> I think it is due to the fact that on first call when the dependencies are
not yet downloaded on local .m2, it takes too much time (more than the 60
seconds timeout). On a second run it took seconds and went fine.
This is not specific to Windows
to reproduce: clean .m2/repository/org/apache/camel , then call the copy
dependency
I reproduced with 480 seconds so there is something more than just the
download time.
An interesting point is that in fact, we do not kill the started process, so
faster timeout when trying to access the exit value, there is an exception
thrown and it means that we have a process that continue to run.
```
java.lang.IllegalThreadStateException: process hasn't exited
at java.base/java.lang.ProcessImpl.exitValue(ProcessImpl.java:460)
at
org.apache.camel.dsl.jbang.core.commands.DependencyCopy.export(DependencyCopy.java:76)
```
I do not reproduce using released Camel JBang so would mean I imagine it is
specific to the test or the fact that is using a snapshot version
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
