-
Notifications
You must be signed in to change notification settings - Fork 6.8k
Conversation
updated ! |
|
Let me guess ... its fails because the workspace is different in JenkinsfileForBinaries ? |
@hellonico - I'm still a little bit unsure of how all the CI/ Nightly tests fit together. I started another PR (temporary) to test my theories of how it all works so we can get a better understanding of it. Anything we learn from that, we can apply here. #13642 |
f6e5b4f
to
1446ce5
Compare
1446ce5
to
e3a3978
Compare
WIP apache#13624 clojure nightly tests
@marcoabreu I think we are at a good point where we understand that the integration tests can run on a node in the regular CI. We just need to move that node over to the nightly tests. Do you think that you could make a copy of the job to point to this branch so that we can test that? |
WIP apache#13624 clojure nightly tests
@marcoabreu - can you please help here? Thanks. |
@marcoabreu So I've been thinking about this a bit more and have a couple of questions.
|
@marcoabreu ping again for the update! Thanks |
started a dev discussion about this - https://lists.apache.org/thread.html/a22e40685d543cce4e2f4420046e8142126275888c1c15cb83a7a103@%3Cdev.mxnet.apache.org%3E I think we can move forward on this by just adding it to CI and not nightlies right now until the notifications get implemented. |
@hellonico if you have some bandwidth to move this forward I think we need:
Thanks for your patience in figuring this out :) |
e3a3978
to
1d6910b
Compare
Bonjour ! Working on it ...
|
tests/nightly/JenkinsfileForBinaries
Outdated
node(NODE_LINUX_GPU) { | ||
ws('workspace/clojure') { | ||
utils.unpack_and_init('gpu', mx_lib) | ||
utils.docker_run('ubuntu_nightly_gpu', 'unittest_ubuntu_cpu_clojure_integration', false) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
unittest_ubuntu_cpu_clojure_integration Are these CPU or GPU? maybe rename the function to XPU?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@larroy Merci ! Thanks for the comment ! Right now and as it is, only CPU but it's almost ready to run a few GPU tests
I don't see any reference to XPU in master, is another language already using the notation ?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
In c++ we use the notion for operator definitions that are applicable for CPU as well as GPU, thus called XPU. I can look for a reference if you're interested
8b6f767
to
6507124
Compare
Hmmm ... locally, I get
And CI shows:
Will do some digging later. |
Poor person, getting misclassified as cow 🐄 :( Jokes aside. There's a guide in our confluence wiki under continuous integration named "reproducing test results" that allows you to locally reproduce the results. I'm on mobile right now, but let me know if you can't find it and I'll be happy to provide a link. |
@marcoabreu poor cow as well ;) Thanks, will dig into the wiki ! |
02fff1a
to
e934050
Compare
Update infer test cases to run in the integration phase (simply with lein test).
|
@gigasquid @marcoabreu : Thank you so much for all the help and support. I promise no cows were harmed during the making of this PR. Let's get this in !!!!!!!!!!!!!!!!!!!!!!!!!! |
Thanks @hellonico - We are soo close! |
cd ${test_dir} && lein test | ||
done | ||
# use AWK pattern for blacklisting | ||
TEST_CASES=`find ${EXAMPLES_HOME} -name test | awk '!/dontselect1|dontselect2/'` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Nice thanks :)
1f7c03c
to
2b4d4b1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good 💯
This reverts commit eebdd5f.
Thanks a lot for your great efforts @hellonico and @gigasquid! What do you think about sending an announcement to dev@ that we are now testing Clojure examples? That's a big win! |
unittest_ubuntu_cpu_clojure_integration() { | ||
set -ex | ||
make scalapkg USE_OPENCV=1 USE_BLAS=openblas USE_DIST_KVSTORE=1 ENABLE_TESTCOVERAGE=1 | ||
make scalainstall USE_OPENCV=1 USE_BLAS=openblas USE_DIST_KVSTORE=1 ENABLE_TESTCOVERAGE=1 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Just to inform that we plan to deprecate the make command for Scala package. Please use mvn install
instead to cover the Scala portion
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally I'd like to keep the native build, the scala build and the scala packaging separate. Right now, this job is done on demand and this leads to GPU instances compiling code without caching. So this sounds like a move in the right direction!
Description
This is about running the inrtegration tests during nightly CI.
Checklist
Essentials
Please feel free to remove inapplicable items for your PR.
Changes
Comments