-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
misc CI (excluding flaky tests) #98
Comments
|
=> see nim-lang#13954 (comment) |
=> moved to #167 |
bisect bot triggered on github issues that contains a keyword + runnable codelinks
links |
avoid rebuilding csources => use choosenim or docker image or some fixed release tarball instead? |
32bit linux VM: can't we use docker for that? |
docker based nim CI's eg https://github.com/nitely/nim-regex/blob/e6efb506662721656567f0dab236b1ea052d518f/.travis.yml#L2
|
important_pacakges: |
does this run with cpp only in NIM_COMPILE_TO_CPP? etc
|
implement proc coverage, simpler than line or branch coverage; useful to see what's missing (or accidentally missing) in tests |
skip parts of CI based on commit msg
|
links:glob approach, similar to what I did in nim-lang#13221 ; this could work by adding a test inside The point of a blacklist (instead of whitelist) is to keep working even if modules are added, removed, or moved. Note that the same code could be reused (with a different blacklist exclusion) for other targets and/or compiler options, eg |
IIRC, ABI checks failed for VCC! links |
refs: fix #13902 distinct uint64 type corruption on 32-bit with borrow nim-lang/Nim#13907 (comment)
The text was updated successfully, but these errors were encountered: