iMSTK issueshttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues2022-07-01T13:39:36-04:00https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/447CI Tasks2022-07-01T13:39:36-04:00Harald ScheirichCI TasksIn Order of importance
- [ ] Enable `IMSTK_WRAP_CSHARP` Windows (Linux optional)
- [ ] Enable Coverage Calc and Posting Linux Only
- [ ] Enable `IMSTK_USE_OpenHaptics` Windows Only
- [ ] Enable `IMSTK_USE_VRPN`In Order of importance
- [ ] Enable `IMSTK_WRAP_CSHARP` Windows (Linux optional)
- [ ] Enable Coverage Calc and Posting Linux Only
- [ ] Enable `IMSTK_USE_OpenHaptics` Windows Only
- [ ] Enable `IMSTK_USE_VRPN`https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/403Case sensitivity not handled in WSL build environment2022-06-29T09:39:38-04:00Harald ScheirichCase sensitivity not handled in WSL build environmentOur CI server is currently configured to be case-insensitive
https://docs.microsoft.com/en-us/windows/wsl/case-sensitivity
documents how to change thisOur CI server is currently configured to be case-insensitive
https://docs.microsoft.com/en-us/windows/wsl/case-sensitivity
documents how to change thisAndrew WilsonAndrew Wilsonhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/332Linux Build Issues2021-07-06T09:10:10-04:00Harald ScheirichLinux Build IssuesStill working on improving the linux dashboard builds
- [x] Debug build compile error
- [x] Debug build link error (!612)
- [x] Dashboard test issuesStill working on improving the linux dashboard builds
- [x] Debug build compile error
- [x] Debug build link error (!612)
- [x] Dashboard test issuesHarald ScheirichHarald Scheirichhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/321msvc2017 Continuous Integration Failure2022-01-07T01:12:21-05:00Andrew Wilsonmsvc2017 Continuous Integration FailureWhen doing an MR and testing, msvc2017 will often fail despite it actually working.
This is known because I've gone in and built it myself manually, and it worked.
I've also merged code that passed 2019 but not 2017, it then tested mas...When doing an MR and testing, msvc2017 will often fail despite it actually working.
This is known because I've gone in and built it myself manually, and it worked.
I've also merged code that passed 2019 but not 2017, it then tested master and passed. Also passed on nightly. So it's clear there wasn't actually an error with the msvc2017.
I believe it to be building out of date code, or reporting out of date (previous) results.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/316Add merge request template to gitlab2021-05-26T16:15:49-04:00Harald ScheirichAdd merge request template to gitlabCreate a template to be filled in during merge requestsCreate a template to be filled in during merge requestsHarald ScheirichHarald Scheirichhttps://gitlab.kitware.com/iMSTK/iMSTK/-/issues/189Add more nightly build configurations2019-07-28T16:23:55-04:00Sreekanth ArikatlaAdd more nightly build configurationsCurrent builds:
* Windows 10; VS2013; VTK backend; Omni device ON; debug
* Windows 10; VS2013; VTK backend; Omni device ON; release
* Windows 10; VS2017; VTK backend; Omni device ON; debug
* Windows 10; VS2017; VTK backend; Omni device O...Current builds:
* Windows 10; VS2013; VTK backend; Omni device ON; debug
* Windows 10; VS2013; VTK backend; Omni device ON; release
* Windows 10; VS2017; VTK backend; Omni device ON; debug
* Windows 10; VS2017; VTK backend; Omni device ON; release
* Ubuntu 16.04; GCC; VTK backend; Omni OFF; debug
* Ubuntu 16.04; GCC; VTK backend; Omni OFF; release
* Mac OS (latest); ninja; VTK backend; Omni OFF; release
* Mac OS (latest); ninja; VTK backend; Omni OFF; debug
Add more builds esp. for vulkan backend.https://gitlab.kitware.com/iMSTK/iMSTK/-/issues/185Create more build bots for CI2018-12-04T11:26:20-05:00Sreekanth ArikatlaCreate more build bots for CICreate more build bots for testing additional optionsCreate more build bots for testing additional options