Details
-
Type:
Bug
-
Status:
Closed
-
Priority:
Major
-
Resolution: Cannot Reproduce
-
Affects Version/s: 1.1-beta-1
-
Fix Version/s: 1.1-beta-3
-
Component/s: None
-
Labels:None
-
Complexity:Intermediate
-
Number of attachments :
Description
I've noticed on several occasions that a project is suddenly marked as "Error" without any change on the project itself.
The error is displayed on the global summary and in the project group summary, but it does not appear on the builds page of the project.
There is no error in the logs.
As it happens quite often, I've finally noticed that the "trigger" to this issue seem to be the following:
When a schedule runs to enqueue project while one of them is being updated from its SCM (even when there is no change), the project is then marked as error as described above.
More specifically, it seems that the log pattern common to these build failure is:
377162928 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Executing: /bin/bash -c "cd /drive/continuum-1.1-beta-1/work/55 && cvs -z3 -f -q update -d"
377162928 [pool-1-thread-1] INFO org.apache.maven.scm.manager.ScmManager:default - Working directory: /drive/continuum-1.1-beta-1/work/55
377163028 [defaultScheduler_Worker-1] INFO org.apache.maven.continuum.build.settings.SchedulesActivator:default - >>>>>>>>>>>>>>>>>>>>> Executing build job (DEFAULT_SCHEDULE)...
377163307 [pool-1-thread-1] INFO org.apache.maven.continuum.buildcontroller.BuildController:default - Merging SCM results
I tested with 1.1-beta-2/beta-3 with a schedule defined to every second to try to reproduce this issue and all works fine without error