#6599 Koji build failed without a reason
Closed: It's all good Opened by tpopela.

Hi,
the build https://koji.fedoraproject.org/koji/taskinfo?taskID=17391659 of webkitgtk4 failed without a reason on armv7hl and arm64. From the build logs it looks that it was still compiling. There is one error mentioned in notification:

: can't commit">

Here is some log from IRC with Dennis:

Hi everyone, can someone explain me why https://koji.fedoraproject.org/koji/taskinfo?taskID=17391659 failed? Is there now some time limit when the compilation have to succeed (if so, it's not enough for WebKitGTK+ ;))
tpopela: there is a timeout of 48 hours
dgilmore, I know about that one :) but from the logs it looks like the task stopped without a reason..
tpopela: I suspect it was killed for using too much memory
it looks like it was linking on armv7hl
dgilmore, no it was building..
though dmesg does not show that
ps axf
gahh
2017-01-23 17:23:14,950 [INFO] koji.TaskManager: Task 17391684 (pid 9103) exited with status 0
2017-01-23 17:23:15,157 [INFO] koji.TaskManager: Expiring subsession 26602149 (task 17391684)
dgilmore, what does that mean? That we have no clue? :)
tpopela: that mock said it finished fine :(
dgilmore, hmm let me start a new build and we will see if it was some hiccup..
thats my best suggestion
the failure in koji is : can't commit
which I think is because there was no rpms
but the mock_output.log agrees the build completed okay
which is clearly did not
actually it says that the build started and nothing more
dgilmore, I will create a bug on pagure and maybe someone will chime in with some idea..
tpopela: its either rpmbuild or mock that failed
I suspect mock


Metadata Update from @ausil:
- Issue assigned to mikem

The most recent version is webkitgtk4-2.20.1-1.fc26

Closing since newer build since ticket filed.

Metadata Update from @syeghiay:
- Issue close_status updated to: It's all good
- Issue status updated to: Closed (was: Open)

Metadata