Vít Ondruch píše v St 28. 02. 2018 v 10:35 +0100: > Can the logs actually contain timestamps with timezone? There's a timezone offset at the beginning of the log: 2018-02-28 00:33:30 [INFO ] Current timezone offset: +00:00 > And was the compose successful today or not. Looking at > > https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-201 > 80228.n.0/logs/global/pungi.global.log > > it probably was, but it is not obvious from the log. It did not actually finish, the status is still STARTED: https://kojipkgs.fedoraproject.org/compose/rawhide/Fedora-Rawhide-20180 228.n.0/STATUS If the compose is successful, the log will say so explicitly: 2018-02-27 20:46:57 [INFO ] Compose finished: /mnt/koji/compose/updates/Fedora-Epel-7-updates-testing-20180227.1 Even on failure there should be indication: 2018-02-27 14:34:22 [CRITICAL] Compose failed: /mnt/koji/compose/rawhide/Fedora-Rawhide-20180227.n.0 Lubomír > > Vít > > > > Dne 16.2.2018 v 21:14 Adam Williamson napsal(a): > > On Fri, 2018-02-16 at 14:34 +0100, Vít Ondruch wrote: > > > I wish the compose process was more transparent. May be it is > > > just me, > > > but I don't know where to start looking when I don't get the > > > daily > > > compose report. > > > > https://kojipkgs.fedoraproject.org/compose/ > > > > All composes initially happen there. Rawhide composes happen in the > > rawhide/ subdirectory. Branched happen in the branched/ > > subdirectory. > > Each compose directory contains logs. The usual process for > > debugging > > failed composes is to look at the pungi.global.log file, which > > usually > > indicates what the failed fatal task was, get the task ID or full > > task > > URL from that log, then go to Koji and look at the actual failed > > task > > and figure out what went wrong with it. > > > > > And the compose report email does pretty bad job explaining where > > > the > > > information comes from etc. > > > > The compose reports are generated by https://pagure.io/compose-util > > s , > > which is called by the scripts that actually run the composes, > > which > > live in https://pagure.io/pungi-fedora , along with (most of) the > > Fedora-specific compose configuration bits. > > https://pagure.io/pungi-fedora/blob/master/f/nightly.sh is the > > script > > that runs the Rawhide composes. Branched composes are run by the > > copy > > of the same script on the appropriately-numbered branch. > > (Personally I > > hate these scripts and the branching system, FWIW, and would much > > prefer to rewrite them entirely, but Mohan has said he's going to > > work > > on that and it's more his job than it is mine, so I'm deferring to > > him > > on that one). > > _______________________________________________ > devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx _______________________________________________ devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
