Smoke [blead] v5.23.8-76-g33e9fee FAIL(X) os/390 24.00 (2964/)

Karl Williamson

2016-03-05 17:31:38 UTC

Automated smoke report for branch blead 5.23.9 patch 33e9feea41a1ba8a58b32a5478d1dda0f7bcd052
v5.23.8-76-g33e9fee
RS12: 2964 (2964/)
on os/390 - 24.00
using c99 version
smoketime 4 hours 48 minutes (average 2 hours 24 minutes)
Summary: FAIL(X)
O = OK F = Failure(s), extended report at the bottom
X = Failure(s) under TEST but not under harness
? = still running or test results not (yet) available
Build failures during: - = unknown or N/A
c = Configure, m = make, M = make (after miniperl), t = make test-prep
v5.23.8-76-g33e9fee Configuration (common) none
----------- ---------------------------------------------------------
X X X X -Dusedl

+----- PERLIO = perlio -DDEBUGGING

+------- PERLIO = stdio -DDEBUGGING

+--------- PERLIO = perlio

+----------- PERLIO = stdio
SMOKE33e9feea41a1ba8a58b32a5478d1dda0f7bcd052
# One test name on a line
Failures: (common-args) none
[stdio/perlio] -Dusedl
[stdio/perlio] -DDEBUGGING -Dusedl
../t/re/pat_advanced.t.................. .............................................
FAILED-
-no leader found
This file there is <00> byte. So it is not converted encoding UTF-8 in UTF-EBCDIC

That should not be. Could it be that the permissions are such that it's
not getting the contents it should have. Attached is the current ASCII
version to try out. You can see if your translation tool is working
properly on it.

Line 2461 <00> byte.
If the file has 00 byte, I define this as a binary file and not converting it
I will redo the tool and will determine the binary files by file name extension.

Another option to consider is one that works well for Perl itself. It
has the -T and -B operators to determine binary-ness of a file. The
implementation takes advantage of the fact that if a string is legal
UTF-8 syntax, the odds that it was meant to instead be binary are
essentially zero for any sequence longer than a few bytes.

These operations look at the first file block, and if it is valid UTF-8,
the file is not binary. (We have to account for the possibility of the
final character straddling the boundary with the next block, but it is
easy to do that.) If it isn't UTF-8, it may or may not be binary, but
that's not your problem here. Using the file name extension in general
is problematic, but clearly a .t or .pm extension isn't going to be
binary, for example.

Post by Karl Williamson

--
Report by Test::Smoke v1.6 running on perl 5.22.0
(Reporter v0.052 / Smoker v0.045)
--
Regards,
Yaroslav Kuzmin
Developer C/C++ ,z/OS , Linux
3 Zhukovskiy Street · Miass, Chelyabinsk region 456318 · Russia
Tel: +7.922.2.38.33.38
Web: www.rocketsoftware.com
================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 877.328.2932 ■
+1 781.577.4321
Manage Your Subscription Preferences -
http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of Rocket Software,
Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the
intended recipient, please notify Rocket Software immediately and destroy all copies of this
communication. Thank you.

================================
Rocket Software, Inc. and subsidiaries ■ 77 Fourth Avenue, Waltham MA 02451 ■ +1 877.328.2932 ■ +1 781.577.4321
Manage Your Subscription Preferences - http://info.rocketsoftware.com/GlobalSubscriptionManagementEmailFooter_SubscriptionCenter.html
Privacy Policy - http://www.rocketsoftware.com/company/legal/privacy-policy
================================
This communication and any attachments may contain confidential information of Rocket Software, Inc. All unauthorized use, disclosure or distribution is prohibited. If you are not the intended recipient, please notify Rocket Software immediately and destroy all copies of this communication. Thank you.