You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@airflow.apache.org by GitBox <gi...@apache.org> on 2020/12/07 12:11:23 UTC
[GitHub] [airflow] potiuk opened a new issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
potiuk opened a new issue #12879:
URL: https://github.com/apache/airflow/issues/12879
While grouping logs in CI for docs seemed like a good idea, it has a big problem. The grouping and displaying the log sections is done in javascript and with huge amount of logs there, it takes > 30 seconds (and my processor and cooler starts spinning like crazy) when Iopen the docs logs. I think just one big log was much more friendly even if it was a long one (at least until it gets optimized by GA - likely off-loading some of that to the server side).
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk closed issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
Posted by GitBox <gi...@apache.org>.
potiuk closed issue #12879:
URL: https://github.com/apache/airflow/issues/12879
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #12879:
URL: https://github.com/apache/airflow/issues/12879#issuecomment-740834532
I am closing the issue. The new GH UI rolled out today is so much faster that this stopped being a problem!
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #12879:
URL: https://github.com/apache/airflow/issues/12879#issuecomment-739879836
cc: @mik-laj WDYT ?
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #12879:
URL: https://github.com/apache/airflow/issues/12879#issuecomment-740511938
This is reallly annoying, because you have to have the Tab open and visible in the browser while waiting :(. If you switch, it stops loading :(
----------------------------------------------------------------
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:
users@infra.apache.org
[GitHub] [airflow] potiuk commented on issue #12879: Grouping logs in Github Actions for DOCs is super slow (javascript in GA)
Posted by GitBox <gi...@apache.org>.
potiuk commented on issue #12879:
URL: https://github.com/apache/airflow/issues/12879#issuecomment-740511553
How about - similar to what I do in other parts of the build? We have now many steps - we do not need any of the logs unless there is an error. What I do there, I redirect both stderr and and stdout to a file, and unless there is an error, I do not output that file.
This could be done separately for every step and it would significantly speed up checking documentation errors - because we would only see the parts that actually had errors - for all other parts we could simply say "This part of the documentation: COMPLETED"
----------------------------------------------------------------
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:
users@infra.apache.org