You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@eugenwintersberger@jkotan, as Windows builds are being added in GitHub CI as part of #501, we are evaluating the possibility dropping the Windows builds from the ESS Jenkins builds.
We don't use Windows internally, so we don't consider the effort it takes to maintain the Windows 10 build node is worth it, as that is the only Windows server we run in our CI infrastructure.
Do the new GitHub CI Windows builds cover the project's needs? What is your opinion on dropping the ESS Windows build?
The text was updated successfully, but these errors were encountered:
Hello @amues,
at DESY/PETRAIII we try to avoid Windows but it is not always possible (because of vendor drivers). I think for us it is enough to it is enough to run Windows tests on github nodes and skip ESS Windows tests runs.
Then it would be good
to extend github tests to all branches (currently they are run only on master branches)
to fix the issue in Cmake improvements #501 PR. Currently some windows tests are not launched
Run cd build
UpdateCTestConfiguration from :D:/a/h5cpp/h5cpp/build/DartConfiguration.tcl
UpdateCTestConfiguration from :D:/a/h5cpp/h5cpp/build/DartConfiguration.tcl
Test project D:/a/h5cpp/h5cpp/build
Constructing a list of tests
Done constructing a list of tests
Updating test list for fixtures
Added 0 tests to meet fixture requirements
Checking test dependency graph...
Checking test dependency graph end
No tests were found!!!
@eugenwintersberger @jkotan, as Windows builds are being added in GitHub CI as part of #501, we are evaluating the possibility dropping the Windows builds from the ESS Jenkins builds.
We don't use Windows internally, so we don't consider the effort it takes to maintain the Windows 10 build node is worth it, as that is the only Windows server we run in our CI infrastructure.
Do the new GitHub CI Windows builds cover the project's needs? What is your opinion on dropping the ESS Windows build?
The text was updated successfully, but these errors were encountered: