Ubuntu 18.04.1 LTS (Bionic Beaver)

Any updates on this?

The slow sounds of a dying product.

1 Like

Any updates?


Upvote this


Technically speaking, they can buy themselves some time if they purchase the Extended Security Maintenance from Canonical. I hope they confirm this somewhere…

A potential issue of supporting 18.04 is that RethinkDB doesn’t officially support 18.04 yet.

Issue about it

Pre-release which supports Bionic

Not sure if that should be a blocker, given RethinkDB company shutting down https://rethinkdb.com/blog/rethinkdb-shutdown/ , and no new community releases since mid-2017. Anyone needing it can continue to use Xenial.

It would be great if Travis CI Dot Com defined what is the minimal acceptance criteria for letting a new Ubuntu version be used as part of early release , so that community members can understand the blockers, and help clear them.

1 Like

I would love to see this happen, so that we can get a more up to date g++ / libtsan ; the sanitizers for older gcc seems to be buggy and produce false positives.

I’m using a very recent Fedora in a container and the sets of tsan errors I’m getting are completely different, and I trust those more as they use gcc-9.

1 Like

I see several threads where people are already using bionic

Travis CI - Test and Deploy Your Code with Confidence seems to be reporting that it is a Bionic image

Search · bionic · GitHub has a few results.

1 Like

It’s trying to use Bionic, but the image isn’t available:

3.5 is not installed; attempting download

Downloading archive: https://storage.googleapis.com/travis-ci-language-archives/python/binaries/ubuntu/18.04/x86_64/python-3.5.tar.bz2

0.06s$ curl -sSf -o python-3.5.tar.bz2 ${archive_url}

curl: (22) The requested URL returned error: 404

Unable to download 3.5 archive. The archive may not exist. Please consider a different version.

If you need 3.5, you need to stay on Trusty.

That sounds like Bionic is now available for 2.7 and 3.6+, and indeed it is!





Will it be available for pypy and pypy3?

1 Like

My interpretation is that, Bionic is available, but in beta since it isn’t announced. Time to add them to the matrix!

I am trying to use ‘dist: bionic’, which appears in the build log as ‘Build dist: bionic’. The Xenial image is still used however with the following in the log ‘Release: 16.04’.

@na-g Are you sure you’re looking at the right build log?

In this test project it does start on Bionic:

Can you post a link to your build? It might be an bug.

@Farwaykorse Here is a link to a build: https://travis-ci.com/na-g/rouladen/jobs/213854421#L18

There is now a category
It is ‘real’ :wink:

I am seeing the same thing as na-g: using dist:bionic just results in a build with dist:xenial.

We are still using travis-ci.org and not travis-ci.com if that matters anything?

Same here

e[0Ke[33;1mBuild system informatione[0m
Build language: rust
Build group: stable
Build dist: bionic
Build id: 121535317
Job id: 221505185
Runtime kernel version: 4.15.0-1028-gcp
travis-build version: 65949ed1e
e[34me[1mBuild image provisioning date and timee[0m
Mon Mar 25 16:52:50 UTC 2019
e[34me[1mOperating System Detailse[0m
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.6 LTS
Release:	16.04
Codename:	xenial

There’s now a dedicated topic for the wrong vm issue: For `dist: bionic`, Xenial VM is used instead