New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 595230 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner:
Last visit > 30 days ago
Closed: Jun 2016
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug



Sign in to add a comment

Auto bug filing failed in test_push when calling check_bug_filed_and_deduped

Project Member Reported by dshi@chromium.org, Mar 16 2016

Issue description

INFO:apiclient.discovery:URL being requested: https://monorail-staging.appspot.com/_ah/api/monorail/v1/projects/chromium/issues/591329/comments?alt=json&maxResults=50
INFO:apiclient.discovery:URL being requested: https://monorail-staging.appspot.com/_ah/api/monorail/v1/projects/chromium/issues/591329/comments?alt=json&sendEmail=false
INFO:root:Updated  issue 591329 , comment Issue closed by test_push script., labels '', status WontFix.
INFO:apiclient.discovery:URL being requested: https://monorail-staging.appspot.com/_ah/api/monorail/v1/projects/chromium/issues?q=%22ANCHOR++TestFailure%7Bpush_to_prod%2Cdummy_Fail.Fail%2Calways+fail%7D%22&startIndex=1&can=all&maxResults=50&alt=json
INFO:apiclient.discovery:URL being requested: https://monorail-staging.appspot.com/_ah/api/monorail/v1/projects/chromium/issues/591329/comments?alt=json&maxResults=50
Test for pushing to prod failed:

Auto bug file failed. Multiple issues (591329, 591329) filed with marker TestFailure{push_to_prod,dummy_Fail.Fail,always fail}
INFO:apiclient.discovery:URL being requested: https://www.googleapis.com/discovery/v1/apis/gmail/v1/rest
INFO:apiclient.discovery:URL being requested: https://www.googleapis.com/gmail/v1/users/me/messages/send?alt=json
DEBUG:root:Email sent: 1537ddcab644996a
Traceback (most recent call last):
  File "/usr/local/autotest/site_utils/test_push.py", line 569, in <module>
    sys.exit(main())
  File "/usr/local/autotest/site_utils/test_push.py", line 535, in main
    check_bug_filed_and_deduped(old_issue_ids)
  File "/usr/local/autotest/site_utils/test_push.py", line 474, in check_bug_filed_and_deduped
    'filed with marker %s') % (ids, BUG_ANCHOR))
__main__.TestPushException: Auto bug file failed. Multiple issues (591329, 591329) filed with marker TestFailure{push_to_prod,dummy_Fail.Fail,always fail}

Note that the issue ids in "Multiple issues" are the same. It's either a bug in monorail that returns duplicated entries, or a bug in reporting api that failed in dedupe.

shuqianz, could you please take a look?
 
Project Member

Comment 1 by bugdroid1@chromium.org, Mar 18 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/049cccd8d07cf02395d9697eacfafba7296fed8a

commit 049cccd8d07cf02395d9697eacfafba7296fed8a
Author: Shuqian Zhao <shuqianz@chromium.org>
Date: Fri Mar 18 02:49:51 2016

[autotest] teach test_push to wait 5s after closing a bug

Monorail server has some latency when closing bugs, which causes the
test_push script failed at checking whether successfully closed a bug.
Let test_push to wait 5s and then query again.

BUG= chromium:595230 
TEST=Test locally

Change-Id: Ifa3616b80c7b49b0140014970d1fa22cfc42998a
Reviewed-on: https://chromium-review.googlesource.com/333388
Commit-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Shuqian Zhao <shuqianz@chromium.org>

[modify] https://crrev.com/049cccd8d07cf02395d9697eacfafba7296fed8a/site_utils/test_push.py

Comment 2 by dshi@chromium.org, Mar 21 2016

The sleep is also needed in close_bug call.

Comment 3 by dshi@chromium.org, Mar 21 2016

Also, 5s seems to be no enough. I'm still seeing the error in test_push run:
Auto bug file failed. Multiple issues (591344, 591344) filed with
marker TestFailure{push_to_prod,dummy_Fail.Fail,always fail}
Project Member

Comment 4 by bugdroid1@chromium.org, Mar 21 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/a7e5da88871117ed367995959ec66d6d939ee67a

commit a7e5da88871117ed367995959ec66d6d939ee67a
Author: Shuqian Zhao <shuqianz@chromium.org>
Date: Mon Mar 21 17:56:39 2016

[autotest] teach test_push to wait 10s after closing a bug

Teach test_push script to wait 10s rather than 5s when closing a bug.

BUG= chromium:595230 
TEST=Test locally

Change-Id: If2cf89cd27ef20b8dd8ec94f3d2b6a286d36189f
Reviewed-on: https://chromium-review.googlesource.com/334099
Commit-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>

[modify] https://crrev.com/a7e5da88871117ed367995959ec66d6d939ee67a/site_utils/test_push.py

Need to add a retry to check_bug_filed_and_deduped
Issue 590894 has been merged into this issue.
Project Member

Comment 7 by bugdroid1@chromium.org, Apr 13 2016

The following revision refers to this bug:
  https://chromium.googlesource.com/chromiumos/third_party/autotest/+/9866ab11ae57866ec00b7066aac372e4254ceb24

commit 9866ab11ae57866ec00b7066aac372e4254ceb24
Author: Shuqian Zhao <shuqianz@chromium.org>
Date: Tue Apr 05 22:55:13 2016

[autotest] add retry for closing bug function in test_push.py

Due to the monorail flake, the test_push sometimes failed at the
function of closing the deduping bugs. Add retry to get pass the flake.

BUG= chromium:595230 
TEST=Running test_push

Change-Id: I90e54ca153377a56e89d6796568b24c726b86ac1
Reviewed-on: https://chromium-review.googlesource.com/337186
Commit-Ready: Shuqian Zhao <shuqianz@chromium.org>
Tested-by: Shuqian Zhao <shuqianz@chromium.org>
Reviewed-by: Dan Shi <dshi@google.com>

[modify] https://crrev.com/9866ab11ae57866ec00b7066aac372e4254ceb24/site_utils/test_push.py
[modify] https://crrev.com/9866ab11ae57866ec00b7066aac372e4254ceb24/site_utils/test_push_unittest.py

Comment 8 by benhenry@google.com, Apr 26 2016

Components: Infra>Client>ChromeOS
Labels: -Infra-ChromeOS
Status: WontFix (was: Untriaged)
Close it, since test_push has not tested bug_filing any more.

Sign in to add a comment