{"harness_only":"0","test_jobs":null,"smoke_version":"1.80","out_file":"Started smoke at 1701805630\nSmoking patch 79950615ae6d4a4ca72bf1b913b8e2842bd927e4 v5.39.5-79-g79950615ae\nSmoking branch blead\nStopped smoke at 1701805632\nStarted smoke at 1701805632\n\nConfiguration: -Dusedevel\n------------------------------------------------------------------------------\n\nCompiler info: cc version 10.2.1 20210110\nIn file included from perl.h:3308,\n                 from scope.c:27:\nscope.c: In function ‘Perl_leave_scope’:\nhandy.h:99:35: warning: ‘a2.any_uv’ may be used uninitialized in this function [-Wmaybe-uninitialized]\n   99 | #  define MUTABLE_PTR(p) ({ void *p_ = (p); p_; })\n      |                                   ^~\nscope.c:1117:21: note: ‘a2.any_uv’ was declared here\n 1117 |         ANY a0, a1, a2; /* up to 3 args */\n      |                     ^~\nWarning (mostly harmless): No library found for -lposix\nWarning (mostly harmless): No library found for -lcposix\nTSTENV = stdio\tu=32.70  s=16.76  cu=1970.10  cs=214.44  scripts=2631  tests=1179240\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nTSTENV = perlio\tu=31.02  s=16.70  cu=1853.18  cs=197.12  scripts=2633  tests=1179356\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nTSTENV = locale:en_US.utf8\tu=30.86  s=17.04  cu=1852.86  cs=198.32  scripts=2633  tests=1179544\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nStopped smoke at 1701814271\nStarted smoke at 1701814271\n\nConfiguration: -Dusedevel -DDEBUGGING\n------------------------------------------------------------------------------\n\nCompiler info: cc version 10.2.1 20210110\nIn file included from perl.h:3308,\n                 from scope.c:27:\nscope.c: In function ‘Perl_leave_scope’:\nhandy.h:99:35: warning: ‘a2.any_uv’ may be used uninitialized in this function [-Wmaybe-uninitialized]\n   99 | #  define MUTABLE_PTR(p) ({ void *p_ = (p); p_; })\n      |                                   ^~\nscope.c:1117:21: note: ‘a2.any_uv’ was declared here\n 1117 |         ANY a0, a1, a2; /* up to 3 args */\n      |                     ^~\nWarning (mostly harmless): No library found for -lposix\nWarning (mostly harmless): No library found for -lcposix\nTSTENV = stdio\tu=43.74  s=17.48  cu=2385.26  cs=227.80  scripts=2632  tests=1179443\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nTSTENV = perlio\tu=41.74  s=17.78  cu=2261.56  cs=210.62  scripts=2634  tests=1179374\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nTSTENV = locale:en_US.utf8\tu=42.32  s=17.74  cu=2267.90  cs=211.54  scripts=2634  tests=1179336\n\n#   Failed test 'Is authors_file 'AUTHORS' up to date?'\n#   at Porting/updateAUTHORS.pl line 127.\n#   File 'AUTHORS' changes:\n#     would add: x-yuri                         <x.yuri.83@gmail.com>\n# \n# Files need updating! You probably just need to run\n# \n#    Porting/updateAUTHORS.pl\n# \n# and commit the results.\n# Looks like you failed 1 test of 5.\n#   \"Apparent broken link\" \n#     to \"Term::ReadLine::*\" near line 1146 of pod/perldebug.pod\n# See end of this test output for your options on silencing this\n# \n# HOW TO GET ../t/porting/podcheck.t TO PASS\n# \n# There was 1 file that had new potential problems identified.\n# Some of them may be real, and some of them may be false positives because\n# this program isn't as smart as it likes to think it is.  You can teach this\n# program to ignore the issues it has identified, and hence pass, by doing the\n# following:\n# \n# 1) If a problem is about a link to an unknown module or man page that\n#    you know exists, re-run the command something like:\n#       ./perl -I../lib porting/podcheck.t --add-link { MODULE | man_page ... }\n#    (MODULEs should look like Foo::Bar, and man_pages should look like\n#    bar(3c); don't do this for a module or man page that you aren't sure\n#    about; instead treat as another type of issue and follow the\n#    instructions below.)\n# \n# 2) For other issues, decide if each should be fixed now or not.  Fix the\n#    ones you decided to, and rerun this test to verify that the fixes\n#    worked.\n# \n# 3) If there remain false positive or problems that you don't plan to fix right\n#    now,\n#    run this test script by hand, using the following formula (on\n#    Un*x-like machines):\n#         cd t\n#         ./perl -I../lib porting/podcheck.t --regen\n# \n#    That should cause all current potential problems to be accepted by\n#    the program, so that the next time it runs, they won't be flagged.\n#    For a few files, such as perltoc, certain issues will always be\n#    expected, and more of the same will be added over time.  For those,\n#    before you do the regen, you can edit\n#    /home/pi/perl5smoke/perl-current/t/porting/known_pod_issues.dat\n#    and find the entry for the module's file and specific error message,\n#    and change the count of known potential problems to -1.\n\n    ../t/porting/authors.t......................................FAILED\n        1\n    ../t/porting/authors.t......................................FAILED\n        Non-zero exit status: 1\n    ../t/porting/podcheck.t.....................................FAILED\n        179\n\nStopped smoke at 1701824631\nFinished smoking 79950615ae6d4a4ca72bf1b913b8e2842bd927e4 v5.39.5-79-g79950615ae blead\n","smoke_revision":"1.80","reporter_version":"0.054","git_id":"79950615ae6d4a4ca72bf1b913b8e2842bd927e4","osname":"linux","nonfatal_msgs":"","plevel":"5.039005zzz079","id":5045074,"smoker_version":"0.046","user_note":"Check: https://perl5.test-smoke.org\n","configs":[{"duration":8639,"id":395525,"cc":"cc","started":"2023-12-05T19:47:12Z","arguments":"","debugging":"N","ccversion":"10.2.1 20210110","results":[{"stat_tests":1179240,"statistics":"u=32.70  s=16.76  cu=1970.10  cs=214.44  scripts=2631  tests=1179240","failures":[{"failure_id":3850,"failure":{"status":"FAILED","test":"../t/porting/authors.t","id":3850,"extra":"1\nNon-zero exit status: 1"},"result_id":637668},{"failure_id":3955,"result_id":637668,"failure":{"extra":"179","status":"FAILED","test":"../t/porting/podcheck.t","id":3955}}],"locale":null,"id":637668,"config_id":395525,"io_env":"stdio","stat_cpu_time":2234,"summary":"F"},{"summary":"F","config_id":395525,"id":637669,"stat_cpu_time":2098.02,"io_env":"perlio","statistics":"u=31.02  s=16.70  cu=1853.18  cs=197.12  scripts=2633  tests=1179356","stat_tests":1179356,"failures":[{"result_id":637669,"failure":{"extra":"1\nNon-zero exit status: 1","id":3850,"test":"../t/porting/authors.t","status":"FAILED"},"failure_id":3850},{"failure":{"extra":"179","id":3955,"status":"FAILED","test":"../t/porting/podcheck.t"},"result_id":637669,"failure_id":3955}],"locale":null},{"id":637670,"config_id":395525,"stat_cpu_time":2099.08,"io_env":"locale","stat_tests":1179544,"statistics":"u=30.86  s=17.04  cu=1852.86  cs=198.32  scripts=2633  tests=1179544","failures":[{"result_id":637670,"failure":{"extra":"1\nNon-zero exit status: 1","id":3850,"test":"../t/porting/authors.t","status":"FAILED"},"failure_id":3850},{"failure_id":3955,"failure":{"extra":"179","id":3955,"status":"FAILED","test":"../t/porting/podcheck.t"},"result_id":637670}],"locale":"en_US.utf8","summary":"F"}],"report_id":5045074},{"arguments":"","started":"2023-12-05T22:11:11Z","debugging":"D","report_id":5045074,"ccversion":"10.2.1 20210110","results":[{"summary":"F","id":637671,"config_id":395526,"stat_cpu_time":2674.28,"io_env":"stdio","failures":[{"failure_id":3850,"result_id":637671,"failure":{"test":"../t/porting/authors.t","status":"FAILED","id":3850,"extra":"1\nNon-zero exit status: 1"}},{"failure_id":3955,"result_id":637671,"failure":{"extra":"179","id":3955,"test":"../t/porting/podcheck.t","status":"FAILED"}}],"statistics":"u=43.74  s=17.48  cu=2385.26  cs=227.80  scripts=2632  tests=1179443","stat_tests":1179443,"locale":null},{"summary":"F","locale":null,"statistics":"u=41.74  s=17.78  cu=2261.56  cs=210.62  scripts=2634  tests=1179374","failures":[{"failure_id":3850,"result_id":637672,"failure":{"id":3850,"test":"../t/porting/authors.t","status":"FAILED","extra":"1\nNon-zero exit status: 1"}},{"failure":{"status":"FAILED","test":"../t/porting/podcheck.t","id":3955,"extra":"179"},"result_id":637672,"failure_id":3955}],"stat_tests":1179374,"io_env":"perlio","stat_cpu_time":2531.7,"id":637672,"config_id":395526},{"summary":"F","locale":"en_US.utf8","statistics":"u=42.32  s=17.74  cu=2267.90  cs=211.54  scripts=2634  tests=1179336","failures":[{"result_id":637673,"failure":{"status":"FAILED","test":"../t/porting/authors.t","id":3850,"extra":"1\nNon-zero exit status: 1"},"failure_id":3850},{"failure":{"id":3955,"test":"../t/porting/podcheck.t","status":"FAILED","extra":"179"},"result_id":637673,"failure_id":3955}],"stat_tests":1179336,"io_env":"locale","stat_cpu_time":2539.5,"id":637673,"config_id":395526}],"duration":10360,"id":395526,"cc":"cc"}],"config_count":2,"cpu_count":"4","sconfig_id":1,"lang":"en_US.UTF-8","reporter":"","smoke_branch":"blead","cpu_description":" (100 MHz)","lc_all":"en_US.UTF-8","harness3opts":"","summary":"FAIL(F)","applied_patches":"SMOKE79950615ae6d4a4ca72bf1b913b8e2842bd927e4","smoke_perl":"5.32.1","manifest_msgs":"","git_describe":"v5.39.5-79-g79950615ae","osversion":"6.1.21-v8+ [Raspbian GNU/Linux 11.8 (bullseye)]","skipped_tests":"","architecture":"aarch64","username":"pi","duration":19001,"compiler_msgs":"scope.c: In function ‘Perl_leave_scope’:\nhandy.h:99:35: warning: ‘a2.any_uv’ may be used uninitialized in this function [-Wmaybe-uninitialized]\nscope.c:1117:21: note: ‘a2.any_uv’ was declared here","perl_id":"5.39.6","log_file":"log file removed","hostname":"fikkie","smoke_date":"2023-12-05T19:47:10Z"}