Account Options

  1. Sign in
The old Google Groups will be going away soon, but your browser is incompatible with the new version.
Google Groups Home
« Groups Home
zorba-dev
Home
About this group
Apply for group membership
1-test failures on remote queue
Options
There are currently too many topics in this group that display first. To make this topic appear first, remove this option from another topic.
There was an error processing your request. Please try again.
flag
   1 message - Collapse all  -  Translate all to Translated (View all originals)
The group you are posting to is a Usenet group. Messages posted to this group will make your email address visible to anyone on the Internet.
Your reply message has not been sent.
Your post was successful
 
From:
To:
Cc:
Followup To:
Add Cc | Add Followup-to | Edit Subject
Subject:
Validation:
For verification purposes please type the characters you see in the picture below or the numbers you hear by clicking the accessibility icon. Listen and type the numbers you hear
 
Chris Hillery  
View profile  
 More options Apr 25 2012, 12:01 pm
From: Chris Hillery <chill...@lambda.nu>
Date: Wed, 25 Apr 2012 09:01:04 -0700
Local: Wed, Apr 25 2012 12:01 pm
Subject: 1-test failures on remote queue
Print | Individual message | Show original | Report this message | Find messages by this author

I've looked at the possibly-spurious single test failures on the queue for
the past week. There's no obvious single test causing trouble. One time it
was a data-cleaning test that failed with an HTTP error, probably due to
the webservice being weird; that's annoying, but if it only happened once
we should probably let it slide. Twice it was swig_xqj segfaulting, and
that was for the same merge proposal so I'm assuming it wasn't "spurious"
at all. The other three that I found also seemed either completely random
(cosmic rays?) or possibly indicative of a real problem with the merge
proposal.

For the time being, there's not anything obvious to do. If you have a test
run that fails with one or two test failures that seem completely unrelated
to your changes, please do two things:

1. Re-submit your changes by marking the proposal "Approved" again.
2. Email the CDash page for the failing test run to me - and let me know if
the second test run with the same changes does NOT have that test fail.

If any test proves to be unreliable repeatedly, I'll disable it.

Ceej
aka Chris Hillery


 
You must Sign in before you can post messages.
To post a message you must first join this group.
Please update your nickname on the subscription settings page before posting.
You do not have the permission required to post.
End of messages
« Back to Discussions « Newer topic     Older topic »

Create a group - Google Groups - Google Home - Terms of Service - Privacy Policy
©2013 Google