Summary: | sys-apps/portage: event loop recursion in Scheduler._task_complete call to BlockerDB.discardBlocker | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Zac Medico <zmedico> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | cyrilmaley |
Priority: | Normal | Keywords: | InVCS, REGRESSION |
Version: | unspecified | ||
Hardware: | All | ||
OS: | All | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 651804, 654390 |
Description
Zac Medico
2018-05-31 04:55:17 UTC
@cyrillic, I think that you must have used the emerge --nodeps/-O option in order to trigger this error, is that right? The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/proj/portage.git/commit/?id=d07a47ff3c06f6e8b2adc21ae29eecae07badc9e commit d07a47ff3c06f6e8b2adc21ae29eecae07badc9e Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-05-31 08:27:45 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-05-31 08:27:45 +0000 emerge: make --nodeps disable --dynamic-deps (bug 656942) Since --nodeps disable's the depgraph's _dynamic_deps_preload code, calls to BlockerDB can trigger inappropriate calls to the FakeVartree _aux_get_wrapper method, triggering event loop recursion. Therefore, make --nodeps disable --dynamic-deps, in order to eliminate the inappropriate _aux_get_wrapper calls. Bug: https://bugs.gentoo.org/656942 pym/_emerge/create_depgraph_params.py | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=763a95a356ab845886e56a72f823f31f6b8a3436 commit 763a95a356ab845886e56a72f823f31f6b8a3436 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-05-31 09:20:23 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-05-31 09:20:37 +0000 sys-apps/portage: fix --nodeps with --keep-going (bug 656942) See: https://gitweb.gentoo.org/proj/portage.git/commit/?id=d07a47ff3c06f6e8b2adc21ae29eecae07badc9e Closes: https://bugs.gentoo.org/656942 Package-Manager: Portage-2.3.40, Repoman-2.3.9 sys-apps/portage/portage-2.3.40.ebuild | 4 ++++ 1 file changed, 4 insertions(+) (In reply to Zac Medico from comment #1) > @cyrillic, I think that you must have used the emerge --nodeps/-O option in > order to trigger this error, is that right? Yes, I was using --nodeps (In reply to cyrillic from comment #4) > (In reply to Zac Medico from comment #1) > > @cyrillic, I think that you must have used the emerge --nodeps/-O option in > > order to trigger this error, is that right? > > Yes, I was using --nodeps Great, then https://gitweb.gentoo.org/proj/portage.git/commit/?id=d07a47ff3c06f6e8b2adc21ae29eecae07badc9e solves the problem. Thanks for reporting! The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cfe44e894ae844ab8768dfd5584506750d0be297 commit cfe44e894ae844ab8768dfd5584506750d0be297 Author: Zac Medico <zmedico@gentoo.org> AuthorDate: 2018-06-06 16:26:12 +0000 Commit: Zac Medico <zmedico@gentoo.org> CommitDate: 2018-06-06 16:27:21 +0000 sys-apps/portage: 2.3.40-r1 revbump for regression fixes Fixes: https://bugs.gentoo.org/656610 Fixes: https://bugs.gentoo.org/656750 Fixes: https://bugs.gentoo.org/656942 Fixes: https://bugs.gentoo.org/657360 Fixes: https://bugs.gentoo.org/657420 Fixes: https://bugs.gentoo.org/657436 Package-Manager: Portage-2.3.40, Repoman-2.3.9 sys-apps/portage/{portage-2.3.40.ebuild => portage-2.3.40-r1.ebuild} | 0 1 file changed, 0 insertions(+), 0 deletions(-) |