eglibc has slowly been merged upstream for the last 2 years. The next eglibc release (2.19) not only will be the last, but it's recommended to use glibc instead unless there's specific need:
> I have now set up the EGLIBC 2.19 branch. This is the last EGLIBC release branch; unless you are relying on changes in EGLIBC relative to glibc that have not been merged to glibc, you are advised to use glibc 2.19 branch instead of EGLIBC 2.19 branch. If you are relying
on such changes, listed below, you should plan to contribute such features to glibc so you can cease using EGLIBC
> I have now set up the EGLIBC 2.19 branch. This is the last EGLIBC release branch; unless you are relying on changes in EGLIBC relative to glibc that have not been merged to glibc, you are advised to use glibc 2.19 branch instead of EGLIBC 2.19 branch. If you are relying on such changes, listed below, you should plan to contribute such features to glibc so you can cease using EGLIBC
http://www.eglibc.org/archives/patches/msg01327.html
Although versions are unspecified, for all intents and purposes testing eglibc was either identical to or better than testing glibc.