#3241 new enhancement

RSB sporadically fails when fetching rtems-tools

Reported by: Christian Mauderer Owned by:
Priority: normal Milestone: Indefinite
Component: tool/rsb Version:
Severity: normal Keywords:
Cc: Blocked By:
Blocking:

Description

Sporadically the rtems source builder fails with a error message like the following:

...
package: rtems-tools-HEAD-1
git: reset: git://git.rtems.org/rtems-tools.git
git: fetch: git://git.rtems.org/rtems-tools.git -> sources/git/rtems-tools.git
error: git command failed (/usr/bin/git): 128
Build FAILED
  See error report: rsb-report-rtems-tools-HEAD-1.txt
error: git command failed (/usr/bin/git): 128
Build Set: Time 0:28:42.787936
Build FAILED

The error report in rsb-report-rtems-tools-HEAD-1.txt isn't really useful in that case:

...
script: 81: build_top=$(pwd)
script: 82: rtems_tools_source="rtems-tools.git"
script: 83: source_dir_rtems_tools=${rtems_tools_source}
source setup: rtems-tools-HEAD-1: source rtems-tools -q -n ${rtems_tools_source}
making dir: /home/EB/christian_m/Projekte/grisp-software/rtems-source-builder/rtems/sources/git
git: reset: git://git.rtems.org/rtems-tools.git
git: fetch: git://git.rtems.org/rtems-tools.git -> sources/git/rtems-tools.git
error: git command failed (/usr/bin/git): 128

I assume that the git fetch went wrong for some reason. That's really annoying because it happens after the quite time consuming build of gcc.

Please correct me if I'm wrong but as far as I know, a download in advance wouldn't do this git command. Therefore this bug can't be triggered before the build.

I'm not that familiar with that step of the RSB but would it be possible to to download a tar.bz2-snapshot of the correct commit from our git server instead of doing a git clone? The git web interface shows a URL like the following for every commit:

https://git.rtems.org/rtems-tools/snapshot/rtems-tools-9f34b38edf2a235e8d41c3265b146b0b1a4da252.tar.bz2

With that it would be possible to do all downloads in advance and then do the build without the risk that some download goes wrong during the build.

Change History (6)

comment:1 Changed on Apr 17, 2018 at 7:59:22 AM by Sebastian Huber

Milestone: Indefinite5.1
Owner: set to Sebastian Huber
Priority: lownormal
Severity: minormajor
Status: newassigned

An additional problem is that the unspecified RTEMS tools version makes the RSB tool set not reproducable (RTEMS tools version is build time dependent).

comment:2 in reply to:  1 ; Changed on Apr 17, 2018 at 10:24:46 AM by Chris Johns

Replying to Sebastian Huber:

An additional problem is that the unspecified RTEMS tools version makes the RSB tool set not reproducable (RTEMS tools version is build time dependent).

Is this to support a bisect?

I always intended to have the RSB be part of the RTEMS Tools repo however it is a lot of work for me to merge the changes in the RSB config and some other parts into the rtemstoolkit version of the modules. Another issue is all the related documentation and work flows that now exist. It is just something that got away on me and I am sorry for that.

comment:3 in reply to:  2 ; Changed on Apr 17, 2018 at 11:29:08 AM by Sebastian Huber

Replying to Chris Johns:

Replying to Sebastian Huber:

An additional problem is that the unspecified RTEMS tools version makes the RSB tool set not reproducable (RTEMS tools version is build time dependent).

Is this to support a bisect?

Yes, this is one use case.

I always intended to have the RSB be part of the RTEMS Tools repo however it is a lot of work for me to merge the changes in the RSB config and some other parts into the rtemstoolkit version of the modules. Another issue is all the related documentation and work flows that now exist. It is just something that got away on me and I am sorry for that.

I think we just have to treat the RTEMS tools like Newlib and GCC. We should specify the version explicitly.

comment:4 in reply to:  3 ; Changed on Apr 18, 2018 at 1:43:38 AM by Chris Johns

Replying to Sebastian Huber:

Replying to Chris Johns:

Replying to Sebastian Huber:

An additional problem is that the unspecified RTEMS tools version makes the RSB tool set not reproducable (RTEMS tools version is build time dependent).

Is this to support a bisect?

Yes, this is one use case.

As pointed out on the devel list newlib breaks bisecting now.

The ticket is about a git issue which is valid and stopping rtems-tools being fetched by git does not fix that issue, it just hides it. I welcome any patches related to fixing this git issue.

comment:5 in reply to:  4 Changed on Apr 18, 2018 at 5:12:08 AM by Sebastian Huber

Replying to Chris Johns:

Replying to Sebastian Huber:

Replying to Chris Johns:

Replying to Sebastian Huber:

An additional problem is that the unspecified RTEMS tools version makes the RSB tool set not reproducable (RTEMS tools version is build time dependent).

Is this to support a bisect?

Yes, this is one use case.

As pointed out on the devel list newlib breaks bisecting now.

A Newlib version update doesn't break the bisecting.

The ticket is about a git issue which is valid and stopping rtems-tools being fetched by git does not fix that issue, it just hides it. I welcome any patches related to fixing this git issue.

Yes, sorry. I should have opened a new bug.

comment:6 Changed on Apr 18, 2018 at 5:12:44 AM by Sebastian Huber

Milestone: 5.1Indefinite
Owner: Sebastian Huber deleted
Severity: majornormal
Status: assignednew
Version: 5
Note: See TracTickets for help on using tickets.