-
Notifications
You must be signed in to change notification settings - Fork 1
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
Run all regression tests on Jenkins #12
Comments
Mini/maxi-batches have been reduced because on Jenkins machine there is usually only 4GB GPU memory available. |
2 tests seems to be failing
ensemble.return-nematus-alignment
ensemble.return-soft-alignment
Hieu Hoang
http://statmt.org/hieu
…On Mon, 17 Sep 2018 at 22:12, Roman Grundkiewicz ***@***.***> wrote:
Mini/maxi-batches have been reduced because on Jenkins machine there is
usually only 4GB GPU memory available.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#12 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAqOFDN_1U4MzJTIrBwMD7FWM6aNLJqiks5ucBBUgaJpZM4WsuiU>
.
|
these 2 as well |
Probably my fault.haven't checked reg tests in a while. Will take a look |
OK. Jenkins jobs work now properly. @hieuhoang To add more tests to Jenkins (which we should do), just update |
cheers. so only 3 GPU test pass on Jenkins? that's weird. Is the GPU particularly old, with only 4GB? I don't have access/never used Jenkins. Most tests pass on my GTX1080 (apart from 4 mentioned above), I'll make sure all tests pass when I have time. Then we will go from there |
No, I added only 3 tests to be run on Jenkins to check if everything is configured correctly. I wasn't sure which tests are designed for GPU, and which for CPU as only some tests have gpu/cpu in their names. Maybe we should run all tests on both CUDA and CPU-only amun? |
On the Jenkins machine these tests fail:
|
Yep. They fail locally too. Will look at out next week |
I have lightened most tests by decreasing mini/maxi-batch sizes and reducing the length of test inputs wherever appropriate, but at the moment, only a few CPU and GPU tests are run on Jenkins.
However, some tests generate wrong textual output for me. @hieuhoang Does all tests work for you?
The text was updated successfully, but these errors were encountered: