github.com/lulzWill/go-agent@v2.1.2+incompatible/internal/crossagent/cross_agent_tests/proc_cpuinfo/README.md (about)

     1  These tests are for determining the numbers of physical packages, physical cores,
     2  and logical processors from the data returned by /proc/cpuinfo on Linux hosts.
     3  Each text file in this directory is the output of /proc/cpuinfo on various machines.
     4  
     5  The names of all test files should be of the form `Apack_Bcore_Clogical.txt`
     6  where `A`, `B`, and `C` are integers or the character `X`. For example,
     7  a single quad-core processor without hyperthreading would correspond to
     8  `1pack_4core_4logical.txt`, while two 6-core processors with hyperthreading
     9  would correspond to `2pack_12core_24logical.txt`, and would be pretty sweet.
    10  
    11  Using `A`, `B`, and `C` from above, code processing the text in these files
    12  should produce the following expected values:
    13  
    14  | property             | value   |
    15  | -------------------- |---------|
    16  | # physical packages  | `A`     |
    17  | # physical cores     | `B`     |
    18  | # logical processors | `C`     |
    19  
    20  (Obviously, the processing code should do this with no knowledge of the filenames.)
    21  
    22  If any of `A`, `B`, or `C` are the character `X` instead of an integer, then
    23  processing code should not return a value (return `null`, return `nil`,
    24  raise an exception... whatever makes most sense for your agent).
    25  
    26  There is a malformed.txt file which is a random file that does not adhere to
    27  any /proc/cpuinfo format. The expected result is `null` for packages, cores and
    28  processors.