update default SlapOS gcc version to 10.5
- OwnerResolved by Jérome Perrin
let's run tests and see what happens :) there might be something with kumofs component that needs an old gcc. I don't know, I wanted to try this as well.
Edited by Jérome Perrin - Last reply by Jérome Perrin
marked as a Work In Progress
changed title from update default SlapOS gcc version to 10.2 to WIP: update default SlapOS gcc version to 10.5
mentioned in merge request !1556 (closed)
resolved all threads
- OwnerResolved by Thomas Gambier
BTW, I noticed you included a commit to add pytest for manual testing, if I remember correctly, some tests are not run when using pytest. I just wanted to say that we need to be careful that the number of running tests remain the same if we ever want to switch to pytest.
And also that zope-testrunner is not bad either as a test runner.
I'm not talking about the features they both have to write tests, basically the two features I like are to have a way to run only selected tests and also to automatically enter a debugger on error, zope-testrunner also does all this. pytest sometimes enters pdb after the test tear down and sometimes after clean up it's too late to investigate.
- Last reply by Thomas Gambier
- OwnerResolved by Thomas Gambier
Isn't it better to omit the minor number string from buildout part name, i.e. gcc-10 instead of gcc-10.5, gcc-5 instead of gcc-5.5 etc. ?
Edited by Kazuhiko Shiozaki - Last reply by Thomas Gambier
resolved all threads
unmarked as a Work In Progress
merged
mentioned in merge request !1551 (merged)
