#976 Logs for accurate time measurements
Closed: Invalid 4 years ago by praiskup. Opened 4 years ago by iucar.

Consider this build. Right now, it shows "Build time: 11 hours" under "General information", but the build time accounted for each chroot is 8 minutes, 7 minutes and - (pending) respectively. So what does this "11 hours" mean?

This is not very helpful, because, for example, I've detected that some packages try to connect to a DISPLAY after the installation (because R package installation tries to load the package to be sure that the installation was successful). I try to detect these packages because they spend an excessive time to build (eventually, there's a warning and the task succeeds, or there's an error and the task fails), and then I add xvfb-run to the SPEC to solve the issue. But if there are timings like the one above, my detection is not reliable.

How is each timing report measured and how could we improve it?


It has ocurred to me... could this difference be due to the time required to run createrepo for each chroot? Because that's huge! I see tasks with one or two days of total time, but just a few minutes for each chroot!

Consider this build. Right now, it shows "Build time: 11 hours" under "General information", but the build time accounted for each chroot is 8 minutes, 7 minutes and - (pending) respectively. So what does this "11 hours" mean?

Build consists of several buildchroots (BuildChroot class in models.py); so when one of the buildchroots starts, the whole build is considered to start. And similarly, when the last buildchroot finishes, the build is marked as finished.
Seems like by bad luck your buildchroots happened with 11 hours gap between them.

I try to detect these packages because they spend an excessive time to build

There's been, afaik, somebody can correct me, no such API call or command-line option for particular buildchroot (I suppose you are interested in buildchroot timing, not build timing). You can either parse the "humanized" time info near particular chroot, or you can listen on message bus and detect that some build has started a long time ago, and no "ended" message was delivered.

There's been, afaik, somebody can correct me, no such API call or command-line option for particular buildchroot (I suppose you are interested in buildchroot timing, not build timing).

In this case, would this help @iucar? Try

https://copr.fedorainfracloud.org/api_3/build-chroot/<BUILD_ID>/<CHROOT_NAME>

e.g.

https://copr.fedorainfracloud.org/api_3/build-chroot/1024802/fedora-30-x86_64

There is started_on and ended_on with timestamps for that particular chroot.

That's very useful, yes. :)

Metadata Update from @praiskup:
- Issue close_status updated to: Invalid
- Issue status updated to: Closed (was: Open)

4 years ago

Closing since this isn't bug then.

Login to comment on this ticket.

Metadata