4.2.1.16 The go-revision test

  Problem:  Using old versions of the GO compiler looses out on security enhacements
  Fix By:   Using a newer GO compiler
  Waive If: No new GO compiler is available

  Example:  FAIL: go-revision test because GO revision must be >= 14
  Example:  FAIL: go-revision test because multiple, different GO version strings found
  Example:  FAIL: go-revision test because no Go compiler revision information found

This test checks to see that GO code has been compiled by at least a revision 14 compiler. Earlier versions of the compiler do not have all the bug fixes and security enhancements of later versions.

Note - it is likely that the minimum revision of the GO compiler will be increased in the future.

If necessary the test can be disabled via the --skip-go-revision option and re-enabled via the --test-go-revision option.