==955187== location. If you are running Memcheck and you just saw a
==955187== warning about a bad jump, it's probably your program's fault.
==955187== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955187== i.e. it's Valgrind's fault. If you think this is the case or
==955187== you are not sure, please let us know and we'll try to fix it.
==955187== Either way, Valgrind will now raise a SIGILL signal which will
==955187== probably kill your program.
Start 220: ResidualBoundaryTrace_Dirichlet_mitState_DGBR2_AD_btest_memcheck
110/984 Test #220: ResidualBoundaryTrace_Dirichlet_mitState_DGBR2_AD_btest_memcheck ..........................................***Exception: Illegal 11.16 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xB7 0xD0 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955251== valgrind: Unrecognised instruction at address 0xbad52f.
==955251== Your program just tried to execute an instruction that Valgrind
==955251== did not recognise. There are two possible reasons for this.
==955251== 1. Your program has a bug and erroneously jumped to a non-code
==955251== location. If you are running Memcheck and you just saw a
==955251== warning about a bad jump, it's probably your program's fault.
==955251== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955251== i.e. it's Valgrind's fault. If you think this is the case or
==955251== you are not sure, please let us know and we'll try to fix it.
==955251== Either way, Valgrind will now raise a SIGILL signal which will
==955251== probably kill your program.
Start 222: ResidualBoundaryTrace_LinearScalar_sansLG_DGBR2_AD_btest_memcheck
111/984 Test #222: ResidualBoundaryTrace_LinearScalar_sansLG_DGBR2_AD_btest_memcheck .........................................***Exception: Illegal 11.19 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x47 0xD0 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955317== valgrind: Unrecognised instruction at address 0xbad5ef.
==955317== Your program just tried to execute an instruction that Valgrind
==955317== did not recognise. There are two possible reasons for this.
==955317== 1. Your program has a bug and erroneously jumped to a non-code
==955317== location. If you are running Memcheck and you just saw a
==955317== warning about a bad jump, it's probably your program's fault.
==955317== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955317== i.e. it's Valgrind's fault. If you think this is the case or
==955317== you are not sure, please let us know and we'll try to fix it.
==955317== Either way, Valgrind will now raise a SIGILL signal which will
==955317== probably kill your program.
Start 224: ResidualCell_DGAdvective_Euler2D_btest_memcheck
112/984 Test #224: ResidualCell_DGAdvective_Euler2D_btest_memcheck ...........................................................***Exception: Illegal 11.00 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xD7 0x68 0x33 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955413== valgrind: Unrecognised instruction at address 0x8ed6af.
==955413== Your program just tried to execute an instruction that Valgrind
==955413== did not recognise. There are two possible reasons for this.
==955413== 1. Your program has a bug and erroneously jumped to a non-code
==955413== location. If you are running Memcheck and you just saw a
==955413== warning about a bad jump, it's probably your program's fault.
==955413== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955413== i.e. it's Valgrind's fault. If you think this is the case or
==955413== you are not sure, please let us know and we'll try to fix it.
==955413== Either way, Valgrind will now raise a SIGILL signal which will
==955413== probably kill your program.
Start 226: ResidualCell_DGBR2_AD_btest_memcheck
113/984 Test #226: ResidualCell_DGBR2_AD_btest_memcheck ......................................................................***Exception: Illegal 11.12 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x67 0x7D 0x2F 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955525== valgrind: Unrecognised instruction at address 0xea062f.
==955525== Your program just tried to execute an instruction that Valgrind
==955525== did not recognise. There are two possible reasons for this.
==955525== 1. Your program has a bug and erroneously jumped to a non-code
==955525== location. If you are running Memcheck and you just saw a
==955525== warning about a bad jump, it's probably your program's fault.
==955525== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955525== i.e. it's Valgrind's fault. If you think this is the case or
==955525== you are not sure, please let us know and we'll try to fix it.
==955525== Either way, Valgrind will now raise a SIGILL signal which will
==955525== probably kill your program.
Start 228: ResidualCell_DGBR2_LiftedQuantity_TwoPhaseAV_btest_memcheck
114/984 Test #228: ResidualCell_DGBR2_LiftedQuantity_TwoPhaseAV_btest_memcheck ...............................................***Exception: Illegal 11.31 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x4F 0x53 0x3C 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955596== valgrind: Unrecognised instruction at address 0xfca30f.
==955596== Your program just tried to execute an instruction that Valgrind
==955596== did not recognise. There are two possible reasons for this.
==955596== 1. Your program has a bug and erroneously jumped to a non-code
==955596== location. If you are running Memcheck and you just saw a
==955596== warning about a bad jump, it's probably your program's fault.
==955596== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955596== i.e. it's Valgrind's fault. If you think this is the case or
==955596== you are not sure, please let us know and we'll try to fix it.
==955596== Either way, Valgrind will now raise a SIGILL signal which will
==955596== probably kill your program.
Start 230: ResidualInteriorTrace_DGBR2_AD_btest_memcheck
115/984 Test #230: ResidualInteriorTrace_DGBR2_AD_btest_memcheck .............................................................***Exception: Illegal 11.14 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x97 0xAA 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955704== valgrind: Unrecognised instruction at address 0xbb98af.
==955704== Your program just tried to execute an instruction that Valgrind
==955704== did not recognise. There are two possible reasons for this.
==955704== 1. Your program has a bug and erroneously jumped to a non-code
==955704== location. If you are running Memcheck and you just saw a
==955704== warning about a bad jump, it's probably your program's fault.
==955704== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955704== i.e. it's Valgrind's fault. If you think this is the case or
==955704== you are not sure, please let us know and we'll try to fix it.
==955704== Either way, Valgrind will now raise a SIGILL signal which will
==955704== probably kill your program.
Start 232: SetFieldBoundaryTrace_DGBR2_LO_AD_Dirichlet_mitState_btest_memcheck
116/984 Test #232: SetFieldBoundaryTrace_DGBR2_LO_AD_Dirichlet_mitState_btest_memcheck .......................................***Exception: Illegal 11.25 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x27 0x15 0x37 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955782== valgrind: Unrecognised instruction at address 0x102d06f.
==955782== Your program just tried to execute an instruction that Valgrind
==955782== did not recognise. There are two possible reasons for this.
==955782== 1. Your program has a bug and erroneously jumped to a non-code
==955782== location. If you are running Memcheck and you just saw a
==955782== warning about a bad jump, it's probably your program's fault.
==955782== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955782== i.e. it's Valgrind's fault. If you think this is the case or
==955782== you are not sure, please let us know and we'll try to fix it.
==955782== Either way, Valgrind will now raise a SIGILL signal which will
==955782== probably kill your program.
Start 234: SetFieldInteriorTrace_DGBR2_LiftedQuantity_TwoPhaseAV_btest_memcheck
117/984 Test #234: SetFieldInteriorTrace_DGBR2_LiftedQuantity_TwoPhaseAV_btest_memcheck ......................................***Exception: Illegal 11.27 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7F 0xF9 0x3A 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955834== valgrind: Unrecognised instruction at address 0xeafd2f.
==955834== Your program just tried to execute an instruction that Valgrind
==955834== did not recognise. There are two possible reasons for this.
==955834== 1. Your program has a bug and erroneously jumped to a non-code
==955834== location. If you are running Memcheck and you just saw a
==955834== warning about a bad jump, it's probably your program's fault.
==955834== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955834== i.e. it's Valgrind's fault. If you think this is the case or
==955834== you are not sure, please let us know and we'll try to fix it.
==955834== Either way, Valgrind will now raise a SIGILL signal which will
==955834== probably kill your program.
Start 236: SetFieldInteriorTrace_DGBR2_LiftingOperator_AD_btest_memcheck
118/984 Test #236: SetFieldInteriorTrace_DGBR2_LiftingOperator_AD_btest_memcheck .............................................***Exception: Illegal 11.25 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xC7 0xE4 0x36 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==955935== valgrind: Unrecognised instruction at address 0x102bdaf.
==955935== Your program just tried to execute an instruction that Valgrind
==955935== did not recognise. There are two possible reasons for this.
==955935== 1. Your program has a bug and erroneously jumped to a non-code
==955935== location. If you are running Memcheck and you just saw a
==955935== warning about a bad jump, it's probably your program's fault.
==955935== 2. The instruction is legitimate but Valgrind doesn't handle it,
==955935== i.e. it's Valgrind's fault. If you think this is the case or
==955935== you are not sure, please let us know and we'll try to fix it.
==955935== Either way, Valgrind will now raise a SIGILL signal which will
==955935== probably kill your program.
Start 238: SolutionData_DGBR2_Block2_btest_memcheck
119/984 Test #238: SolutionData_DGBR2_Block2_btest_memcheck ..................................................................***Exception: Illegal 11.17 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x77 0xDF 0x32 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956050== valgrind: Unrecognised instruction at address 0xbad1cf.
==956050== Your program just tried to execute an instruction that Valgrind
==956050== did not recognise. There are two possible reasons for this.
==956050== 1. Your program has a bug and erroneously jumped to a non-code
==956050== location. If you are running Memcheck and you just saw a
==956050== warning about a bad jump, it's probably your program's fault.
==956050== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956050== i.e. it's Valgrind's fault. If you think this is the case or
==956050== you are not sure, please let us know and we'll try to fix it.
==956050== Either way, Valgrind will now raise a SIGILL signal which will
==956050== probably kill your program.
Start 240: SolutionData_DGBR2_btest_memcheck
120/984 Test #240: SolutionData_DGBR2_btest_memcheck .........................................................................***Exception: Illegal 11.13 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x37 0x72 0x34 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956292== valgrind: Unrecognised instruction at address 0xbaff0f.
==956292== Your program just tried to execute an instruction that Valgrind
==956292== did not recognise. There are two possible reasons for this.
==956292== 1. Your program has a bug and erroneously jumped to a non-code
==956292== location. If you are running Memcheck and you just saw a
==956292== warning about a bad jump, it's probably your program's fault.
==956292== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956292== i.e. it's Valgrind's fault. If you think this is the case or
==956292== you are not sure, please let us know and we'll try to fix it.
==956292== Either way, Valgrind will now raise a SIGILL signal which will
==956292== probably kill your program.
Start 242: AlgebraicEquationSet_Galerkin_BuckleyLeverett_ST_btest_memcheck
121/984 Test #242: AlgebraicEquationSet_Galerkin_BuckleyLeverett_ST_btest_memcheck ...........................................***Exception: Illegal 11.16 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xE7 0xE3 0x63 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956414== valgrind: Unrecognised instruction at address 0xe17d6f.
==956414== Your program just tried to execute an instruction that Valgrind
==956414== did not recognise. There are two possible reasons for this.
==956414== 1. Your program has a bug and erroneously jumped to a non-code
==956414== location. If you are running Memcheck and you just saw a
==956414== warning about a bad jump, it's probably your program's fault.
==956414== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956414== i.e. it's Valgrind's fault. If you think this is the case or
==956414== you are not sure, please let us know and we'll try to fix it.
==956414== Either way, Valgrind will now raise a SIGILL signal which will
==956414== probably kill your program.
Start 244: AlgebraicEquationSet_Galerkin_Stabilized_Triangle_AD_btest_memcheck
122/984 Test #244: AlgebraicEquationSet_Galerkin_Stabilized_Triangle_AD_btest_memcheck .......................................***Exception: Illegal 11.18 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xEF 0x90 0x4E 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956510== valgrind: Unrecognised instruction at address 0xead66f.
==956510== Your program just tried to execute an instruction that Valgrind
==956510== did not recognise. There are two possible reasons for this.
==956510== 1. Your program has a bug and erroneously jumped to a non-code
==956510== location. If you are running Memcheck and you just saw a
==956510== warning about a bad jump, it's probably your program's fault.
==956510== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956510== i.e. it's Valgrind's fault. If you think this is the case or
==956510== you are not sure, please let us know and we'll try to fix it.
==956510== Either way, Valgrind will now raise a SIGILL signal which will
==956510== probably kill your program.
Start 246: AlgebraicEquationSet_Galerkin_Stabilized_Triangle_SA_btest_memcheck
123/984 Test #246: AlgebraicEquationSet_Galerkin_Stabilized_Triangle_SA_btest_memcheck .......................................***Exception: Illegal 11.18 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xFF 0x75 0x73 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956618== valgrind: Unrecognised instruction at address 0x16b814f.
==956618== Your program just tried to execute an instruction that Valgrind
==956618== did not recognise. There are two possible reasons for this.
==956618== 1. Your program has a bug and erroneously jumped to a non-code
==956618== location. If you are running Memcheck and you just saw a
==956618== warning about a bad jump, it's probably your program's fault.
==956618== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956618== i.e. it's Valgrind's fault. If you think this is the case or
==956618== you are not sure, please let us know and we'll try to fix it.
==956618== Either way, Valgrind will now raise a SIGILL signal which will
==956618== probably kill your program.
Start 248: AlgebraicEquationSet_Galerkin_Triangle_AD_btest_memcheck
124/984 Test #248: AlgebraicEquationSet_Galerkin_Triangle_AD_btest_memcheck ..................................................***Exception: Illegal 11.25 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x5F 0x90 0x4E 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956693== valgrind: Unrecognised instruction at address 0xe806ef.
==956693== Your program just tried to execute an instruction that Valgrind
==956693== did not recognise. There are two possible reasons for this.
==956693== 1. Your program has a bug and erroneously jumped to a non-code
==956693== location. If you are running Memcheck and you just saw a
==956693== warning about a bad jump, it's probably your program's fault.
==956693== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956693== i.e. it's Valgrind's fault. If you think this is the case or
==956693== you are not sure, please let us know and we'll try to fix it.
==956693== Either way, Valgrind will now raise a SIGILL signal which will
==956693== probably kill your program.
Start 250: AlgebraicEquationSet_Local_Galerkin_Stabilized_Triangle_AD_btest_memcheck
125/984 Test #250: AlgebraicEquationSet_Local_Galerkin_Stabilized_Triangle_AD_btest_memcheck .................................***Exception: Illegal 15.51 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xA7 0x10 0x4A 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==956814== valgrind: Unrecognised instruction at address 0xf590cf.
==956814== Your program just tried to execute an instruction that Valgrind
==956814== did not recognise. There are two possible reasons for this.
==956814== 1. Your program has a bug and erroneously jumped to a non-code
==956814== location. If you are running Memcheck and you just saw a
==956814== warning about a bad jump, it's probably your program's fault.
==956814== 2. The instruction is legitimate but Valgrind doesn't handle it,
==956814== i.e. it's Valgrind's fault. If you think this is the case or
==956814== you are not sure, please let us know and we'll try to fix it.
==956814== Either way, Valgrind will now raise a SIGILL signal which will
==956814== probably kill your program.
Start 252: AlgebraicEquationSet_Local_Galerkin_Stabilized_Triangle_Euler_btest_memcheck
126/984 Test #252: AlgebraicEquationSet_Local_Galerkin_Stabilized_Triangle_Euler_btest_memcheck ..............................***Exception: Illegal 11.20 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xCF 0xF2 0x83 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957004== valgrind: Unrecognised instruction at address 0x112ae8f.
==957004== Your program just tried to execute an instruction that Valgrind
==957004== did not recognise. There are two possible reasons for this.
==957004== 1. Your program has a bug and erroneously jumped to a non-code
==957004== location. If you are running Memcheck and you just saw a
==957004== warning about a bad jump, it's probably your program's fault.
==957004== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957004== i.e. it's Valgrind's fault. If you think this is the case or
==957004== you are not sure, please let us know and we'll try to fix it.
==957004== Either way, Valgrind will now raise a SIGILL signal which will
==957004== probably kill your program.
Start 254: AlgebraicEquationSet_ProjectFunction_btest_memcheck
127/984 Test #254: AlgebraicEquationSet_ProjectFunction_btest_memcheck .......................................................***Exception: Illegal 26.51 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xB7 0x85 0x2D 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957106== valgrind: Unrecognised instruction at address 0x917fcf.
==957106== Your program just tried to execute an instruction that Valgrind
==957106== did not recognise. There are two possible reasons for this.
==957106== 1. Your program has a bug and erroneously jumped to a non-code
==957106== location. If you are running Memcheck and you just saw a
==957106== warning about a bad jump, it's probably your program's fault.
==957106== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957106== i.e. it's Valgrind's fault. If you think this is the case or
==957106== you are not sure, please let us know and we'll try to fix it.
==957106== Either way, Valgrind will now raise a SIGILL signal which will
==957106== probably kill your program.
Start 256: ElementIntegral_Galerkin_2D_Triangle_AD_btest_memcheck
128/984 Test #256: ElementIntegral_Galerkin_2D_Triangle_AD_btest_memcheck ....................................................***Exception: Illegal 10.99 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x27 0xBC 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957315== valgrind: Unrecognised instruction at address 0x56a6cf.
==957315== Your program just tried to execute an instruction that Valgrind
==957315== did not recognise. There are two possible reasons for this.
==957315== 1. Your program has a bug and erroneously jumped to a non-code
==957315== location. If you are running Memcheck and you just saw a
==957315== warning about a bad jump, it's probably your program's fault.
==957315== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957315== i.e. it's Valgrind's fault. If you think this is the case or
==957315== you are not sure, please let us know and we'll try to fix it.
==957315== Either way, Valgrind will now raise a SIGILL signal which will
==957315== probably kill your program.
Start 258: ExtractCGLocalBoundaries_btest_memcheck
129/984 Test #258: ExtractCGLocalBoundaries_btest_memcheck ...................................................................***Exception: Illegal 23.11 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xB7 0xB5 0x2F 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957367== valgrind: Unrecognised instruction at address 0x1091b8f.
==957367== Your program just tried to execute an instruction that Valgrind
==957367== did not recognise. There are two possible reasons for this.
==957367== 1. Your program has a bug and erroneously jumped to a non-code
==957367== location. If you are running Memcheck and you just saw a
==957367== warning about a bad jump, it's probably your program's fault.
==957367== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957367== i.e. it's Valgrind's fault. If you think this is the case or
==957367== you are not sure, please let us know and we'll try to fix it.
==957367== Either way, Valgrind will now raise a SIGILL signal which will
==957367== probably kill your program.
Start 260: FunctionalBoundaryTrace_Dispatch_Galerkin_AD_btest_memcheck
130/984 Test #260: FunctionalBoundaryTrace_Dispatch_Galerkin_AD_btest_memcheck ...............................................***Exception: Illegal 11.13 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x8F 0x3C 0x32 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957511== valgrind: Unrecognised instruction at address 0x9a84ef.
==957511== Your program just tried to execute an instruction that Valgrind
==957511== did not recognise. There are two possible reasons for this.
==957511== 1. Your program has a bug and erroneously jumped to a non-code
==957511== location. If you are running Memcheck and you just saw a
==957511== warning about a bad jump, it's probably your program's fault.
==957511== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957511== i.e. it's Valgrind's fault. If you think this is the case or
==957511== you are not sure, please let us know and we'll try to fix it.
==957511== Either way, Valgrind will now raise a SIGILL signal which will
==957511== probably kill your program.
Start 262: FunctionalBoundaryTrace_Galerkin_btest_memcheck
131/984 Test #262: FunctionalBoundaryTrace_Galerkin_btest_memcheck ...........................................................***Exception: Illegal 11.07 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xF 0xB 0x29 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==957701== valgrind: Unrecognised instruction at address 0x8d266f.
==957701== Your program just tried to execute an instruction that Valgrind
==957701== did not recognise. There are two possible reasons for this.
==957701== 1. Your program has a bug and erroneously jumped to a non-code
==957701== location. If you are running Memcheck and you just saw a
==957701== warning about a bad jump, it's probably your program's fault.
==957701== 2. The instruction is legitimate but Valgrind doesn't handle it,
==957701== i.e. it's Valgrind's fault. If you think this is the case or
==957701== you are not sure, please let us know and we'll try to fix it.
==957701== Either way, Valgrind will now raise a SIGILL signal which will
==957701== probably kill your program.
Start 264: FunctionalBoundaryTrace_WeightedResidual_Galerkin_btest_memcheck
132/984 Test #264: FunctionalBoundaryTrace_WeightedResidual_Galerkin_btest_memcheck ..........................................***Exception: Illegal 11.07 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x8F 0x8 0x29 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==958283== valgrind: Unrecognised instruction at address 0x8ce90f.
==958283== Your program just tried to execute an instruction that Valgrind
==958283== did not recognise. There are two possible reasons for this.
==958283== 1. Your program has a bug and erroneously jumped to a non-code
==958283== location. If you are running Memcheck and you just saw a
==958283== warning about a bad jump, it's probably your program's fault.
==958283== 2. The instruction is legitimate but Valgrind doesn't handle it,
==958283== i.e. it's Valgrind's fault. If you think this is the case or
==958283== you are not sure, please let us know and we'll try to fix it.
==958283== Either way, Valgrind will now raise a SIGILL signal which will
==958283== probably kill your program.
Start 266: FunctionalCell_Galerkin_btest_memcheck
133/984 Test #266: FunctionalCell_Galerkin_btest_memcheck ....................................................................***Exception: Illegal 26.52 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x57 0xC0 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==958989== valgrind: Unrecognised instruction at address 0xa640ef.
==958989== Your program just tried to execute an instruction that Valgrind
==958989== did not recognise. There are two possible reasons for this.
==958989== 1. Your program has a bug and erroneously jumped to a non-code
==958989== location. If you are running Memcheck and you just saw a
==958989== warning about a bad jump, it's probably your program's fault.
==958989== 2. The instruction is legitimate but Valgrind doesn't handle it,
==958989== i.e. it's Valgrind's fault. If you think this is the case or
==958989== you are not sure, please let us know and we'll try to fix it.
==958989== Either way, Valgrind will now raise a SIGILL signal which will
==958989== probably kill your program.
Start 268: IntegrandBoundaryTrace_Dirichlet_Galerkin_HSM2D_btest_memcheck
134/984 Test #268: IntegrandBoundaryTrace_Dirichlet_Galerkin_HSM2D_btest_memcheck ............................................***Exception: Illegal 10.99 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xDF 0x8D 0xC 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==959379== valgrind: Unrecognised instruction at address 0x5034cf.
==959379== Your program just tried to execute an instruction that Valgrind
==959379== did not recognise. There are two possible reasons for this.
==959379== 1. Your program has a bug and erroneously jumped to a non-code
==959379== location. If you are running Memcheck and you just saw a
==959379== warning about a bad jump, it's probably your program's fault.
==959379== 2. The instruction is legitimate but Valgrind doesn't handle it,
==959379== i.e. it's Valgrind's fault. If you think this is the case or
==959379== you are not sure, please let us know and we'll try to fix it.
==959379== Either way, Valgrind will now raise a SIGILL signal which will
==959379== probably kill your program.
Start 270: IntegrandBoundaryTrace_Dirichlet_mitLG_Galerkin_AD_btest_memcheck
135/984 Test #270: IntegrandBoundaryTrace_Dirichlet_mitLG_Galerkin_AD_btest_memcheck .........................................***Exception: Illegal 11.19 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7F 0x2D 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==959519== valgrind: Unrecognised instruction at address 0x4fc42f.
==959519== Your program just tried to execute an instruction that Valgrind
==959519== did not recognise. There are two possible reasons for this.
==959519== 1. Your program has a bug and erroneously jumped to a non-code
==959519== location. If you are running Memcheck and you just saw a
==959519== warning about a bad jump, it's probably your program's fault.
==959519== 2. The instruction is legitimate but Valgrind doesn't handle it,
==959519== i.e. it's Valgrind's fault. If you think this is the case or
==959519== you are not sure, please let us know and we'll try to fix it.
==959519== Either way, Valgrind will now raise a SIGILL signal which will
==959519== probably kill your program.
Start 272: IntegrandBoundaryTrace_Dirichlet_mitLG_Galerkin_Euler_btest_memcheck
136/984 Test #272: IntegrandBoundaryTrace_Dirichlet_mitLG_Galerkin_Euler_btest_memcheck ......................................***Failed 8.87 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 274: IntegrandBoundaryTrace_Dirichlet_mitState_Galerkin_Euler_btest_memcheck
137/984 Test #274: IntegrandBoundaryTrace_Dirichlet_mitState_Galerkin_Euler_btest_memcheck ...................................***Exception: Illegal 10.97 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xDF 0x7B 0xE 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==960179== valgrind: Unrecognised instruction at address 0x5035af.
==960179== Your program just tried to execute an instruction that Valgrind
==960179== did not recognise. There are two possible reasons for this.
==960179== 1. Your program has a bug and erroneously jumped to a non-code
==960179== location. If you are running Memcheck and you just saw a
==960179== warning about a bad jump, it's probably your program's fault.
==960179== 2. The instruction is legitimate but Valgrind doesn't handle it,
==960179== i.e. it's Valgrind's fault. If you think this is the case or
==960179== you are not sure, please let us know and we'll try to fix it.
==960179== Either way, Valgrind will now raise a SIGILL signal which will
==960179== probably kill your program.
Start 276: IntegrandBoundaryTrace_Dirichlet_sansLG_Galerkin_Euler_btest_memcheck
138/984 Test #276: IntegrandBoundaryTrace_Dirichlet_sansLG_Galerkin_Euler_btest_memcheck .....................................***Exception: Illegal 26.36 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xD7 0x7E 0xE 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==960305== valgrind: Unrecognised instruction at address 0x50a42f.
==960305== Your program just tried to execute an instruction that Valgrind
==960305== did not recognise. There are two possible reasons for this.
==960305== 1. Your program has a bug and erroneously jumped to a non-code
==960305== location. If you are running Memcheck and you just saw a
==960305== warning about a bad jump, it's probably your program's fault.
==960305== 2. The instruction is legitimate but Valgrind doesn't handle it,
==960305== i.e. it's Valgrind's fault. If you think this is the case or
==960305== you are not sure, please let us know and we'll try to fix it.
==960305== Either way, Valgrind will now raise a SIGILL signal which will
==960305== probably kill your program.
Start 278: IntegrandBoundaryTrace_Flux_mitState_Nitsche_AD_btest_memcheck
139/984 Test #278: IntegrandBoundaryTrace_Flux_mitState_Nitsche_AD_btest_memcheck ............................................***Exception: Illegal 11.15 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xE7 0x75 0x1A 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==960616== valgrind: Unrecognised instruction at address 0x5e0b6f.
==960616== Your program just tried to execute an instruction that Valgrind
==960616== did not recognise. There are two possible reasons for this.
==960616== 1. Your program has a bug and erroneously jumped to a non-code
==960616== location. If you are running Memcheck and you just saw a
==960616== warning about a bad jump, it's probably your program's fault.
==960616== 2. The instruction is legitimate but Valgrind doesn't handle it,
==960616== i.e. it's Valgrind's fault. If you think this is the case or
==960616== you are not sure, please let us know and we'll try to fix it.
==960616== Either way, Valgrind will now raise a SIGILL signal which will
==960616== probably kill your program.
Start 280: IntegrandBoundaryTrace_LinearScalar_mitLG_Galerkin_AD_btest_memcheck
140/984 Test #280: IntegrandBoundaryTrace_LinearScalar_mitLG_Galerkin_AD_btest_memcheck ......................................***Exception: Illegal 11.13 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xAF 0xCE 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==960886== valgrind: Unrecognised instruction at address 0x5b242f.
==960886== Your program just tried to execute an instruction that Valgrind
==960886== did not recognise. There are two possible reasons for this.
==960886== 1. Your program has a bug and erroneously jumped to a non-code
==960886== location. If you are running Memcheck and you just saw a
==960886== warning about a bad jump, it's probably your program's fault.
==960886== 2. The instruction is legitimate but Valgrind doesn't handle it,
==960886== i.e. it's Valgrind's fault. If you think this is the case or
==960886== you are not sure, please let us know and we'll try to fix it.
==960886== Either way, Valgrind will now raise a SIGILL signal which will
==960886== probably kill your program.
Start 282: IntegrandBoundaryTrace_LinearScalar_sansLG_Galerkin_AD_btest_memcheck
141/984 Test #282: IntegrandBoundaryTrace_LinearScalar_sansLG_Galerkin_AD_btest_memcheck .....................................***Exception: Illegal 11.14 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xCF 0xCC 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==961183== valgrind: Unrecognised instruction at address 0x58650f.
==961183== Your program just tried to execute an instruction that Valgrind
==961183== did not recognise. There are two possible reasons for this.
==961183== 1. Your program has a bug and erroneously jumped to a non-code
==961183== location. If you are running Memcheck and you just saw a
==961183== warning about a bad jump, it's probably your program's fault.
==961183== 2. The instruction is legitimate but Valgrind doesn't handle it,
==961183== i.e. it's Valgrind's fault. If you think this is the case or
==961183== you are not sure, please let us know and we'll try to fix it.
==961183== Either way, Valgrind will now raise a SIGILL signal which will
==961183== probably kill your program.
Start 284: IntegrandBoundaryTrace_None_Galerkin_AD_btest_memcheck
142/984 Test #284: IntegrandBoundaryTrace_None_Galerkin_AD_btest_memcheck ....................................................***Exception: Illegal 11.14 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xF7 0xD3 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==961312== valgrind: Unrecognised instruction at address 0x593d4f.
==961312== Your program just tried to execute an instruction that Valgrind
==961312== did not recognise. There are two possible reasons for this.
==961312== 1. Your program has a bug and erroneously jumped to a non-code
==961312== location. If you are running Memcheck and you just saw a
==961312== warning about a bad jump, it's probably your program's fault.
==961312== 2. The instruction is legitimate but Valgrind doesn't handle it,
==961312== i.e. it's Valgrind's fault. If you think this is the case or
==961312== you are not sure, please let us know and we'll try to fix it.
==961312== Either way, Valgrind will now raise a SIGILL signal which will
==961312== probably kill your program.
Start 286: IntegrandBoundaryTrace_Output_Galerkin_btest_memcheck
143/984 Test #286: IntegrandBoundaryTrace_Output_Galerkin_btest_memcheck .....................................................***Exception: Illegal 15.59 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x8F 0x7D 0xE 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==961541== valgrind: Unrecognised instruction at address 0x5063ef.
==961541== Your program just tried to execute an instruction that Valgrind
==961541== did not recognise. There are two possible reasons for this.
==961541== 1. Your program has a bug and erroneously jumped to a non-code
==961541== location. If you are running Memcheck and you just saw a
==961541== warning about a bad jump, it's probably your program's fault.
==961541== 2. The instruction is legitimate but Valgrind doesn't handle it,
==961541== i.e. it's Valgrind's fault. If you think this is the case or
==961541== you are not sure, please let us know and we'll try to fix it.
==961541== Either way, Valgrind will now raise a SIGILL signal which will
==961541== probably kill your program.
Start 288: IntegrandBoundaryTrace_Robin_sansLG_Galerkin_IncNS_btest_memcheck
144/984 Test #288: IntegrandBoundaryTrace_Robin_sansLG_Galerkin_IncNS_btest_memcheck .........................................***Failed 9.04 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 290: IntegrandBoundaryTrace_Robin_sansLG_Galerkin_IncRANSSA_btest_memcheck
145/984 Test #290: IntegrandBoundaryTrace_Robin_sansLG_Galerkin_IncRANSSA_btest_memcheck .....................................***Failed 9.08 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 292: IntegrandCell_Galerkin_AD_btest_memcheck
146/984 Test #292: IntegrandCell_Galerkin_AD_btest_memcheck ..................................................................***Exception: Illegal 11.19 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x87 0xC2 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==961911== valgrind: Unrecognised instruction at address 0x5872cf.
==961911== Your program just tried to execute an instruction that Valgrind
==961911== did not recognise. There are two possible reasons for this.
==961911== 1. Your program has a bug and erroneously jumped to a non-code
==961911== location. If you are running Memcheck and you just saw a
==961911== warning about a bad jump, it's probably your program's fault.
==961911== 2. The instruction is legitimate but Valgrind doesn't handle it,
==961911== i.e. it's Valgrind's fault. If you think this is the case or
==961911== you are not sure, please let us know and we'll try to fix it.
==961911== Either way, Valgrind will now raise a SIGILL signal which will
==961911== probably kill your program.
Start 294: IntegrandCell_Galerkin_BDF_AD_btest_memcheck
147/984 Test #294: IntegrandCell_Galerkin_BDF_AD_btest_memcheck ..............................................................***Exception: Illegal 20.22 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xE7 0x1D 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==962502== valgrind: Unrecognised instruction at address 0x4fd3cf.
==962502== Your program just tried to execute an instruction that Valgrind
==962502== did not recognise. There are two possible reasons for this.
==962502== 1. Your program has a bug and erroneously jumped to a non-code
==962502== location. If you are running Memcheck and you just saw a
==962502== warning about a bad jump, it's probably your program's fault.
==962502== 2. The instruction is legitimate but Valgrind doesn't handle it,
==962502== i.e. it's Valgrind's fault. If you think this is the case or
==962502== you are not sure, please let us know and we'll try to fix it.
==962502== Either way, Valgrind will now raise a SIGILL signal which will
==962502== probably kill your program.
Start 296: IntegrandCell_Galerkin_CR_btest_memcheck
148/984 Test #296: IntegrandCell_Galerkin_CR_btest_memcheck ..................................................................***Exception: Illegal 10.99 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xF7 0x1 0xF 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==963779== valgrind: Unrecognised instruction at address 0x4b5f4f.
==963779== Your program just tried to execute an instruction that Valgrind
==963779== did not recognise. There are two possible reasons for this.
==963779== 1. Your program has a bug and erroneously jumped to a non-code
==963779== location. If you are running Memcheck and you just saw a
==963779== warning about a bad jump, it's probably your program's fault.
==963779== 2. The instruction is legitimate but Valgrind doesn't handle it,
==963779== i.e. it's Valgrind's fault. If you think this is the case or
==963779== you are not sure, please let us know and we'll try to fix it.
==963779== Either way, Valgrind will now raise a SIGILL signal which will
==963779== probably kill your program.
Start 298: IntegrandCell_Galerkin_Conservative_btest_memcheck
149/984 Test #298: IntegrandCell_Galerkin_Conservative_btest_memcheck ........................................................***Exception: Illegal 11.02 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x87 0x39 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==963923== valgrind: Unrecognised instruction at address 0x4da82f.
==963923== Your program just tried to execute an instruction that Valgrind
==963923== did not recognise. There are two possible reasons for this.
==963923== 1. Your program has a bug and erroneously jumped to a non-code
==963923== location. If you are running Memcheck and you just saw a
==963923== warning about a bad jump, it's probably your program's fault.
==963923== 2. The instruction is legitimate but Valgrind doesn't handle it,
==963923== i.e. it's Valgrind's fault. If you think this is the case or
==963923== you are not sure, please let us know and we'll try to fix it.
==963923== Either way, Valgrind will now raise a SIGILL signal which will
==963923== probably kill your program.
Start 300: IntegrandCell_Galerkin_HB_AD_btest_memcheck
150/984 Test #300: IntegrandCell_Galerkin_HB_AD_btest_memcheck ...............................................................***Failed 8.97 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 302: IntegrandCell_Galerkin_HSM2D_btest_memcheck
151/984 Test #302: IntegrandCell_Galerkin_HSM2D_btest_memcheck ...............................................................***Exception: Illegal 24.01 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x6F 0x40 0x1B 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==964571== valgrind: Unrecognised instruction at address 0x51572f.
==964571== Your program just tried to execute an instruction that Valgrind
==964571== did not recognise. There are two possible reasons for this.
==964571== 1. Your program has a bug and erroneously jumped to a non-code
==964571== location. If you are running Memcheck and you just saw a
==964571== warning about a bad jump, it's probably your program's fault.
==964571== 2. The instruction is legitimate but Valgrind doesn't handle it,
==964571== i.e. it's Valgrind's fault. If you think this is the case or
==964571== you are not sure, please let us know and we'll try to fix it.
==964571== Either way, Valgrind will now raise a SIGILL signal which will
==964571== probably kill your program.
Start 304: IntegrandCell_Galerkin_HSMKL_btest_memcheck
152/984 Test #304: IntegrandCell_Galerkin_HSMKL_btest_memcheck ...............................................................***Exception: Illegal 25.76 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xD7 0x60 0x12 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==964916== valgrind: Unrecognised instruction at address 0x4c954f.
==964916== Your program just tried to execute an instruction that Valgrind
==964916== did not recognise. There are two possible reasons for this.
==964916== 1. Your program has a bug and erroneously jumped to a non-code
==964916== location. If you are running Memcheck and you just saw a
==964916== warning about a bad jump, it's probably your program's fault.
==964916== 2. The instruction is legitimate but Valgrind doesn't handle it,
==964916== i.e. it's Valgrind's fault. If you think this is the case or
==964916== you are not sure, please let us know and we'll try to fix it.
==964916== Either way, Valgrind will now raise a SIGILL signal which will
==964916== probably kill your program.
Start 306: IntegrandCell_Galerkin_IRS_AD_btest_memcheck
153/984 Test #306: IntegrandCell_Galerkin_IRS_AD_btest_memcheck ..............................................................***Exception: Illegal 11.05 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xD7 0x12 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==965174== valgrind: Unrecognised instruction at address 0x505e6f.
==965174== Your program just tried to execute an instruction that Valgrind
==965174== did not recognise. There are two possible reasons for this.
==965174== 1. Your program has a bug and erroneously jumped to a non-code
==965174== location. If you are running Memcheck and you just saw a
==965174== warning about a bad jump, it's probably your program's fault.
==965174== 2. The instruction is legitimate but Valgrind doesn't handle it,
==965174== i.e. it's Valgrind's fault. If you think this is the case or
==965174== you are not sure, please let us know and we'll try to fix it.
==965174== Either way, Valgrind will now raise a SIGILL signal which will
==965174== probably kill your program.
Start 308: IntegrandCell_Galerkin_Output_AD_btest_memcheck
154/984 Test #308: IntegrandCell_Galerkin_Output_AD_btest_memcheck ...........................................................***Exception: Illegal 20.71 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x1F 0x80 0x13 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==965372== valgrind: Unrecognised instruction at address 0x51314f.
==965372== Your program just tried to execute an instruction that Valgrind
==965372== did not recognise. There are two possible reasons for this.
==965372== 1. Your program has a bug and erroneously jumped to a non-code
==965372== location. If you are running Memcheck and you just saw a
==965372== warning about a bad jump, it's probably your program's fault.
==965372== 2. The instruction is legitimate but Valgrind doesn't handle it,
==965372== i.e. it's Valgrind's fault. If you think this is the case or
==965372== you are not sure, please let us know and we'll try to fix it.
==965372== Either way, Valgrind will now raise a SIGILL signal which will
==965372== probably kill your program.
Start 310: IntegrandCell_Galerkin_Output_Stabilized_AD_btest_memcheck
155/984 Test #310: IntegrandCell_Galerkin_Output_Stabilized_AD_btest_memcheck ................................................***Exception: Illegal 26.03 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x97 0xC5 0x16 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==965603== valgrind: Unrecognised instruction at address 0x546baf.
==965603== Your program just tried to execute an instruction that Valgrind
==965603== did not recognise. There are two possible reasons for this.
==965603== 1. Your program has a bug and erroneously jumped to a non-code
==965603== location. If you are running Memcheck and you just saw a
==965603== warning about a bad jump, it's probably your program's fault.
==965603== 2. The instruction is legitimate but Valgrind doesn't handle it,
==965603== i.e. it's Valgrind's fault. If you think this is the case or
==965603== you are not sure, please let us know and we'll try to fix it.
==965603== Either way, Valgrind will now raise a SIGILL signal which will
==965603== probably kill your program.
Start 312: IntegrandCell_Galerkin_PTC_AD_btest_memcheck
156/984 Test #312: IntegrandCell_Galerkin_PTC_AD_btest_memcheck ..............................................................***Exception: Illegal 11.00 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xB7 0x15 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==965945== valgrind: Unrecognised instruction at address 0x502b8f.
==965945== Your program just tried to execute an instruction that Valgrind
==965945== did not recognise. There are two possible reasons for this.
==965945== 1. Your program has a bug and erroneously jumped to a non-code
==965945== location. If you are running Memcheck and you just saw a
==965945== warning about a bad jump, it's probably your program's fault.
==965945== 2. The instruction is legitimate but Valgrind doesn't handle it,
==965945== i.e. it's Valgrind's fault. If you think this is the case or
==965945== you are not sure, please let us know and we'll try to fix it.
==965945== Either way, Valgrind will now raise a SIGILL signal which will
==965945== probably kill your program.
Start 314: IntegrandCell_Galerkin_ShallowWater1D_btest_memcheck
157/984 Test #314: IntegrandCell_Galerkin_ShallowWater1D_btest_memcheck ......................................................***Failed 9.04 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 316: IntegrandCell_Galerkin_Stabilized_AD_btest_memcheck
158/984 Test #316: IntegrandCell_Galerkin_Stabilized_AD_btest_memcheck .......................................................***Exception: Illegal 11.18 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xF 0x1A 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==966227== valgrind: Unrecognised instruction at address 0x51d72f.
==966227== Your program just tried to execute an instruction that Valgrind
==966227== did not recognise. There are two possible reasons for this.
==966227== 1. Your program has a bug and erroneously jumped to a non-code
==966227== location. If you are running Memcheck and you just saw a
==966227== warning about a bad jump, it's probably your program's fault.
==966227== 2. The instruction is legitimate but Valgrind doesn't handle it,
==966227== i.e. it's Valgrind's fault. If you think this is the case or
==966227== you are not sure, please let us know and we'll try to fix it.
==966227== Either way, Valgrind will now raise a SIGILL signal which will
==966227== probably kill your program.
Start 318: IntegrandCell_Galerkin_Stabilized_Corrected_AD_btest_memcheck
159/984 Test #318: IntegrandCell_Galerkin_Stabilized_Corrected_AD_btest_memcheck .............................................***Exception: Illegal 15.95 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xB7 0xDC 0x7 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==966384== valgrind: Unrecognised instruction at address 0x4c248f.
==966384== Your program just tried to execute an instruction that Valgrind
==966384== did not recognise. There are two possible reasons for this.
==966384== 1. Your program has a bug and erroneously jumped to a non-code
==966384== location. If you are running Memcheck and you just saw a
==966384== warning about a bad jump, it's probably your program's fault.
==966384== 2. The instruction is legitimate but Valgrind doesn't handle it,
==966384== i.e. it's Valgrind's fault. If you think this is the case or
==966384== you are not sure, please let us know and we'll try to fix it.
==966384== Either way, Valgrind will now raise a SIGILL signal which will
==966384== probably kill your program.
Start 320: IntegrandCell_Galerkin_Stabilized_NS_btest_memcheck
160/984 Test #320: IntegrandCell_Galerkin_Stabilized_NS_btest_memcheck .......................................................***Exception: Illegal 10.96 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xAF 0xC6 0x13 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==966808== valgrind: Unrecognised instruction at address 0x4cbb2f.
==966808== Your program just tried to execute an instruction that Valgrind
==966808== did not recognise. There are two possible reasons for this.
==966808== 1. Your program has a bug and erroneously jumped to a non-code
==966808== location. If you are running Memcheck and you just saw a
==966808== warning about a bad jump, it's probably your program's fault.
==966808== 2. The instruction is legitimate but Valgrind doesn't handle it,
==966808== i.e. it's Valgrind's fault. If you think this is the case or
==966808== you are not sure, please let us know and we'll try to fix it.
==966808== Either way, Valgrind will now raise a SIGILL signal which will
==966808== probably kill your program.
Start 322: IntegrandCell_Galerkin_StrongForm_AD_btest_memcheck
161/984 Test #322: IntegrandCell_Galerkin_StrongForm_AD_btest_memcheck .......................................................***Exception: Illegal 24.45 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x1F 0x17 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==967013== valgrind: Unrecognised instruction at address 0x503caf.
==967013== Your program just tried to execute an instruction that Valgrind
==967013== did not recognise. There are two possible reasons for this.
==967013== 1. Your program has a bug and erroneously jumped to a non-code
==967013== location. If you are running Memcheck and you just saw a
==967013== warning about a bad jump, it's probably your program's fault.
==967013== 2. The instruction is legitimate but Valgrind doesn't handle it,
==967013== i.e. it's Valgrind's fault. If you think this is the case or
==967013== you are not sure, please let us know and we'll try to fix it.
==967013== Either way, Valgrind will now raise a SIGILL signal which will
==967013== probably kill your program.
Start 324: IntegrandCell_ProjectFunction_btest_memcheck
162/984 Test #324: IntegrandCell_ProjectFunction_btest_memcheck ..............................................................***Exception: Illegal 11.18 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x8F 0x47 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==967400== valgrind: Unrecognised instruction at address 0x506e6f.
==967400== Your program just tried to execute an instruction that Valgrind
==967400== did not recognise. There are two possible reasons for this.
==967400== 1. Your program has a bug and erroneously jumped to a non-code
==967400== location. If you are running Memcheck and you just saw a
==967400== warning about a bad jump, it's probably your program's fault.
==967400== 2. The instruction is legitimate but Valgrind doesn't handle it,
==967400== i.e. it's Valgrind's fault. If you think this is the case or
==967400== you are not sure, please let us know and we'll try to fix it.
==967400== Either way, Valgrind will now raise a SIGILL signal which will
==967400== probably kill your program.
Start 326: IntegrandCell_Project_btest_memcheck
163/984 Test #326: IntegrandCell_Project_btest_memcheck ......................................................................***Exception: Illegal 11.15 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x17 0xF5 0x7 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==967577== valgrind: Unrecognised instruction at address 0x4cbc2f.
==967577== Your program just tried to execute an instruction that Valgrind
==967577== did not recognise. There are two possible reasons for this.
==967577== 1. Your program has a bug and erroneously jumped to a non-code
==967577== location. If you are running Memcheck and you just saw a
==967577== warning about a bad jump, it's probably your program's fault.
==967577== 2. The instruction is legitimate but Valgrind doesn't handle it,
==967577== i.e. it's Valgrind's fault. If you think this is the case or
==967577== you are not sure, please let us know and we'll try to fix it.
==967577== Either way, Valgrind will now raise a SIGILL signal which will
==967577== probably kill your program.
Start 328: IntegrandInteriorTrace_Galerkin_AD_btest_memcheck
164/984 Test #328: IntegrandInteriorTrace_Galerkin_AD_btest_memcheck .........................................................***Exception: Illegal 10.97 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xBF 0x90 0x1A 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==967774== valgrind: Unrecognised instruction at address 0x5d008f.
==967774== Your program just tried to execute an instruction that Valgrind
==967774== did not recognise. There are two possible reasons for this.
==967774== 1. Your program has a bug and erroneously jumped to a non-code
==967774== location. If you are running Memcheck and you just saw a
==967774== warning about a bad jump, it's probably your program's fault.
==967774== 2. The instruction is legitimate but Valgrind doesn't handle it,
==967774== i.e. it's Valgrind's fault. If you think this is the case or
==967774== you are not sure, please let us know and we'll try to fix it.
==967774== Either way, Valgrind will now raise a SIGILL signal which will
==967774== probably kill your program.
Start 330: IntegrandInteriorTrace_Galerkin_CR_btest_memcheck
165/984 Test #330: IntegrandInteriorTrace_Galerkin_CR_btest_memcheck .........................................................***Exception: Illegal 11.16 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7F 0x14 0xB 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==968035== valgrind: Unrecognised instruction at address 0x510ccf.
==968035== Your program just tried to execute an instruction that Valgrind
==968035== did not recognise. There are two possible reasons for this.
==968035== 1. Your program has a bug and erroneously jumped to a non-code
==968035== location. If you are running Memcheck and you just saw a
==968035== warning about a bad jump, it's probably your program's fault.
==968035== 2. The instruction is legitimate but Valgrind doesn't handle it,
==968035== i.e. it's Valgrind's fault. If you think this is the case or
==968035== you are not sure, please let us know and we'll try to fix it.
==968035== Either way, Valgrind will now raise a SIGILL signal which will
==968035== probably kill your program.
Start 332: IntegrandInteriorTrace_Galerkin_StrongForm_AD_btest_memcheck
166/984 Test #332: IntegrandInteriorTrace_Galerkin_StrongForm_AD_btest_memcheck ..............................................***Exception: Illegal 11.12 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xCF 0xAF 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==968504== valgrind: Unrecognised instruction at address 0x58818f.
==968504== Your program just tried to execute an instruction that Valgrind
==968504== did not recognise. There are two possible reasons for this.
==968504== 1. Your program has a bug and erroneously jumped to a non-code
==968504== location. If you are running Memcheck and you just saw a
==968504== warning about a bad jump, it's probably your program's fault.
==968504== 2. The instruction is legitimate but Valgrind doesn't handle it,
==968504== i.e. it's Valgrind's fault. If you think this is the case or
==968504== you are not sure, please let us know and we'll try to fix it.
==968504== Either way, Valgrind will now raise a SIGILL signal which will
==968504== probably kill your program.
Start 334: IntegrandInteriorTrace_SIP_Galerkin_AD_btest_memcheck
167/984 Test #334: IntegrandInteriorTrace_SIP_Galerkin_AD_btest_memcheck .....................................................***Exception: Illegal 23.02 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xAF 0xBA 0x11 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==968844== valgrind: Unrecognised instruction at address 0x57a68f.
==968844== Your program just tried to execute an instruction that Valgrind
==968844== did not recognise. There are two possible reasons for this.
==968844== 1. Your program has a bug and erroneously jumped to a non-code
==968844== location. If you are running Memcheck and you just saw a
==968844== warning about a bad jump, it's probably your program's fault.
==968844== 2. The instruction is legitimate but Valgrind doesn't handle it,
==968844== i.e. it's Valgrind's fault. If you think this is the case or
==968844== you are not sure, please let us know and we'll try to fix it.
==968844== Either way, Valgrind will now raise a SIGILL signal which will
==968844== probably kill your program.
Start 336: IntegrateBoundaryTrace_Dispatch_Galerkin_AD_1D_btest_memcheck
168/984 Test #336: IntegrateBoundaryTrace_Dispatch_Galerkin_AD_1D_btest_memcheck .............................................***Failed 9.32 sec
Please verify that both the operating system and the processor support Intel(R) AVX512F, AVX512DQ, ADX, AVX512CD, AVX512BW, AVX512VL and AVX512_VNNI instructions.
--> build quadrature store for simplex, category = 1
--> build quadrature store for simplex, category = 2
--> build quadrature store for simplex, category = 0
Start 338: JacobianBoundaryTrace_Dirichlet_mitLG_Galerkin_AD_btest_memcheck
169/984 Test #338: JacobianBoundaryTrace_Dirichlet_mitLG_Galerkin_AD_btest_memcheck ..........................................***Exception: Illegal 22.48 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x37 0xCE 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==969609== valgrind: Unrecognised instruction at address 0x91c7ef.
==969609== Your program just tried to execute an instruction that Valgrind
==969609== did not recognise. There are two possible reasons for this.
==969609== 1. Your program has a bug and erroneously jumped to a non-code
==969609== location. If you are running Memcheck and you just saw a
==969609== warning about a bad jump, it's probably your program's fault.
==969609== 2. The instruction is legitimate but Valgrind doesn't handle it,
==969609== i.e. it's Valgrind's fault. If you think this is the case or
==969609== you are not sure, please let us know and we'll try to fix it.
==969609== Either way, Valgrind will now raise a SIGILL signal which will
==969609== probably kill your program.
Start 340: JacobianBoundaryTrace_LinearScalar_mitLG_Galerkin_AD_btest_memcheck
170/984 Test #340: JacobianBoundaryTrace_LinearScalar_mitLG_Galerkin_AD_btest_memcheck .......................................***Exception: Illegal 23.60 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xA7 0x7E 0x38 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==969835== valgrind: Unrecognised instruction at address 0xd807af.
==969835== Your program just tried to execute an instruction that Valgrind
==969835== did not recognise. There are two possible reasons for this.
==969835== 1. Your program has a bug and erroneously jumped to a non-code
==969835== location. If you are running Memcheck and you just saw a
==969835== warning about a bad jump, it's probably your program's fault.
==969835== 2. The instruction is legitimate but Valgrind doesn't handle it,
==969835== i.e. it's Valgrind's fault. If you think this is the case or
==969835== you are not sure, please let us know and we'll try to fix it.
==969835== Either way, Valgrind will now raise a SIGILL signal which will
==969835== probably kill your program.
Start 342: JacobianBoundaryTrace_LinearScalar_sansLG_Galerkin_AD_btest_memcheck
171/984 Test #342: JacobianBoundaryTrace_LinearScalar_sansLG_Galerkin_AD_btest_memcheck ......................................***Exception: Illegal 26.27 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7 0x77 0x38 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==970262== valgrind: Unrecognised instruction at address 0xcfcf4f.
==970262== Your program just tried to execute an instruction that Valgrind
==970262== did not recognise. There are two possible reasons for this.
==970262== 1. Your program has a bug and erroneously jumped to a non-code
==970262== location. If you are running Memcheck and you just saw a
==970262== warning about a bad jump, it's probably your program's fault.
==970262== 2. The instruction is legitimate but Valgrind doesn't handle it,
==970262== i.e. it's Valgrind's fault. If you think this is the case or
==970262== you are not sure, please let us know and we'll try to fix it.
==970262== Either way, Valgrind will now raise a SIGILL signal which will
==970262== probably kill your program.
Start 344: JacobianCell_Galerkin_AD_ArtificialViscosity_btest_memcheck
172/984 Test #344: JacobianCell_Galerkin_AD_ArtificialViscosity_btest_memcheck ...............................................***Exception: Illegal 25.05 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xF 0x4 0x26 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==971188== valgrind: Unrecognised instruction at address 0x980d6f.
==971188== Your program just tried to execute an instruction that Valgrind
==971188== did not recognise. There are two possible reasons for this.
==971188== 1. Your program has a bug and erroneously jumped to a non-code
==971188== location. If you are running Memcheck and you just saw a
==971188== warning about a bad jump, it's probably your program's fault.
==971188== 2. The instruction is legitimate but Valgrind doesn't handle it,
==971188== i.e. it's Valgrind's fault. If you think this is the case or
==971188== you are not sure, please let us know and we'll try to fix it.
==971188== Either way, Valgrind will now raise a SIGILL signal which will
==971188== probably kill your program.
Start 346: JacobianCell_Galerkin_AD_btest_memcheck
173/984 Test #346: JacobianCell_Galerkin_AD_btest_memcheck ...................................................................***Exception: Illegal 22.31 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7F 0xE9 0x36 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==971621== valgrind: Unrecognised instruction at address 0xe867cf.
==971621== Your program just tried to execute an instruction that Valgrind
==971621== did not recognise. There are two possible reasons for this.
==971621== 1. Your program has a bug and erroneously jumped to a non-code
==971621== location. If you are running Memcheck and you just saw a
==971621== warning about a bad jump, it's probably your program's fault.
==971621== 2. The instruction is legitimate but Valgrind doesn't handle it,
==971621== i.e. it's Valgrind's fault. If you think this is the case or
==971621== you are not sure, please let us know and we'll try to fix it.
==971621== Either way, Valgrind will now raise a SIGILL signal which will
==971621== probably kill your program.
Start 348: JacobianCell_Galerkin_BDF_AD_btest_memcheck
174/984 Test #348: JacobianCell_Galerkin_BDF_AD_btest_memcheck ...............................................................***Exception: Illegal 11.11 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7 0xA6 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==971898== valgrind: Unrecognised instruction at address 0xa49b8f.
==971898== Your program just tried to execute an instruction that Valgrind
==971898== did not recognise. There are two possible reasons for this.
==971898== 1. Your program has a bug and erroneously jumped to a non-code
==971898== location. If you are running Memcheck and you just saw a
==971898== warning about a bad jump, it's probably your program's fault.
==971898== 2. The instruction is legitimate but Valgrind doesn't handle it,
==971898== i.e. it's Valgrind's fault. If you think this is the case or
==971898== you are not sure, please let us know and we'll try to fix it.
==971898== Either way, Valgrind will now raise a SIGILL signal which will
==971898== probably kill your program.
Start 350: JacobianCell_Galerkin_CR_btest_memcheck
175/984 Test #350: JacobianCell_Galerkin_CR_btest_memcheck ...................................................................***Exception: Illegal 11.16 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x77 0xAF 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==972070== valgrind: Unrecognised instruction at address 0x8ed1cf.
==972070== Your program just tried to execute an instruction that Valgrind
==972070== did not recognise. There are two possible reasons for this.
==972070== 1. Your program has a bug and erroneously jumped to a non-code
==972070== location. If you are running Memcheck and you just saw a
==972070== warning about a bad jump, it's probably your program's fault.
==972070== 2. The instruction is legitimate but Valgrind doesn't handle it,
==972070== i.e. it's Valgrind's fault. If you think this is the case or
==972070== you are not sure, please let us know and we'll try to fix it.
==972070== Either way, Valgrind will now raise a SIGILL signal which will
==972070== probably kill your program.
Start 352: JacobianCell_Galerkin_IRS_AD_btest_memcheck
176/984 Test #352: JacobianCell_Galerkin_IRS_AD_btest_memcheck ...............................................................***Exception: Illegal 11.09 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7 0xAA 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==972182== valgrind: Unrecognised instruction at address 0xa5378f.
==972182== Your program just tried to execute an instruction that Valgrind
==972182== did not recognise. There are two possible reasons for this.
==972182== 1. Your program has a bug and erroneously jumped to a non-code
==972182== location. If you are running Memcheck and you just saw a
==972182== warning about a bad jump, it's probably your program's fault.
==972182== 2. The instruction is legitimate but Valgrind doesn't handle it,
==972182== i.e. it's Valgrind's fault. If you think this is the case or
==972182== you are not sure, please let us know and we'll try to fix it.
==972182== Either way, Valgrind will now raise a SIGILL signal which will
==972182== probably kill your program.
Start 354: JacobianCell_Galerkin_PTC_AD_btest_memcheck
177/984 Test #354: JacobianCell_Galerkin_PTC_AD_btest_memcheck ...............................................................***Exception: Illegal 10.97 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x7 0xA1 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==972356== valgrind: Unrecognised instruction at address 0xa5008f.
==972356== Your program just tried to execute an instruction that Valgrind
==972356== did not recognise. There are two possible reasons for this.
==972356== 1. Your program has a bug and erroneously jumped to a non-code
==972356== location. If you are running Memcheck and you just saw a
==972356== warning about a bad jump, it's probably your program's fault.
==972356== 2. The instruction is legitimate but Valgrind doesn't handle it,
==972356== i.e. it's Valgrind's fault. If you think this is the case or
==972356== you are not sure, please let us know and we'll try to fix it.
==972356== Either way, Valgrind will now raise a SIGILL signal which will
==972356== probably kill your program.
Start 356: JacobianCell_Galerkin_Stabilized_AD_btest_memcheck
178/984 Test #356: JacobianCell_Galerkin_Stabilized_AD_btest_memcheck ........................................................***Exception: Illegal 23.27 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x57 0xEC 0x36 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==972482== valgrind: Unrecognised instruction at address 0xec558f.
==972482== Your program just tried to execute an instruction that Valgrind
==972482== did not recognise. There are two possible reasons for this.
==972482== 1. Your program has a bug and erroneously jumped to a non-code
==972482== location. If you are running Memcheck and you just saw a
==972482== warning about a bad jump, it's probably your program's fault.
==972482== 2. The instruction is legitimate but Valgrind doesn't handle it,
==972482== i.e. it's Valgrind's fault. If you think this is the case or
==972482== you are not sure, please let us know and we'll try to fix it.
==972482== Either way, Valgrind will now raise a SIGILL signal which will
==972482== probably kill your program.
Start 358: JacobianCell_Galerkin_Stabilized_NS_btest_memcheck
179/984 Test #358: JacobianCell_Galerkin_Stabilized_NS_btest_memcheck ........................................................***Exception: Illegal 11.33 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0xD7 0xDB 0x3E 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==972889== valgrind: Unrecognised instruction at address 0xc0070f.
==972889== Your program just tried to execute an instruction that Valgrind
==972889== did not recognise. There are two possible reasons for this.
==972889== 1. Your program has a bug and erroneously jumped to a non-code
==972889== location. If you are running Memcheck and you just saw a
==972889== warning about a bad jump, it's probably your program's fault.
==972889== 2. The instruction is legitimate but Valgrind doesn't handle it,
==972889== i.e. it's Valgrind's fault. If you think this is the case or
==972889== you are not sure, please let us know and we'll try to fix it.
==972889== Either way, Valgrind will now raise a SIGILL signal which will
==972889== probably kill your program.
Start 360: JacobianFunctionalBoundaryTrace_Galerkin_HSM2D_btest_memcheck
180/984 Test #360: JacobianFunctionalBoundaryTrace_Galerkin_HSM2D_btest_memcheck .............................................***Exception: Illegal 22.95 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x57 0xB0 0x25 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==973182== valgrind: Unrecognised instruction at address 0x8bb14f.
==973182== Your program just tried to execute an instruction that Valgrind
==973182== did not recognise. There are two possible reasons for this.
==973182== 1. Your program has a bug and erroneously jumped to a non-code
==973182== location. If you are running Memcheck and you just saw a
==973182== warning about a bad jump, it's probably your program's fault.
==973182== 2. The instruction is legitimate but Valgrind doesn't handle it,
==973182== i.e. it's Valgrind's fault. If you think this is the case or
==973182== you are not sure, please let us know and we'll try to fix it.
==973182== Either way, Valgrind will now raise a SIGILL signal which will
==973182== probably kill your program.
Start 362: JacobianFunctionalBoundaryTrace_WeightedResidual_Galerkin_btest_memcheck
181/984 Test #362: JacobianFunctionalBoundaryTrace_WeightedResidual_Galerkin_btest_memcheck ..................................***Exception: Illegal 11.12 sec
vex amd64->IR: unhandled instruction bytes: 0x62 0xF1 0xFD 0x18 0x54 0x5 0x57 0x5 0x29 0x0
vex amd64->IR: REX=0 REX.W=0 REX.R=0 REX.X=0 REX.B=0
vex amd64->IR: VEX=0 VEX.L=0 VEX.nVVVV=0x0 ESC=NONE
vex amd64->IR: PFX.66=0 PFX.F2=0 PFX.F3=0
==973864== valgrind: Unrecognised instruction at address 0x8ecc6f.
==973864== Your program just tried to execute an instruction that Valgrind
==973864== did not recognise. There are two possible reasons for this.
==973864== 1. Your program has a bug and erroneously jumped to a non-code
==973864== location. If you are running Memcheck and you just saw a
==973864== warning about a bad jump, it's probably your program's fault.
==973864== 2. The instruction is legitimate but Valgrind doesn't handle it,
==973864== i.e. it's Valgrind's fault. If you think this is the case or
==973864== you are not sure, please let us know and we'll try to fix it.
==973864== Either way, Valgrind will now raise a SIGILL signal which will
==973864== probably kill your program.
Start 364: JacobianFunctionalCell_Galerkin_btest_memcheck
Build was aborted
[GNU C Compiler (gcc)ClangIntel Compiler (C, Fortran)Vera++] Skipping execution of recorder since overall result is 'ABORTED'
[Valgrind] Files to copy:
[Valgrind] build/release_intel/test/valgrind.937189.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.937313.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.937544.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.937897.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.938404.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.939748.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.940131.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.940283.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.940455.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.940710.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.941234.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.941498.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.941987.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.942120.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.942537.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.942764.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.943026.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.943315.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.943723.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.943974.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944152.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944274.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944560.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944742.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944847.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.944953.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945075.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945133.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945195.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945292.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945383.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945442.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945570.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945632.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945774.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945840.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.945903.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946030.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946179.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946241.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946348.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946428.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946572.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.946680.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947005.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947083.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947209.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947302.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947469.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947545.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947651.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947728.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947812.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.947926.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948003.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948086.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948226.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948312.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948412.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948502.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948623.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948774.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948835.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.948923.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.949093.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.949188.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.949385.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.949716.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.949871.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950025.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950163.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950252.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950332.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950423.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950506.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950653.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950730.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.950806.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951220.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951369.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951463.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951552.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951655.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951764.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951859.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.951950.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952060.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952126.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952202.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952373.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952446.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952533.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952687.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952787.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952912.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.952964.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953064.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953272.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953371.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953449.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953535.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953627.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.953702.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.954174.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.954839.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.954955.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955019.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955110.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955187.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955251.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955317.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955413.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955525.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955596.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955704.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955782.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955834.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.955935.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956050.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956292.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956414.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956510.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956618.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956693.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.956814.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957004.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957106.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957315.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957367.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957511.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.957701.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.958283.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.958989.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.959379.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.959519.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.960024.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.960179.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.960305.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.960616.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.960886.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961183.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961312.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961541.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961728.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961816.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.961911.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.962502.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.963779.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.963923.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.964347.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.964571.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.964916.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.965174.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.965372.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.965603.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.965945.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.966119.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.966227.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.966384.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.966808.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.967013.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.967400.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.967577.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.967774.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.968035.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.968504.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.968844.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.969252.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.969609.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.969835.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.970262.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.971188.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.971621.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.971898.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.972070.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.972182.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.972356.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.972482.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.972889.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.973182.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.973864.memcheck.xml
[Valgrind] build/release_intel/test/valgrind.974107.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.937189.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.937189.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.937313.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.937313.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.937544.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.937544.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.937897.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.937897.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.938404.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.938404.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.939748.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.939748.memcheck.xml
make[3]: *** [test/unit/CMakeFiles/memcheck_unit.dir/build.make:70: test/unit/CMakeFiles/memcheck_unit] Terminated
make[2]: *** [CMakeFiles/Makefile2:18979: test/unit/CMakeFiles/memcheck_unit.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:18986: test/unit/CMakeFiles/memcheck_unit.dir/rule] Error 2
make: *** [Makefile:2961: memcheck_unit] Error 2
real 63m39.510s
user 54m18.299s
sys 6m5.097s
+ status=1
++ find /jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/build/release_intel -name Test.xml
[Valgrind] Copying build/release_intel/test/valgrind.940131.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.940131.memcheck.xml
+ mv /jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/build/Test_unit_memcheck.xml
mv: missing destination file operand after '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/build/Test_unit_memcheck.xml'
Try 'mv --help' for more information.
[Valgrind] Copying build/release_intel/test/valgrind.940283.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.940283.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.940455.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.940455.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.940710.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.940710.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.941234.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.941234.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.941498.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.941498.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.941987.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.941987.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.942120.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.942120.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.942537.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.942537.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.942764.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.942764.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.943026.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.943026.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.943315.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.943315.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.943723.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.943723.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.943974.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.943974.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944152.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944152.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944274.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944274.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944560.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944560.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944742.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944742.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944847.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944847.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.944953.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.944953.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945075.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945075.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945133.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945133.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945195.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945195.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945292.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945292.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945383.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945383.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945442.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945442.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945570.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945570.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945632.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945632.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945774.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945774.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945840.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945840.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.945903.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.945903.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946030.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946030.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946179.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946179.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946241.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946241.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946348.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946348.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946428.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946428.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946572.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946572.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.946680.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.946680.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947005.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947005.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947083.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947083.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947209.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947209.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947302.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947302.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947469.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947469.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947545.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947545.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947651.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947651.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947728.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947728.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947812.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947812.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.947926.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.947926.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948003.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948003.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948086.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948086.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948226.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948226.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948312.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948312.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948412.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948412.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948502.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948502.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948623.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948623.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948774.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948774.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948835.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948835.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.948923.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.948923.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.949093.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.949093.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.949188.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.949188.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.949385.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.949385.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.949716.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.949716.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.949871.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.949871.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950025.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950025.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950163.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950163.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950252.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950252.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950332.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950332.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950423.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950423.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950506.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950506.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950653.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950653.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950730.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950730.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.950806.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.950806.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951220.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951220.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951369.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951369.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951463.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951463.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951552.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951552.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951655.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951655.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951764.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951764.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951859.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951859.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.951950.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.951950.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952060.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952060.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952126.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952126.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952202.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952202.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952373.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952373.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952446.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952446.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952533.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952533.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952687.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952687.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952787.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952787.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952912.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952912.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.952964.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.952964.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953064.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953064.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953272.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953272.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953371.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953371.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953449.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953449.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953535.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953535.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953627.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953627.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.953702.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.953702.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.954174.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.954174.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.954839.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.954839.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.954955.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.954955.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955019.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955019.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955110.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955110.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955187.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955187.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955251.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955251.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955317.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955317.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955413.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955413.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955525.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955525.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955596.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955596.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955704.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955704.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955782.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955782.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955834.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955834.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.955935.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.955935.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956050.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956050.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956292.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956292.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956414.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956414.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956510.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956510.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956618.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956618.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956693.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956693.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.956814.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.956814.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957004.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957004.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957106.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957106.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957315.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957315.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957367.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957367.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957511.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957511.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.957701.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.957701.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.958283.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.958283.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.958989.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.958989.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.959379.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.959379.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.959519.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.959519.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.960024.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.960024.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.960179.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.960179.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.960305.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.960305.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.960616.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.960616.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.960886.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.960886.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961183.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961183.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961312.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961312.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961541.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961541.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961728.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961728.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961816.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961816.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.961911.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.961911.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.962502.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.962502.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.963779.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.963779.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.963923.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.963923.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.964347.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.964347.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.964571.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.964571.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.964916.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.964916.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.965174.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.965174.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.965372.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.965372.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.965603.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.965603.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.965945.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.965945.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.966119.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.966119.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.966227.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.966227.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.966384.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.966384.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.966808.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.966808.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.967013.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.967013.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.967400.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.967400.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.967577.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.967577.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.967774.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.967774.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.968035.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.968035.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.968504.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.968504.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.968844.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.968844.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.969252.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.969252.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.969609.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.969609.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.969835.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.969835.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.970262.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.970262.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.971188.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.971188.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.971621.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.971621.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.971898.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.971898.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.972070.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.972070.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.972182.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.972182.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.972356.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.972356.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.972482.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.972482.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.972889.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.972889.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.973182.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.973182.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.973864.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.973864.memcheck.xml
[Valgrind] Copying build/release_intel/test/valgrind.974107.memcheck.xml to /var/lib/jenkins/jobs/SANS_Nightly/configurations/axis-builddir/release_intel/axis-buildnode/reynolds/builds/1617/valgrind-plugin/valgrind-results/build/release_intel/test/valgrind.974107.memcheck.xml
[Valgrind] Analysing valgrind results
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/elf/elf/dl-init.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/string/string/strdup.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/csu/libc-start.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/stdio-common/stdio-common/reg-modifier.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/intl/intl/bindtextdom.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/locale/locale/newlocale.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/stdlib/stdlib/cxa_atexit.c' does not exist, source code won't be available
[Valgrind] copying source file '/usr/include/c++/11/iostream' to 'source_8.tmp'...
[Valgrind] copying source file '/home/jenkins/util/ESP/EngSketchPad/src/EGADS/src/egadsSplineFit.cpp' to 'source_9.tmp'...
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/stdio-common/stdio-common/reg-type.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/stdio-common/stdio-common/reg-printf.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/include/rtld-malloc.h' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/elf/dl-tls.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/nptl/nptl/allocatestack.c' does not exist, source code won't be available
[Valgrind] '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/nptl/nptl/pthread_create.c' does not exist, source code won't be available
[Valgrind] workspacePath: /jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds/
[Valgrind] Ending the valgrind analysis.
INFO: Processing BoostTest-1.x (default)
INFO: [BoostTest-1.x (default)] - No test report file(s) were found with the pattern 'build/boosttest/*.xml' relative to '/jenkins/workspace/SANS_Nightly/builddir/release_intel/buildnode/reynolds' for the testing framework 'BoostTest-1.x (default)'.
Did you enter a pattern relative to (and within) the workspace directory?
Did you generate the result report(s) for 'BoostTest-1.x (default)'?"
WARNING: All test reports are empty.
INFO: Check 'Failed Tests' threshold.
INFO: Check 'Skipped Tests' threshold.
[Checks API] No suitable checks publisher found.
INFO: Setting the build status to SUCCESS
[PostBuildScript] - [INFO] Executing post build scripts.
[PostBuildScript] - [INFO] Node does not have the role MASTER. Did not execute build step #0.
[PostBuildScript] - [INFO] Node does not have the role MASTER. Did not execute build step #1.
[WS-CLEANUP] Deleting project workspace...
[WS-CLEANUP] Deferred wipeout is used...
[WS-CLEANUP] done
Finished: ABORTED
![[Jenkins]](/csi/static/a404d988/images/svgs/logo.svg){kind=logo}
