Bug 972623
| Summary: | jbpm-human-task-core tests fail on mssql due to: null id in org.jbpm.services.task.impl.model.TaskImpl entry | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] JBoss BPMS Platform 6 | Reporter: | Jiri Svitak <jsvitak> | ||||
| Component: | jBPM Core | Assignee: | Mauricio Salatino <msalatin> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Jiri Svitak <jsvitak> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | unspecified | CC: | mbaluch | ||||
| Target Milestone: | ER1 | ||||||
| Target Release: | 6.0.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-08-06 20:10:54 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Jiri Svitak
2013-06-10 08:48:05 UTC
I don't know how to reproduce the issue. Can you make sure that you have the correct MSSQL drivers for that database version? For this case I would recommend to see if the tests works at least with one version of MS SQL Hi, yes, I am sure that I use correct drivers. Other jBPM modules besides human-task work the same drivers fine, see the whole db matrix: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/view/All/job/jbpm-persistence-db-matrix/ Have you looked at the Jenkins job results? Have you analyzed the stack traces? Please open the the attached links to Jenkins. If the available logs and resources are insufficient, you can reproduce the problem again - either configure your local test suite to use MSSQL or use Jenkins job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/view/All/job/droolsjbpm-persistence-db-single/ You can also look how this 'single' job is executed and use its configuration Groovy script to run the job on local computer. Please, do not ignore these bugs and set them to MODIFIED status only if the issue is resolved. Thanks. Hi the tests are not running now: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/view/All/job/jbpm-persistence-db-matrix/DATABASE=mssql2008R2,MODULES=jbpm-human-task%2Fjbpm-human-task-core,jdk=java16_default,label=RHEL_any/136/console It seems that the update to use maven 3.0.5 break all the tests Verified in 6.0.x product branch: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/Drools%20jBPM/view/All/job/jbpm-persistence-db-matrix-6.0.x/DATABASE=mssql2008R2,MODULES=jbpm-human-task%2Fjbpm-human-task-core,jdk=java16_default,label_exp=RHEL5||RHEL6/5/ Cannot set the mandatory target milestone, because: 1.) there are no libraries of the product, which the verification can be done against 2.) the job is configured to run continuously against 6.0.x product branch (Using ER1 for this.) commit in 6.0.x branch: https://github.com/droolsjbpm/jbpm/commit/9b274ffa840ad0e56fb552b1f6384a9f9627e260 This BZ has been part of the 6.0.0 stream. |