Hi,
I was looking at exploding the Racket CI configurations to make them
more fine-grained.
For non x86_64 architectures with default flags / racketcs etc, there
are many failures and I would like to make the testing more fine-grained
so that I can lock a configuration /to success/ as soon as possible.
What I mean by this is... most our jobs at the moment have:
'allow_failure: true'. I want to reduce these.
Instead of having a testing job that does:
- raco test -l tests/racket/test 2>&1 | tee logs/test.log
- racket -l tests/racket/contract/all 2>&1 | tee logs/contract-test.log
- raco test -l tests/json/json 2>&1 | tee logs/json-test.log
- raco test -l tests/file/main 2>&1 | tee logs/file-test.log
- raco test -l tests/net/head 2>&1 | tee logs/net-head-test.log
- raco test -l tests/net/uri-codec 2>&1 | tee
logs/net-uri-codec-test.log
- raco test -l tests/net/url 2>&1 | tee logs/net-url-test.log
- raco test -l tests/net/url-port 2>&1 | tee logs/net-url-port-test.log
- raco test -l tests/net/encoders 2>&1 | tee logs/net-encoders-test.log
- raco test -l tests/openssl/basic 2>&1 | tee
logs/openssl-basic-test.log
- raco test -l tests/openssl/https 2>&1 | tee
logs/openssl-https-test.log
- raco test -l tests/match/main 2>&1 | tee logs/match-main-test.log
- raco test -l tests/zo-path 2>&1 | tee logs/zo-path-test.log
- raco test -l tests/xml/test 2>&1 | tee logs/xml-test.log
- raco test -l tests/db/all-tests 2>&1 | tee logs/db-test.log
- raco test -c tests/stxparse 2>&1 | tee logs/stxparse-test.log
When one of them fails, we silence the failure with 'allow_failure:
true'. The problem with this is that if a problem shows up somewhere
else, it will go unnoticed because we allow failure by default. I want
to make each of these a single job and allow failure only on those which
really fail and once they pass, lock them onto success by not allowing
failure anymore.
I initially copied the above lines without the redirections from travis
yml. Is this list of tests up-to-date? Is this all we have and are they
being run correctly?
I should point out I find it slightly strange that the tests seem to be
implemented in different ways since the contract tests are ran with
`racket -l`, and stxparse are ran with `raco test -c`. What's the reason
for this difference?
Kind regards,
--
Paulo Matos
--
You received this message because you are subscribed to the Google Groups
"Racket Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to racket-dev+unsubscr...@googlegroups.com.
To post to this group, send email to racket-dev@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/racket-dev/a010e885-4f63-44d4-e73e-5457a0159fdc%40linki.tools.
For more options, visit https://groups.google.com/d/optout.
