www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sebb (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (INFRA-7119) Whimsy self-subcribe data is stale
Date Fri, 03 Jan 2014 11:38:50 GMT

    [ https://issues.apache.org/jira/browse/INFRA-7119?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13861453#comment-13861453
] 

Sebb commented on INFRA-7119:
-----------------------------

Looks like the SVN update has failed for the Whimsy software itself; the most recent changes
I made have not been picked up, whereas the earlier ones were picked up quickly.

I wonder if there could be an interaction between the cron job and running the code?
Perhaps the ruby runtime locks some of the workspace files and causes the update to fail?
I was testing the changes so it's quite possible that the update ran whilst the CGI was running.

[I could not find where the scripts run by the cronjobs on whimsy are held in SVN]

> Whimsy self-subcribe data is stale
> ----------------------------------
>
>                 Key: INFRA-7119
>                 URL: https://issues.apache.org/jira/browse/INFRA-7119
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Whimsy
>         Environment: https://whimsy.apache.org/committers/subscribe
>            Reporter: Sebb
>            Assignee: Sam Ruby
>
> The Whimsy self-subscribe page does not have mesos as a TLP, which means it must be using
a very stale version of .archives.
> 1) Please could the data be updated
> 2) it would help if the page showed the details of the data file it was using



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Mime
View raw message