Opened 2 years ago

Closed 18 months ago

#27299 closed defect (duplicate)

docker docbuild is slow

Reported by: saraedum Owned by:
Priority: major Milestone: sage-duplicate/invalid/wontfix
Component: distribution Keywords:
Cc: embray, jdemeyer, slelievre Merged in:
Authors: Reviewers:
Report Upstream: N/A Work issues:
Branch: Commit:
Dependencies: Stopgaps:

Status badges

Description (last modified by saraedum)

In the lastest beta 8.7.beta4, the docker builds fail their self test. Namely we run make and then we time another run of make (after deleting some cheap build artifacts.) This second run takes 400 seconds since this beta.

Have there been any changes to sphinx that could cause this? For some reason we seem to be rebuilding most of the reference manual:

[dochtml] [combinat ] updating environment: 0 added, 199 changed, 0 removed

Change History (9)

comment:1 Changed 2 years ago by saraedum

  • Description modified (diff)

comment:3 Changed 2 years ago by saraedum

Ok. This is unrelated to the latest beta. This changed earlier most likely. Anyway, the docbuild is taking too long at the moment at rebuilding. At least in the docker setup. It might be that we are throwing something away that is needed for the caching by now. But I doubt it because it used to work but there were always a few files that failed to be taken from the cache…

comment:4 Changed 2 years ago by embray

I noticed this as well. I wasn't sure if it was a fluke or what, or if the docbuild just...got slower for some unexplained reason.

Could you point out where the "cheap build artifacts" are being deleted? Is there an easy way I can run this test locally so I could maybe find out where it changed (e.g. by running git bisect)?

comment:5 Changed 2 years ago by embray

  • Milestone changed from sage-8.7 to sage-8.8

Ticket retargeted after milestone closed (if you don't believe this ticket is appropriate for the Sage 8.8 release please retarget manually)

comment:6 Changed 22 months ago by embray

  • Milestone sage-8.8 deleted

As the Sage-8.8 release milestone is pending, we should delete the sage-8.8 milestone for tickets that are not actively being worked on or that still require significant work to move forward. If you feel that this ticket should be included in the next Sage release at the soonest please set its milestone to the next release milestone (sage-8.9).

comment:7 Changed 19 months ago by saraedum

  • Milestone set to sage-duplicate/invalid/wontfix
  • Status changed from new to needs_review

This is essentially adressed in #28502 though this does not seem to be the full answer yet.

comment:8 Changed 19 months ago by saraedum

  • Status changed from needs_review to positive_review

comment:9 Changed 18 months ago by chapoton

  • Resolution set to duplicate
  • Status changed from positive_review to closed
Note: See TracTickets for help on using tickets.