Build status

Build Id Status Comments
225 FAILURE
  • ticket:1610 - Reload WCS/WMS GetCapabilities when user invokes change requests from OWS client Summary: In OWS client, when user sends a DeleteCoverage request or InsertCoverage, the old (new) coverageId does not show correctly in the list of coverageIds. It only shows correctly when user click on WCS GetCapabiliteis button. WMS insert/update/delete style also needs to click on WMS GetCapabilities button to show newly updated values. It is not convenient for user to do this redundant actions and OWS client should invoke WCS/WMS GetCapabilities internally. Test Plan: Run system test for testing OWS client. Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D458
224 FAILURE
  • ticket:971 - WCST_Import reports time, speed to ingest each slice Summary: WCST_Import needs to report time, speed (MB/s) to ingest each slice (file). Example: Progress: [------------------------------] 0/4 0.00% Test me: AUT-PM10_2008-01-01T02:01:20.geo.tif with size: 0.02 MB. Total time to ingest: 0.71 s. Speed: 0.03 MB/s. Test Plan: Run test wcst_import Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D462
223 FAILURE
  • ticket:242 - improved precision of output in csv and json Summary: included <limit> and <iomanip> in csv.cc to acheive optimal stream output precision for float and double. also removed archaic oracle files in the systemtest directory for test_wcps and test_wcs. Test Plan: repeat tests in test_select, test_wcps, test_wcs Reviewers: dmisev Reviewed By: dmisev Subscribers: bphamhuu Differential Revision: http://codereview.rasdaman.org/D464
222 FAILURE
  • ticket:1603 - SystemTest_Test wcst_import should remove obsolete cases when running test Summary: When a test in test wcst_import folder is renamed in a new patch and the patch is applied, the old test case folder still exists due to it contains a file ingest.json. Then, wcst_import test still runs this test but it could not find the data files, so just returns as a failed case. Test wcst_import should remove these obsolete cases instead of running them. Test Plan: Run tst wcst_import test. Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D459
  • ticket:502 - Fix error with delete temp directory for gdal-java when starting petascope Summary: GDAL JNI is used in petascope and it is copied to /tmp/rasdaman/gdal_java folder everytime petascope applications (main, migration) start. Then, it will load these files to JVM and this folder could be removed when petascope restarts. FileUtils cannot remove this folder properly, so it needs to use the shell command to remove and it will not throw exception as folder cannot be removed. Test Plan: Tested by running migration application which uses root permission, then start petascope with tomcat permission. Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D460
  • ticket:1029 - WCST_Import uses more meaningful type names when creating cell/array/set instead of random name Summary: WCST_Import creates cell/array/set of rasdaman collection with random name. This makes it very hard to manage from user's perspective. It will change to use the collection name as prefix and add _Cell/Array_Set accordingly. Example: CREATE TYPE test_irr_cube_2_Cell AS ( band0 float ,band1 float ) CREATE TYPE test_irr_cube_2_Array AS test_irr_cube_2_Cell MDARRAY [dim0,dim1,dim2] CREATE TYPE test_irr_cube_2_Set AS SET (test_irr_cube_2_Array ) Test Plan: Run test system Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D461
221 FAILURE
  • ticket:502 - Fix logging in the Spring framework and faulty Bean injection in petascope Summary: There is a hidden problem from Spring Framework which it will stop Tomcat then petascope also cannot start. The problem is shown when adding the log4j for Spring Framework when it starts and is fixed. It was about the ambiguity of injection Bean to a java class, but Spring cannot show the error in log as Spring Framework starts before petascope.properties is loaded. Test Plan: Tested by copying war, jar to a VM and it could run. Reviewers: dmisev Differential Revision: http://codereview.rasdaman.org/D457

Build system information

OSCentOS release 6.5 (Final)
archx86_64
gcc --version4.4.7 20120313 (Red Hat 4.4.7-4)
javac -version1.7.0_55
bison --version2.4.1