This slave is running wily and has libgcrypt20 installed.

libgcrypt11 is the version running on trusty/precise so I think there is a builder/tester version mis-match here.

Having said that let me see if I can get the libgcrypt11 installed.

Ah, it must be running Wily in order to get the more up to date Intel drivers. There doesn't seem to be libgcrypt11 packages for Wily, however there is libgcrypt20 for Trusty, which the builder is probably using.

I installed the package from trusty: libgcrypt11_1.5.3-2ubuntu4.2_amd64.deb

root@build73-b1:~# ls -al /lib/x86_64-linux-gnu/libgcrypt*
lrwxrwxrwx 1 root root     19 Mar 26  2015 /lib/x86_64-linux-gnu/libgcrypt.so.11 -> libgcrypt.so.11.8.2
-rw-r--r-- 1 root root 524704 Mar 26  2015 /lib/x86_64-linux-gnu/libgcrypt.so.11.8.2
lrwxrwxrwx 1 root root     19 Feb 10 08:41 /lib/x86_64-linux-gnu/libgcrypt.so.20 -> libgcrypt.so.20.0.3
-rw-r--r-- 1 root root 923200 Feb 10 08:41 /lib/x86_64-linux-gnu/libgcrypt.so.20.0.3

And it looks like it will work:

root@build73-b1:~# ldd /lib/x86_64-linux-gnu/libgcrypt.so.11.8.2
	linux-vdso.so.1 =>  (0x00007ffd083d4000)
	libgpg-error.so.0 => /lib/x86_64-linux-gnu/libgpg-error.so.0 (0x00007fd08690f000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fd086545000)
	/lib64/ld-linux-x86-64.so.2 (0x00005605ad056000)

I meant the builder is running Trusty and is not using libgcrypt20 but it could, I'm not sure what changes would be required for that though.

Let's see how the next run goes. Thank you!

context_lost_tests was able to run Chrome in the current run, which it couldn't before. It seems that fixed it!