You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docker compose takes really long to start up at "INFO:manifest:Updating manifest". It attempts to rebuild manifest file and which takes long time. Can we include the right manifest generation / build to the image so it is quicker to spin up docker container please?
I can see from Dockerfile https://github.com/cta-wave/WMAS-deploy/blob/wmas2021/Dockerfile it runs "RUN ./wpt manifest --no-download --rebuild" already, however, it seems that the manifest built again when container is starting. Is it required to build manifest again?
The text was updated successfully, but these errors were encountered:
We know about this for a little while now and had several attempts to fix this (the line in the docker file is one attempt). At this point, what we can do about it is either ask the developers of the original wpt runner or try to modify the code of the wpt runner (which we didn't touch so far).
I don't really like the idea of modifying the original test runner code, as this would potentially introduce more conflicts when syncing with upstream and when merging changes back into the original wpt project.
@FritzHeiden Did you open an issue against the original WPT runner to see how they react? Sure they may react negatively or not at all but you'll never know if you don't try?
@FritzHeiden do you know which WMAS versions have this issue please? I can see WMAS2018 is quick to start up. Is this because wpt runner for WMAS2018 runs differently?
Docker compose takes really long to start up at "INFO:manifest:Updating manifest". It attempts to rebuild manifest file and which takes long time. Can we include the right manifest generation / build to the image so it is quicker to spin up docker container please?
I can see from Dockerfile https://github.com/cta-wave/WMAS-deploy/blob/wmas2021/Dockerfile it runs "RUN ./wpt manifest --no-download --rebuild" already, however, it seems that the manifest built again when container is starting. Is it required to build manifest again?
The text was updated successfully, but these errors were encountered: