I'm not in a position to debug these now but wanted to document:

that I've been getting some cron build fail mails from Jenkins:

See

------------------------------------------
Started by timer
Building remotely on www2 in workspace
[groups.d.o_cron] $ /bin/sh -xe /home/bender/tmp/hudson8529477747973410428.sh
+ export PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/bin
+ PATH=/usr/kerberos/bin:/usr/local/bin:/bin:/usr/bin:/usr/local/bin
+ export TERM=dumb
+ TERM=dumb
+ drush='drush -r /var/www/groups.drupal.org/htdocs -l groups.drupal.org'
+ drush -r /var/www/groups.drupal.org/htdocs -l groups.drupal.org cron -v
Initialized Drupal 6.28 root directory at [notice]
/var/www/groups.drupal.org/htdocs
Initialized Drupal site groups.drupal.org at sites/default [notice]
WD aggregator: The feed from UUID-related issues seems to be broken, [warning]
due to an error "Processing Instruction not finished" on line 39.
WD aggregator: The feed from @DrupalFit seems to be broken, due to [warning]
"410 Gone".
WD aggregator: The feed from @SBDrupal seems to be broken, due to [warning]
"410 Gone".
WD aggregator: The feed from Issues in the core token system queue [warning]
seems to be broken, due to an error "Processing Instruction not
finished" on line 39.
WD aggregator: The feed from Token module issues seems to be broken, [warning]
due to an error "Processing Instruction not finished" on line 39.
WD aggregator: The feed from @mobiledrupal seems to be broken, due to [warning]
"410 Gone".
WD aggregator: The feed from @DrupalCoworking seems to be broken, due [warning]
to "410 Gone".
WD aggregator: The feed from @ladrupal seems to be broken, due to [warning]
"410 Gone".
Indexing node 311558. [ok]
Indexing node 24119. [ok]
Indexing node 24119. [ok]
Indexing node 311558. [ok]
WD Apache Solr: Adding 2 documents. [notice]
WD Apache Solr: Indexing succeeded on 2 documents [info]
WD Apache Solr Multisite: Fetched site meta data [notice]
WD l10n_update: Automatically checked 0 translations, updated 0. [notice]
WD cron: Cron run completed. [notice]
Cron run successful. [success]
The feed from UUID-related issues seems to be broken, because of [error]
error "Processing Instruction not finished" on line 39.
The feed from Issues in the core token system queue seems to be [error]
broken, because of error "Processing Instruction not finished" on
line 39.
The feed from Token module issues seems to be broken, because of [error]
error "Processing Instruction not finished" on line 39.
The feed from @DrupalFit seems to be broken, because of error "410 [status]
Gone".
The feed from @SBDrupal seems to be broken, because of error "410 [status]
Gone".
The feed from @mobiledrupal seems to be broken, because of error "410 [status]
Gone".
The feed from @DrupalCoworking seems to be broken, because of error [status]
"410 Gone".
The feed from @ladrupal seems to be broken, because of error "410 [status]
Gone".

Support from Acquia helps fund testing for Drupal Acquia logo

Comments

ezra-g’s picture

I looked into the failures related to the Twitter feeds above and found that the feeds pointed to URLs based on the discontinued Twitter Rest API v1:

api.twitter.com_1_statuses_user_timeline.rss_screen_name_DrupalCoworking.png

I deleted these feeds. However, Several of the remaining feeds still report an error similar to:

The feed from Issues in the core token system queue seems to be [error]
broken, because of error "Processing Instruction not finished" on
line 39.

ezra-g’s picture

Title: Multiple cron run fails » Multiple cron run fails related to Aggregator