{"id":2334,"date":"2010-03-26T19:54:25","date_gmt":"2010-03-27T03:54:25","guid":{"rendered":"http:\/\/multimedia.cx\/eggs\/?p=2334"},"modified":"2010-03-26T19:54:25","modified_gmt":"2010-03-27T03:54:25","slug":"testing-older-snapshots-with-fate","status":"publish","type":"post","link":"https:\/\/multimedia.cx\/eggs\/testing-older-snapshots-with-fate\/","title":{"rendered":"Testing Older Snapshots With FATE"},"content":{"rendered":"

Suppose FATE<\/a> had the infrastructure to test arbitrary branches of FFmpeg<\/a>. I just realized that it wouldn’t necessarily help because the FATE test specs keep changing as the code is adjusted. This implies that there needs to be more sophisticated test management.<\/p>\n

This occurred to me due to the chatter surrounding the recent FFmpeg 0.51 security release. Running the FATE suite against 0.51 doesn’t work since the current state of the various FATE tests are contingent upon the current mainline FFmpeg source. Possible solutions going forward? Perhaps upgrade the FATE database to support some kind of versioning? However, this would also limit my ability to monkey with the existing FATE suite of samples.<\/p>\n","protected":false},"excerpt":{"rendered":"

Just one of many ways in which FATE falls over<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[101],"tags":[],"class_list":["post-2334","post","type-post","status-publish","format-standard","hentry","category-fate-server"],"aioseo_notices":[],"aioseo_head":"\n\t\t\n\t\n\t\n\t\n\t\n\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t\n\t\t