Page MenuHomePhabricator

Mark test build as useless due to non-test issues (beta, jenkins, etc)
Closed, ResolvedPublic

Description

From the QA mailing list today:

<quote name="Jon Robson" date="2014-05-01" time="10:00:38 -0700">

When I visit the dashboard at
https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome/
and click on this
https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-chrome/416/
I can see that there was one test failure. When I review the test I
notice this was due to an issue with betalabs and shouldn't have
failed as the test wasn't valid.

Is there anyway we could update the UI so we could mark these tests
yellow or some other colour to show they are a false positive. It
would be great to be able to manually review these tests and save them
being reviewed more than once...


Version: wmf-deployment
Severity: enhancement

Details

Reference
bz64957

Event Timeline

bzimport raised the priority of this task from to Medium.Nov 22 2014, 3:21 AM
bzimport set Reference to bz64957.

Change 131940 had a related patch set uploaded by Hashar:
Allow user to claim failed build

https://gerrit.wikimedia.org/r/131940

Change 131940 merged by jenkins-bot:
Allow user to claim failed build

https://gerrit.wikimedia.org/r/131940

Jobs updated. Pending verification and we might want to document the feature somewhere.

Thanks guys for such the quick response. I currently can't work out how to claim older failed jobs so I can't test it - is this possible?

What is the workflow?

I went to https://wmf.ci.cloudbees.com/job/MobileFrontend-en.m.wikipedia.beta.wmflabs.org-linux-firefox/541/ but I don't see a claim link there.

If I visit https://integration.wikimedia.org/ci/claims/? I see two things that can be claimed - will future failed jobs show up here?

The Claim plugin is only allowed on the Wikimedia instances and only on the browser tests jobs listed at https://integration.wikimedia.org/ci/view/BrowserTests/

I haven't noticed the link https://integration.wikimedia.org/ci/claims/ , that it is a nice finding :-)

I lost my access to Cloudbees and we will get all jobs migrated whenever Zeljkof comes back. So I am not sure whether it is worth the effort to install Claim there (if at all possible).

Once you got some experience with claiming builds, would you like to advertise it to the whole engineering and dev community? It might have usages beyond browsertests.

Okay.. I see how this works but until we move MobileFrontend away from Cloudbees and generate emails from integration.wikimedia.org it's near impossible for me to provide useful feedback on how this works. I'll wait patiently :)

Thanks for the work so far!

The browser tests have been migrated out of Cloudbees to Wikimedia Jenkins. They should all have the claim plugin enabled now.

greg renamed this task from Mark flaky tests in Jenkins to Mark test build as useless due to non-test issues (beta, jenkins, etc).Mar 27 2015, 6:41 PM
greg set Security to None.