Bugzilla – Full Text Bug Listing
| Summary: | tptp:execution Ant task puts invalid paths into resultsrefid attribute (not resolving project root folders correctly) | ||||||
|---|---|---|---|---|---|---|---|
| Product: | z_Archived | Reporter: | John O'Shea <john.oshea> | ||||
| Component: | TPTP | Assignee: | Joe Toomey <jptoomey> | ||||
| Status: | CLOSED FIXED | QA Contact: | |||||
| Severity: | normal | ||||||
| Priority: | P1 | CC: | paulslau, ravi.aroy, scott.schneider | ||||
| Version: | unspecified | Keywords: | plan | ||||
| Target Milestone: | --- | ||||||
| Hardware: | All | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Attachments: |
|
||||||
Hi John, This defect appears to have lain dormant for a while. I will be taking ownership of the ASF code in TPTP, and can fix this defect. However, we are about to begin our final test pass of the 4.2.1 release, and without a low-risk fix in hand, this defect is no longer a candidate to be fixed in this release. We can address it in 4.3 i2 (which will open in a couple of weeks.) Based on the defect severity, I assume this is okay with you. If it is not, please reply and increase the severity of the defect, and we can discuss possible alternatives. Thanks, --Joe If 4.3i2 is coming in a couple of weeks we can wait until then. We do currently the workaround of creating the workspace in the folder below the project dir so this is not blocking. 4.3 is scheduled to GA at the end of October. 4.2.1 is scheduled to GA at the end of September, but we are beginning the shutdown process very early, and are now including only stop-ship fixes. CVS HEAD will open for 4.3 i2 work (which will include 4.3 enhancements) on August 14th. Daily development builds will be available as usual, but the first "stable driver" (on which we have completed a full test pass) will not be available until the end of i2 (September 22nd.) Hopefully this will not dissuade you from taking and using a development driver to address this problem once the fix has been made. Please target to 4.4 since all non-blocking/critical defects will be deferred as decided in today's AG call. Unfortunately, I let this defect go too long, and I can no longer get approval to fix it in 4.3. I will address it as soon as 4.4 opens. Sorry for the delay. Created attachment 57515 [details]
mylar/context/zip
Incomplete fix, moving to new workspace
Fix is still incomplete but ongoing. Need to target for i2. The priority of this defect has not changed, but it is being deferred to i3 to allow for other work with UI changes that need to be complete in i2. Fix from March finally validated and delivered. Sorry for the slow turnaround. Reporter: Please verify and close in preparation for shutting down the TPTP 4.4 release. Thanks. Fixed and validated in TPTP 4.4. Closing. |
It appears that the <tptp:execution> Ant task assumes that TPTP project folders are always physically located under the workspace directory. When I run this task like <tptp:execution resultsrefid="tptp.test.results" project="${tptp.test.project}" suite="testsuites/SampleTest.testsuite" deployment="testsuites/AutoUiDeployment.deploy"> </tptp:execution> </target> I subsequently pass the tptp.test.results refid into the test-results-interrogation task to see what happened: <!-- Interrogate test suite results for verdict --> <target name="test-results-interrogation"> <echo message="Interrogating test suite results..." /> <condition property="tptp.test.success"> <tptp:interrogation verdictproperty="tptp.test.verdict"> <filelist refid="tptp.test.results"/> </tptp:interrogation> </condition> <echo message="The overall test result verdict is: '${tptp.test.verdict}'" /> </target> If the project that I am testing is not located beheath the workspace folder then I get the following error: test-results-interrogation: [echo] Interrogating test suite results... [echo] Results File is: 'org.apache.tools.ant.types.FileList@1c282a1' [condition] C:\fdb2\test\ui-tests\workspace\com.capeclear.ui.test\SampleTest_1150107716328.execution does not exist -- s kipping It looks like the implementation is not resolving the project path's real root folder but rather is assuming that it is relative to the workspace root folder. (I'm sure you are aware that it is a common scenario to import projects from locations outside the workspace dir). Hope I've logged this against the correct TPTP component?