Some tests fail under Travis-CI / Ubuntu 12.04

[lunixbochs]

I'm trying to add Travis support, but some of the tests fail:

=== RUN TestGCM
--- FAIL: TestGCM (0.00 seconds)
    ciphers_test.go:154: Decryption with b=256: Failed to add authenticated data: failed to add additional authenticated data
=== RUN TestGCMWithNoAAD
--- FAIL: TestGCMWithNoAAD (0.00 seconds)
    ciphers_test.go:172: Decryption failure: Failed to perform a decryption: failed to decrypt
=== RUN TestBadTag
--- FAIL: TestBadTag (0.00 seconds)
    ciphers_test.go:198: Decryption failure: Failed to perform a decryption: failed to decrypt
=== RUN TestBadCiphertext
--- FAIL: TestBadCiphertext (0.00 seconds)
    ciphers_test.go:224: Decryption failure: Failed to add authenticated data: failed to add additional authenticated data
=== RUN TestBadAAD
--- FAIL: TestBadAAD (0.00 seconds)
    ciphers_test.go:250: Decryption failure: Failed to add authenticated data: failed to add additional authenticated data

The travis-ci.org boxes are running Ubuntu 12.04. I installed libssl-dev as a dependency.

Tests do not fail on my own Ubuntu 14.04 VM. I'm setting up a 12.04 VM to debug.

[thepaul]

The authenticated encryption functions were added in OpenSSL 1.1.0 and backported to OpenSSL 1.0.1. Ubuntu decided not to add support for them in 12.04, for (probably) reasons (but I don't know them).

We should probably have the tests somehow detect the situation where the functions are not available and do a t.Skip() or something, since testing them in places that don't have the underlying functionality doesn't make sense.

[lunixbochs]

I kinda disagree with that solution, because then you have active code not covered by tests. I think a better solution (until travis-ci.org gets Ubuntu 14.04 support) would be to come up with a travis build that installs a newer version of OpenSSL to test against.

[thepaul]

That sounds fine to me. Here we just run the tests on Debian Wheezy, which does have the GCM functions.

[zeebo]

Closing due to inactivity.