BuildStream-Migration-Bot opened a new issue #1393: URL: https://github.com/apache/buildstream/issues/1393
[See original issue on GitLab](https://gitlab.com/BuildStream/buildstream/-/issues/1393) In GitLab by [[Gitlab user @tristanvb]](https://gitlab.com/tristanvb) on Sep 20, 2020, 07:27 One of our most frequently regressing problems has appeared once again. Testing the latest port of `freedesktop-sdk` with master today I observed the following: ``` [--:--:--][f7ebac9b][ build:bootstrap/build/gcc-stage1.bst] START freedesktop-sdk/bootstrap-build-gcc-stage1/f7ebac9b-build.4071769.log [--:--:--][f7ebac9b][ build:bootstrap/gnu-config.bst ] STATUS Staging bootstrap/gnu-config.bst/41de65c5 [--:--:--][f7ebac9b][ build:bootstrap/build/base-sdk/filtered.bst] STATUS Staging bootstrap/build/base-sdk/filtered.bst/5747e62f [--:--:--][f7ebac9b][ build:bootstrap/build/base-sdk/symlinks.bst] STATUS Staging bootstrap/build/base-sdk/symlinks.bst/b4e168e0 [--:--:--][f7ebac9b][ build:bootstrap/build/base-sdk.bst ] STATUS Staging bootstrap/build/base-sdk.bst/36b8498b [--:--:--][f7ebac9b][ build:bootstrap/build/binutils-stage1.bst] STATUS Staging bootstrap/build/binutils-stage1.bst/8f278972 ``` Here we can see that we are staging a bunch of elements in order to build `bootstrap/build/gcc-stage1.bst`. Note: * The cache key of `gcc-stage1.bst` is correctly printed for all lines * The message content shows the correct elements being staged * The element name shown in the UI is **incorrect** * Even though we issue log messages on dependency elements, we are supposed to be stamping those messages with the `task_id` * The frontend is supposed to favor the `task_id` to print the element name here if one is present, instead of the `plugin_id` As a secondary note, I think that these messages are supposed to be `silent_nested=True`, I think this is a bit overly verbose. ---------------------------------------------------------------- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: [email protected]
