wsalmonct commented on issue #2151:
URL: https://github.com/apache/buildstream/issues/2151#issuecomment-4924652621

   thank you @abderrahim for pointing me to the answer
   
   ```
   toolchain-2026-06-03 src # bst shell components/python3-mkdocs.bst --mount 
/src/tests/ /doc/ -- mkdocs build -f /doc/config.yml
   [--:--:--][        ][    main:core activity                 ] START   
Loading elements
   [00:00:00][        ][    main:core activity                 ] SUCCESS 
Loading elements
   [--:--:--][        ][    main:core activity                 ] START   
Resolving elements
   [00:00:00][        ][    main:core activity                 ] SUCCESS 
Resolving elements
   [--:--:--][        ][    main:core activity                 ] START   
Initializing remote caches
   [00:00:02][        ][    main:core activity                 ] SUCCESS 
Initializing remote caches
   [--:--:--][        ][    main:core activity                 ] START   Query 
cache
   [00:00:00][        ][    main:core activity                 ] SUCCESS Query 
cache
   [--:--:--][d37eff3b][    main:components/python3-mkdocs.bst ] START   
Staging dependencies
   [00:00:00][d37eff3b][    main:components/python3-mkdocs.bst ] SUCCESS 
Staging dependencies
   [--:--:--][d37eff3b][    main:components/python3-mkdocs.bst ] START   
Integrating sandbox
   [00:00:00][d37eff3b][    main:components/python3-mkdocs.bst ] SUCCESS 
Integrating sandbox
   [--:--:--][d37eff3b][    main:components/python3-mkdocs.bst ] STATUS  
Running command
   
       mkdocs build -f /doc/config.yml
   
   INFO    -  Cleaning site directory
   INFO    -  Building documentation to directory: /doc/site
   INFO    -  Documentation built in 0.08 seconds
   ```
   
   I still think that bst needs to provide a much more helpful error message :) 
so still think this is a bug


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to