Skip to navigation
Skip to content

Build result summary

Details

Completed: 22 Aug 2019, 2:05:15 PM – 5 years ago
Queue duration: 3 hours
Duration: 617 minutes
Labels: None

Revision: 96a1a12573bf099dd4f5e8ca580cb3d8ce9cc6c1 96a1a12573bf099dd4f5e8ca580cb3d8ce9cc6c1
Total tests: 228

Tests

0 New failures
8 Existing failures
0 Fixed

Responsible

No one has taken responsibility for this failure

Code commits

Author		Commit	Message	Commit date
	Darrell Schiebel	96a1a12573bf099dd4f5e8ca580cb3d8ce9cc6c1 96a1a12573bf099dd4f5e8ca580cb3d8ce9cc6c1	Merge pull request #1082 in CASA/casa from bugfix/CAS-12636 to release/pipeline/5.6.0 * commit '07057738fca2a7fe4a5828a134757223e812ea4d': CAS-12582: Added trap for case of user specifying too many spws in spwmap (in general), which was causing a memory corruption in filling pivot frequencies for delay (KJones) application. Also introduced interim fix in KJones for spwmap'd pivot frequency comprehension in the cal library context (assume spwmap uniformity over callib entries, for now).	21 Aug 2019
	Kana Sugimoto <ksugimot@nrao.edu>	b8584fdedfde6690a3b7fda526f12896d30ed68b b8584fdedfde6690a3b7fda526f12896d30ed68b	Merge pull request #1084 in CASA/casa from bugfix/CAS-12639 to release/pipeline/5.6.0 * commit '70a499648f98c58e28cf12f69f70e94de6605640': CAS-12603: Fix additional dangling table cache issues which occurs in inner antenna loop when insufficient data triggers a continue (added missing st.close()). CAS-12603: Added close of the table tool created by the deep copy of the input table, so it doesn't get stuck in the table cache.	21 Aug 2019
	George Moellenbrock	70a499648f98c58e28cf12f69f70e94de6605640 70a499648f98c58e28cf12f69f70e94de6605640	CAS-12603: Fix additional dangling table cache issues which occurs in inner antenna loop when insufficient data triggers a continue (added missing st.close()).	20 Aug 2019
	George Moellenbrock	8cc62cdc693f046af427bfd4e1696957f908a48d 8cc62cdc693f046af427bfd4e1696957f908a48d	CAS-12603: Added close of the table tool created by the deep copy of the input table, so it doesn't get stuck in the table cache.	20 Aug 2019
	George Moellenbrock	07057738fca2a7fe4a5828a134757223e812ea4d 07057738fca2a7fe4a5828a134757223e812ea4d	CAS-12582: Added trap for case of user specifying too many spws in spwmap (in general), which was causing a memory corruption in filling pivot frequencies for delay (KJones) application. Also introduced interim fix in KJones for spwmap'd pivot frequency comprehension in the cal library context (assume spwmap uniformity over callib entries, for now).	19 Aug 2019

Tests

Existing test failures 8
	Status	Test	Failing since	View job	Duration
Expand	Failed	5805 SIMOBSERVE Run regression History		Accepted Test EL7	4 mins
AssertionError: The execution of test_simobserve failed...
Expand	Failed	5805 SIMOBSERVE Run regression History		Accepted Test OSX10.14	5 mins
AssertionError: The execution of test_simobserve failed...
Expand	Failed	5805 SIMOBSERVE Run regression History		Accepted Test EL6	8 mins
AssertionError: The execution of test_simobserve failed...
Expand	Failed	5805 SIMOBSERVE Run regression History		Accepted Test OSX10.13	6 mins
AssertionError: The execution of test_simobserve failed...
Expand	Failed	8705 PIPELINE VLA Run regression History		Accepted Test EL7	32 mins
AssertionError: The execution of pipelineTest_vla failed...
Expand	Failed	8705 PIPELINE VLA Run regression History		Accepted Test OSX10.14	39 mins
AssertionError: The execution of pipelineTest_vla failed...
Expand	Failed	8705 PIPELINE VLA Run regression History		Accepted Test EL6	34 mins
AssertionError: The execution of pipelineTest_vla failed...
Expand	Failed	8705 PIPELINE VLA Run regression History		Accepted Test OSX10.13	35 mins
AssertionError: The execution of pipelineTest_vla failed...

Jira issues

Issue		Description	Status
Unknown Issue Type	CAS-12582	Could not obtain issue details from Jira
Unknown Issue Type	CAS-12603	Could not obtain issue details from Jira
Unknown Issue Type	CAS-12636	Could not obtain issue details from Jira
Unknown Issue Type	CAS-12639	Could not obtain issue details from Jira