tony at develop-help
Jul 26, 2012, 4:38 PM
Post #2 of 4
(111 views)
Permalink
|
On Thu, Jul 26, 2012 at 06:14:23PM -0400, bulk 88 wrote:
>
> I've been looking at perl.daily-build.reports using google groups, and I can't seem to find a single cygwin smoke in any perl release (5.16 or 5.17, maybe 5.14) that ever passed in 2012. Is it normal for the cygwin smokes to never pass?
>
Yes, they never pass.
The call_checker.t failure is ticket 78502.
The Win32 failure is https://rt.cpan.org/Ticket/Display.html?id=66751
The Win32-Unicode failure is https://rt.cpan.org/Ticket/Display.html?id=74332
The Net-Ping failures I was looking at, the icmp one is a permissions
problem (it should skip), I couldn't figure out the udp failure, but I
haven't spent much time on it.
I haven't followed up on the sigdispatch.t failure, it appears[1] to have
started between b7256f66 and 32995a38 where I had a big break in smoke
testing.
Tony
[1]
mysql> select left(pr.sha, 8) as "sha", ordering as "ord", body like('%sigdispatch%') from parsed_reports pr, git_commits gc where gc.sha = pr.sha and os like 'cygwin%' and gc.branch = 'blead' order by 2 desc limit 255,10;
+----------+-------+----------------------------+
| sha | ord | body like('%sigdispatch%') |
+----------+-------+----------------------------+
| 1d8dd5fc | 43926 | 1 |
| 6d91e957 | 43920 | 1 |
| ad790500 | 43917 | 1 |
| c2654555 | 43915 | 1 |
| 32995a38 | 43914 | 1 |
| b7256f66 | 42829 | 0 |
| d39de893 | 42440 | 0 |
| 985b9e54 | 42433 | 0 |
| ff55a019 | 42394 | 0 |
| 656b40da | 42147 | 0 |
+----------+-------+----------------------------+
10 rows in set (4.03 sec)
|
