You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@buildstream.apache.org by GitBox <gi...@apache.org> on 2022/08/25 12:26:35 UTC

[GitHub] [buildstream] jjardon opened a new issue, #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

jjardon opened a new issue, #1742:
URL: https://github.com/apache/buildstream/issues/1742

   Logs here: https://gitlab.gnome.org/GNOME/gnome-build-meta/-/jobs/2231934


-- 
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: commits-unsubscribe@buildstream.apache.org.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] nanonyme commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
nanonyme commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232113948

   There are no delays between attempts though so if it fails five times in rapid sequence, that might break build?


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] nanonyme commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
nanonyme commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232113029

   Looks like also https://github.com/apache/buildstream/blob/bst-1/buildstream/_artifactcache/cascache.py#L1100 there are retries and https://github.com/apache/buildstream/blob/bst-1/buildstream/_artifactcache/cascache.py#L72 UNAVAILABLE is handled


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] jjardon commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
jjardon commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232101767

   Sure, I think we need a new tag as soon as possible 


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] nanonyme commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
nanonyme commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232095597

   @jjardon afaik bst *would* actually retry on this message if it was happening after init. Do you consider this a blocker? I don't think it's a regression and it would be nice to get bst 1.6.8 out as it loosens requirements.


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] nanonyme commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
nanonyme commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232087669

   Looks like it's in a critical place (init). Retrying is hard to handle there.


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org

[GitHub] [buildstream] nanonyme commented on issue #1742: bst1: Seems buidlstream is not trying after receiveing a UNAVAILABLE message

Posted by GitBox <gi...@apache.org>.
nanonyme commented on issue #1742:
URL: https://github.com/apache/buildstream/issues/1742#issuecomment-1232088184

   bst1 design is not great here in the sense init seems to get called throughout the build.


-- 
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: commits-unsubscribe@buildstream.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org