"bst --debug --verbose build --track-all core/gedit.bst" hangs and prints nothing

Summary

Building gedit with bst --debug --verbose build --track-all core/gedit.bst hangs and prints nothing which indicates two problem: the hanging and the fact that --verbose --debug doesn't indicate which action is executed and probably caused the hang. --verbose --debug should print a ton of information no matter what.

Steps to reproduce

Following https://wiki.gnome.org/Newcomers/BuildSystemComponent:

git clone https://gitlab.gnome.org/GNOME/gnome-build-meta.git
cd /path/to/gnome-build-meta
bst --debug --verbose build --track-all core/gedit.bst

Download of information (probably git clones or tarballs) regularly hang, i.e. after a portion of downloads succeed no download occurs for a long time until the process is terminated. I aborted such a download before this issue started occurring all the time.

What is the current bug behavior?

The process doesn't print anything to console and does't return after 10 minutes, probably never.

What is the expected correct behavior?

The command should start downloading dependencies or building without --verbose --debug. With --verbose --debug at least all blocking tasks should be logged before running them.

Relevant logs and/or screenshots

./.

Possible fixes

./.

Other relevant information

  • BuildStream version affected: 1.1.3-123-g9f77cb66 (built with python3 setup.py build && sudo python3 setup.py install)
  • Debugging shows that the hang is caused by
> /usr/local/lib/python3.6/dist-packages/click-6.7-py3.6.egg/click/core.py(1066)invoke()
-> return _process_result(sub_ctx.command.invoke(sub_ctx))
(Pdb) l
1061 	                cmd_name, cmd, args = self.resolve_command(ctx, args)
1062 	                ctx.invoked_subcommand = cmd_name
1063 	                Command.invoke(self, ctx)
1064 	                sub_ctx = cmd.make_context(cmd_name, args, parent=ctx)
1065 	                with sub_ctx:
1066 ->	                    return _process_result(sub_ctx.command.invoke(sub_ctx))
1067 	
1068 	        # In chain mode we create the contexts step by step, but after the
1069 	        # base command has been invoked.  Because at that point we do not
1070 	        # know the subcommands yet, the invoked subcommand attribute is
1071 	        # set to ``*`` to inform the command that subcommands are executed
(Pdb) n

EDIT: Fixed formatting of code sample (~Chandan)

Edited by Chandan Singh