{"push_id":1137633610,"size":8,"distinct_size":8,"ref":"refs/heads/master","head":"a082bea5624b60a8d10d9d564c88f5bac82a3697","before":"203b13c5f97b1d9bd20c29ab9165663b09a704b6","commits":[{"sha":"21031482e7a9fc828622ea2015d87432704b1c7f","author":{"name":"Olivier Berthier","email":"3fef44842777675c0651acdc295b796744cb3e84@linux.intel.com"},"message":"framework: Add aborting option when a monitored error is detected\n\nThis adds a policy which advises when the user should reboot the system\nto avoid noisy test results due to system becoming unstable, for\ninstance, and therefore continues testing successfully.\n\nTo do this, a new module is proposed. A class Monitoring is used for\nmanaging the monitoring rules. Two types of rules, MonitoringFile and\nMonitoringLinuxDmesg, derived from the abstract class MonitoringBase,\nhave been implemented. The first allow to track a pattern on standard\nfiles or locked files. The second, derived from dmesg.LinuxDmesg, will\ntrack a pattern on the dmesg.\n\nThe monitoring rules must be defined in piglit.conf at the section\nmonitored-errors. If one of the regex is found, Piglit will raise a\nPiglitAbort exception, stop the test execution -terminating test thread\npool- and exit with code 3.\n\nThen test execution resume, after rebooting the system or not, is done\nlike usually with command line parameter \"resume\".\n\nTo call it, use command line parameter: --abort-on-monitored-error\n\nThis option implies --no-concurrent\n\nThis include also a set of unit tests for this module.\n\nReviewed-by: Dylan Baker <dylanx.c.baker@intel.com>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/21031482e7a9fc828622ea2015d87432704b1c7f"},{"sha":"b402f8b311cd45c8a6fbb23e7d728eb047173d03","author":{"name":"Jan Vesely","email":"d1857f189d27309d4ee686c3c524179c94b3bd87@rutgers.edu"},"message":"cl: declare enum counts as extern\n\nThe correct symbols are in libpiglitutil_cl.so\n\nReported-by: Jose Luis Cercós <jlcercos@gmail.com>\nSigned-off-by: Jan Vesely <jan.vesely@rutgers.edu>\nReviewed-by: Serge Martin <edb+mesa@sigluy.net>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/b402f8b311cd45c8a6fbb23e7d728eb047173d03"},{"sha":"fb381fdbe1447c22cba0573a495b49f88cf768e0","author":{"name":"Samuel Iglesias Gonsálvez","email":"696499febbb821894b47a781ec89e21f5b31e804@igalia.com"},"message":"arb_gpu_shader_fp64: add simple explicit location execution test\n\nIt is failing in current i965 Mesa driver. This tests checks\nVS, GS and FS stages.\n\nv2:\n- Rename the test (Timothy)\n- Don't require GLSL 4.20 (Timothy)\n\nSigned-off-by: Samuel Iglesias Gonsálvez <siglesias@igalia.com>\nReviewed-by: Timothy Arceri <timothy.arceri@collabora.com>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/fb381fdbe1447c22cba0573a495b49f88cf768e0"},{"sha":"1ea15c92fa41cbe62bd32e77b616e2560107a34f","author":{"name":"Ian Romanick","email":"5d0faf76d4a631a1258a1364a2f3c90ffb34764c@intel.com"},"message":"arb_program_interface_query: Expect certain built-ins be prefixed with gl_PerVertex\n\nThe ARB_program_interface_query spec says:\n\n   Issues:\n\n   (16) How are inputs and outputs in the built-in interface block\n        \"gl_PerVertex\" enumerated?\n\n\t...\n\n     For tessellation control, tessellation evaluation, and geometry shaders,\n     per-vertex built-in inputs like gl_Position are in a block with an\n     instance name of \"gl_in[]\".  Additionally, for tessellation control\n     shaders, per-vertex built-in outputs like gl_Position are in a block\n     with an instance name of \"gl_out[]\".  In these cases, applying the\n     standard rules would result in an enumerated name of\n     \"gl_PerVertex.gl_Position\".\n\nThis causes a number of failures on GeForce GT 430/PCIe/SSE2 using\nNVIDIA 355.11 drivers.  All of the failures are because the names don't\nhave gL_PerVertex, so they are 13 characters shorter than the test (now)\nexpects.\n\n'GL_PROGRAM_INPUT(gs) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_INPUT(gs)\" : \"fail\"}}\n'GL_PROGRAM_INPUT(gs,fs) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_INPUT(gs,fs)\" : \"fail\"}}\n'GL_PROGRAM_INPUT(tes) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_INPUT(tes)\" : \"fail\"}}\n'GL_PROGRAM_INPUT(tcs) active resources' expected 3 but got 2\n'GL_PROGRAM_INPUT(tcs) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_INPUT(tcs)\" : \"fail\"}}\n'GL_PROGRAM_INPUT(tcs,tes) active resources' expected 3 but got 2\n'GL_PROGRAM_INPUT(tcs,tes) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_INPUT(tcs,tes)\" : \"fail\"}}\n'GL_PROGRAM_OUTPUT(tcs) active resources' expected 3 but got 2\n'GL_PROGRAM_OUTPUT(tcs) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_OUTPUT(tcs)\" : \"fail\"}}\n\nSigned-off-by: Ian Romanick <ian.d.romanick@intel.com>\nReviewed-by: Martin Peres <martin.peres@linux.intel.com>\nCc: Dave Airlie <airlied@redhat.com>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/1ea15c92fa41cbe62bd32e77b616e2560107a34f"},{"sha":"7e67bbac72f85db494103fffe38e979d1fddcdc5","author":{"name":"Ian Romanick","email":"5d0faf76d4a631a1258a1364a2f3c90ffb34764c@intel.com"},"message":"arb_program_interface_query: Expect array suffixes on array inputs / outputs\n\nThe ARB_program_interface_query spec says:\n\n   * For an active variable declared as an array of basic types, a single\n     entry will be generated, with its name string formed by concatenating\n     the name of the array and the string \"[0]\".\n\nI can find no language that implies that geometry or tessellation inputs\nor tessellation control outputs should be excluded from this rule.\nVarious dEQP tests also expect [0] be added to geometry shader inputs.\n\nThis appears to match the behavior expected by a GeForce GT\n430/PCIe/SSE2 using NVIDIA 355.11 drivers.\n\nSigned-off-by: Ian Romanick <ian.d.romanick@intel.com>\nReviewed-by: Martin Peres <martin.peres@linux.intel.com>\nCc: Dave Airlie <airlied@redhat.com>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/7e67bbac72f85db494103fffe38e979d1fddcdc5"},{"sha":"e428ddff67340156bcbe4a748395234ceedbbd07","author":{"name":"Ian Romanick","email":"5d0faf76d4a631a1258a1364a2f3c90ffb34764c@intel.com"},"message":"arb_program_interface_query: Fix TCS input expectations\n\nSection 7.1 (Built-In Language Variables) of the GLSL 4.00 spec says:\n\n   In the tessellation control language, built-in variables are\n   intrinsically declared as:\n\n   in gl_PerVertex {\n      vec4 gl_Position;\n      float gl_PointSize;\n      float gl_ClipDistance[];\n   } gl_in[gl_MaxPatchVertices];\n\n   in int gl_PatchVerticesIn;\n   in int gl_PrimitiveID;\n   in int gl_InvocationID;\n\nSince gl_PointSize, gl_ClipDistance[], gl_PatchVerticesIn, and\ngl_PrimitiveID are not used, they are eliminated.\n\nThis still differs from the behavior of a GeForce GT 430/PCIe/SSE2\nusing NVIDIA 355.11 drivers.  I'm not sure which expected name isn't\nbeing reported.\n\n'GL_PROGRAM_OUTPUT(tcs) active resources' expected 3 but got 2\n'GL_PROGRAM_OUTPUT(tcs) max length name' expected 25 but got 12\nPIGLIT: {\"subtest\": {\"GL_PROGRAM_OUTPUT(tcs)\" : \"fail\"}}\n\nSigned-off-by: Ian Romanick <ian.d.romanick@intel.com>\nReviewed-by: Martin Peres <martin.peres@linux.intel.com>\nCc: Dave Airlie <airlied@redhat.com>","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/e428ddff67340156bcbe4a748395234ceedbbd07"},{"sha":"077b7c7b07bd07c2ced7ae6b0c50ed0a3de0b6c5","author":{"name":"Matt Arsenault","email":"0276f30a2f0578e398f46784516b4e125e2c2f76@amd.com"},"message":"cl: Add more arithmetic tests to exercise 24bit div/mod routines\n\nv2 (jan): extend to unsigned variants","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/077b7c7b07bd07c2ced7ae6b0c50ed0a3de0b6c5"},{"sha":"a082bea5624b60a8d10d9d564c88f5bac82a3697","author":{"name":"Tom Stellard","email":"1ab8e172806ba53318a3e2dcaf9ac0215f1df251@amd.com"},"message":"cl: Add failing case to exp test","distinct":true,"url":"https://api.github.com/repos/jvesely/piglit/commits/a082bea5624b60a8d10d9d564c88f5bac82a3697"}]}
{"actor":{"display_login":"jvesely"}}