Jump to content

ThomasGutzler

Members
  • Content Count

    20
  • Joined

  • Last visited

  • Days Won

    4

ThomasGutzler last won the day on June 23

ThomasGutzler had the most liked content!

Community Reputation

12 Good

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Our build server fell over last Friday. Nobody noticed, this morning I am greeted with this: This is how it started: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:08 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = User Defined Message Start = VI Package Builder Error = User Defined Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0-> VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58-> VIPB_API.BuildAndPackageLibrary.vi-> 5AB213F9CD1875C24859DBC20A7CDE64-> VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 05:29:10 PM = Automated Message Start = Error 2 occurred at Obtain Queue in JKI_LVConfig__jki_lib_configuration_file.lvlib:1188A4A91C005F423D89358A8C95F362->4F9D0428213F8F95FE3 A745133E46203->FF473C6B63ADACAEF90D52E8AFBDC45F->246E5055266A40F567071DB843B25FE8->1C008B1C8A190D0D7 176E93799F7534B->VIPB_API.BuildAndPackageLibraryFromSpec[Private].vi:6610001->5AB213F9CD1875C24859DB C20A7CDE64->VIPB_API.BuildAndPackageLibrary.vi->VIPM API.lvlib:31462C1008B1B48A698808B4D0EE6D58->41AC743D0ED402FF42A432FD77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Friday July 31, 2020 at 08:57:05 PM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== And after that it's just this: =========== START of VIPM 2018.0.0 (build 2027) Error Message =========== An internal VIPM 2018.0.0 (build 2027) Error has occured on: Monday August 03, 2020 at 09:13:31 AM = Automated Message Start = Error 2 occurred at Obtain Queue in NI_LVConfig.lvlib:Open Config Data.vi->343FBFE9D2AE778BDCE948E13EDD148A->A37D44BD2FCED7810A2AC814B145247C->41AC743D0ED402FF42A432F D77E580E0->VIPM Main Window.vi Possible reason(s): LabVIEW: Memory is full. = Automated Message End = = Error Handler Call Chain Start = VIPM Main Window.vi-> 41AC743D0ED402FF42A432FD77E580E0 = Error Handler Call Chain End = =========== END of VIPM 2018.0.0 (build 2027) Error Message =========== and continuing to fill. Task Manager tells me there are still 2GB of memory available
  2. Always forward, Jim I don't want to bring up the "increased performance" argument. I mean, we're using LabVIEW after all. Nobody who's using LabVIEW can seriously play the performance card. I regularly see VIPM using over 1GB of memory and sometimes crashing with an "out of memory" error - although that might be due to the ridiculous 4GB of total memory available on that machine. How long before that goes to 2GB, 3GB? We've had 64bit on windows for 15 years now. I think it's time to move on. At least give us the option. Surely VIPM isn't depending on modules that don't exist in 64bit land
  3. Please make a 64bit release of VIPM
  4. Hi, This is not a problem report but more a success story. Well done crew! I heard about caraya when I looked through the talks of VI Week (and I'm still watching videos) and I wanted to give it a go. I've been wanting to try unit testing for a while but the built-in stuff just wasn't doing it for me. We (work) do all our building, releasing and deployment via Azure pipelines so when I heard that caraya can generate JUnit format test results, I jumped straight in and made myself a test pipeline for a new feature we just added to one of our libraries. I downloaded the TDD template, copied the Pre-Build-Action.vi into my project (it needed a bit of fixing) and defined some tests. Once I had the pre-build vi working I looked at the Azure part. I wanted the pipeline to be aware of the test results. All I had to do is to call the Publish Test Results task which takes the results and publishes them to the Azure test repository and bang! Unit testing done. Here are some screenshots And then I added a broken test
  5. Excellent, Thanks @Jim Kring. Is there a planned release date for VIPM 2020?
  6. Has anyone from JKI seen this? @Ashish @Jim Kring I thought there might be some interest in fixing this bug
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.