Daily GIT builds of Verilator for Ubuntu on Launchpad

This is not really important stuff, please do not waste too much time on it.

I tried to setup a daily build receipt for Verilator on Launchpad. The procedure requires an import of the git repository into Bazaar. The servers attempting it reported an error. I will retry it later this week on my desktop, maybe I get some more info. I did not have this issue while importing from GitHub or Sourceforge. 2012-04-19 06:46:42 INFO Starting job. 2012-04-19 06:46:42 INFO Getting exising bzr branch from central store. 2012-04-19 06:46:42 INFO [chan bzr SocketAsChannelAdapter] Opened sftp connection (server version 3) 2012-04-19 06:46:43 INFO [chan bzr SocketAsChannelAdapter] Opened sftp connection (server version 3) 2012-04-19 06:46:43 INFO 292 bytes transferred 2012-04-19 06:46:44 INFO No branch found at remote location.

The daily build would also differ from the regular Debian package by having SystemC support enabled (for the non-final 2.3 version).

The question is, is there interest for such a build, I was planning to use it for my recent interest in testing SystemVerilog support.

Regards, Iztok Jeras

Replies (5)

RE: Daily GIT builds of Verilator for Ubuntu on Launchpad - Added by Wilson Snyder about 1 year ago

Sure, always glad to have more package builds and also good to find issues when they're introduced instead of at release time.

RE: Daily GIT builds of Verilator for Ubuntu on Launchpad - Added by Iztok Jeras about 1 year ago

Hi,

I tried to import using bazaar on my desktop and I get this: $ bzr git-import http://git.veripool.org/git/verilator bzr: ERROR: exceptions.AssertionError: Invalid object name 'ref: refs/heads/master' ... (some Python debug info)

I do not know if this is an issue with the server for the repository or the client. In any case the HTTP GIT server on VeriPool behaves differently than the server for GitHub. For example cloning from VeriPool is almost silent, while cloning from GitHub gives a verbose countdoun of blob objects.

$ git clone http://git.veripool.org/git/verilator Cloning into 'verilator'...

versus

$ git clone https://jeras@github.com/jeras/verilator.git verilator_github_https Cloning into 'verilator_github_https'... remote: Counting objects: 14035, done. remote: Compressing objects: 100% (2422/2422), done. remote: Total 14035 (delta 11878), reused 13762 (delta 11605) Receiving objects: 100% (14035/14035), 2.64 MiB | 863 KiB/s, done. Resolving deltas: 100% (11878/11878), done.

Is it possible that an old version of GIT is used to serve the repository over HTTP or is there an uncommon setting used? If you think this is a bazaar issue could you at least give me the server version and configuration, so I could use it in a bug report (if this is not a security issue).

Regards, Iztok Jeras

RE: Daily GIT builds of Verilator for Ubuntu on Launchpad - Added by Wilson Snyder about 1 year ago

A git clone seems to be working, so if it's still failing (not some intermittent server problem) I'd say it's a bzr bug.

I did just pack the repository in case it helps, though it shouldn't matter other than making it faster.

There is no "git version used to server the HTTP". That's the advantage of HTTP protocol, it's just apache doing all of the work. Anyhow in case the files are somehow different, the version used to pack the files is 1.7.0.4 and apache 2.2.14.

RE: Daily GIT builds of Verilator for Ubuntu on Launchpad - Added by Iztok Jeras about 1 year ago

Hi,

One last thing before I report a bzr bug, is it OK for me to use the Verilator repository as the example in the bug report, or would you prefer to avoid it. I do not know for what reason, but there will probably be some extra traffic while debugging the issue.

Regards, Iztok Jeras

RE: Daily GIT builds of Verilator for Ubuntu on Launchpad - Added by Wilson Snyder about 1 year ago

I'm fine for them to use it, I'm sure it's in the noise compared to all the search engine traffic.

(1-5/5)