[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedor
From: |
NO-REPLY |
Subject: |
[Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora |
Date: |
Tue, 24 Dec 2019 20:16:31 +0000 |
The Buildbot has detected a failed build on builder clang-fedora while building
octave.
Full details are available at:
http://buildbot.octave.org:8010/#builders/9/builds/1376
Buildbot URL: http://buildbot.octave.org:8010/
Worker for this Build: das_fc25-x86_64
Build Reason: <unknown>
Blamelist: Kai T. Ohlhus <address@hidden>, Markus Mützel <address@hidden>,
Pantxo Diribarne <address@hidden>, Rik <address@hidden>, Torsten Lilge
<address@hidden>
BUILD FAILED: failed configure (failure)
Sincerely,
-The Buildbot
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, (continued)
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/14
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/14
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/14
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/14
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/15
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/15
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/15
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/15
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/16
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/16
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora,
NO-REPLY <=
- [Octave-buildbot] Buildbot failure in GNU Octave Buildbot on clang-fedora, NO-REPLY, 2019/12/31