Opened on 02/01/2017 at 03:08:09 PM
Last modified on 02/15/2017 at 10:16:23 AM
#4860 new change
Reproduction of a trac bug [x not in list]
| Reported by: | saroyanm | Assignee: | |
|---|---|---|---|
| Priority: | Unknown | Milestone: | |
| Module: | Unknown | Keywords: | |
| Cc: | philll | Blocked By: | |
| Blocking: | #4862 | Platform: | Unknown / Cross platform |
| Ready: | no | Confidential: | no |
| Tester: | Unknown | Verified working: | no |
| Review URL(s): | |||
Description (last modified by saroyanm)
Background
This is a bug reproduction ticket, to reproduce the behavior of #4846 and #4822, currently each time somebody comments under that tickets the error message below shows up:
Trac detected an internal error: ValueError: list.remove(x): x not in list
The actions that caused the error was:
step 1) made #4822 blocked by #4846
step 2) Removed Blocking #4846 from #4822
Attachments (0)
Change History (14)
comment:1 Changed on 02/01/2017 at 03:09:11 PM by saroyanm
- Blocked By 4861 added
comment:2 Changed on 02/01/2017 at 03:09:31 PM by saroyanm
- Blocked By 4861 removed
comment:3 Changed on 02/01/2017 at 03:12:32 PM by saroyanm
- Blocking 4861 added
comment:4 Changed on 02/01/2017 at 03:12:47 PM by saroyanm
- Blocking 4861 removed
comment:5 Changed on 02/01/2017 at 03:14:51 PM by saroyanm
- Sensitive set
comment:6 Changed on 02/01/2017 at 03:15:44 PM by saroyanm
- Blocked By 4861 added
comment:7 Changed on 02/01/2017 at 03:15:53 PM by saroyanm
- Blocked By 4861 removed
comment:8 Changed on 02/01/2017 at 03:18:07 PM by saroyanm
- Blocking 4862 added
comment:9 Changed on 02/01/2017 at 03:21:03 PM by saroyanm
- Blocking 4861 added
comment:10 Changed on 02/01/2017 at 03:21:22 PM by saroyanm
- Blocking 4861 removed
comment:11 Changed on 02/01/2017 at 03:41:46 PM by saroyanm
- Description modified (diff)
- Summary changed from Reproduction of a trac bug [blocked by] to Reproduction of a trac bug [x not in list]
comment:12 Changed on 02/01/2017 at 03:45:48 PM by saroyanm
- Cc philll added
comment:13 Changed on 02/01/2017 at 03:48:16 PM by saroyanm
comment:14 Changed on 02/15/2017 at 10:16:23 AM by saroyanm
- Sensitive unset
Note: See
TracTickets for help on using
tickets.
@Phill I'm not being able to reproduce, considering the fact that the initial ticket was created not by the person who performed dependency changes on tickets, I thought maybe it make sense if somebody who is not the author of the ticket can try to add dependency in one ticket and remove from another, to be completely sure that it's not the case.