[GH-ISSUE #875] PowerPC build fails #509

Closed
opened 2026-03-04 01:46:13 +03:00 by kerem · 9 comments
Owner

Originally created by @gaul on GitHub (Dec 16, 2018).
Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/875

It is unclear to me whether this ever worked or regressed. @Basavaraju013 can you investigate this? References #866.

Originally created by @gaul on GitHub (Dec 16, 2018). Original GitHub issue: https://github.com/s3fs-fuse/s3fs-fuse/issues/875 It is unclear to me whether this ever worked or regressed. @Basavaraju013 can you investigate this? References #866.
kerem closed this issue 2026-03-04 01:46:13 +03:00
Author
Owner

@gaul commented on GitHub (Dec 17, 2018):

Failure:

$ sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java
update-alternatives: error: alternative /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java for java not registered; not setting
The command "sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java" failed and exited with 2 during .
Your build has been stopped.

From https://travis-ci.org/s3fs-fuse/s3fs-fuse/jobs/468559312#L495 .

<!-- gh-comment-id:447690372 --> @gaul commented on GitHub (Dec 17, 2018): Failure: ``` $ sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java update-alternatives: error: alternative /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java for java not registered; not setting The command "sudo update-alternatives --set java /usr/lib/jvm/java-7-openjdk-ppc64el/jre/bin/java" failed and exited with 2 during . Your build has been stopped. ``` From https://travis-ci.org/s3fs-fuse/s3fs-fuse/jobs/468559312#L495 .
Author
Owner

@Basavaraju-G commented on GitHub (Dec 17, 2018):

It is unclear to me whether this ever worked or regressed. @Basavaraju013 can you investigate this? References #866.

it worked earlier, Here is my travis passed build.
https://travis-ci.org/Basavaraju013/s3fs-fuse/jobs/460721270

Even it is passed, When i Raised PR for s3fs-fuse
https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/460730544

its failed because travis-ci updated PowerPC CPP image recently.

Build is passing in this OS version.

Runtime kernel version: 4.4.0-121-generic
travis-build version: a3472fade
Build image provisioning date and time
Mon Mar  5 07:05:18 UTC 2018
Operating System Details
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.4 LTS
Release:	16.04
Codename:	xenial
**Build image provisioning date and time
Mon Mar  5 07:05:18 UTC 2018**

In your Build i.e failed Build OS information:

Build system information
Build language: cpp
Build group: stable
Build dist: trusty
Build id: 468559309
Job id: 468559312
Runtime kernel version: 4.4.0-101-generic
travis-build version: 7e601479a
**Build image provisioning date and time
Tue Dec  5 19:58:13 UTC 2017**
<!-- gh-comment-id:447726067 --> @Basavaraju-G commented on GitHub (Dec 17, 2018): > It is unclear to me whether this ever worked or regressed. @Basavaraju013 can you investigate this? References #866. it worked earlier, Here is my travis passed build. https://travis-ci.org/Basavaraju013/s3fs-fuse/jobs/460721270 Even it is passed, When i Raised PR for s3fs-fuse https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/460730544 its failed because travis-ci updated PowerPC CPP image recently. Build is passing in this OS version. ``` Runtime kernel version: 4.4.0-121-generic travis-build version: a3472fade Build image provisioning date and time Mon Mar 5 07:05:18 UTC 2018 Operating System Details Distributor ID: Ubuntu Description: Ubuntu 16.04.4 LTS Release: 16.04 Codename: xenial **Build image provisioning date and time Mon Mar 5 07:05:18 UTC 2018** ``` In your Build i.e failed Build OS information: ``` Build system information Build language: cpp Build group: stable Build dist: trusty Build id: 468559309 Job id: 468559312 Runtime kernel version: 4.4.0-101-generic travis-build version: 7e601479a **Build image provisioning date and time Tue Dec 5 19:58:13 UTC 2017** ```
Author
Owner

@gaul commented on GitHub (Dec 17, 2018):

Should we revert the change or can you investigate this?

<!-- gh-comment-id:447728061 --> @gaul commented on GitHub (Dec 17, 2018): Should we revert the change or can you investigate this?
Author
Owner

@Basavaraju-G commented on GitHub (Dec 17, 2018):

would you change this line from trusty to xenial.
https://github.com/s3fs-fuse/s3fs-fuse/blob/master/.travis.yml#L48

<!-- gh-comment-id:447728366 --> @Basavaraju-G commented on GitHub (Dec 17, 2018): would you change this line from trusty to xenial. https://github.com/s3fs-fuse/s3fs-fuse/blob/master/.travis.yml#L48
Author
Owner

@gaul commented on GitHub (Dec 17, 2018):

Can you submit a PR for this?

<!-- gh-comment-id:447728480 --> @gaul commented on GitHub (Dec 17, 2018): Can you submit a PR for this?
Author
Owner

@Basavaraju-G commented on GitHub (Dec 17, 2018):

Can you submit a PR for this?

Sure.

<!-- gh-comment-id:447729362 --> @Basavaraju-G commented on GitHub (Dec 17, 2018): > Can you submit a PR for this? Sure.
Author
Owner

@Basavaraju-G commented on GitHub (Dec 17, 2018):

it issue with travis-ci.org. both amd64 and ppc64le jobs are running on amd64 machine only.
https://travis-ci.org/s3fs-fuse/s3fs-fuse/jobs/468559312#L495

Actually amd64 job need to run on amd64 and PowerPC job need to run on ppc64le VM.
This
but in now both jobs are running on x86 only. Checking with travis-ci support team on this issue.
Here the documentation support of ppc64le machine on travis-ci.org
https://travis-ci.community/t/linux-multiarch-testing-tips/862

<!-- gh-comment-id:447753917 --> @Basavaraju-G commented on GitHub (Dec 17, 2018): it issue with travis-ci.org. both amd64 and ppc64le jobs are running on amd64 machine only. https://travis-ci.org/s3fs-fuse/s3fs-fuse/jobs/468559312#L495 Actually amd64 job need to run on amd64 and PowerPC job need to run on ppc64le VM. This but in now both jobs are running on x86 only. Checking with travis-ci support team on this issue. Here the documentation support of ppc64le machine on travis-ci.org https://travis-ci.community/t/linux-multiarch-testing-tips/862
Author
Owner

@Basavaraju-G commented on GitHub (Dec 21, 2018):

@gaul Travis-ci.org has fixed the RabitMQ authentication details now.
Below is response from travis-ci support team.

Hi Basavaraju,

Thanks for your patience.

I talked with our engineering team and it appears there was a problem with IBM's RabbitMQ credentials.

This should be fixed now though, so can you please try running a build and let us know how it goes?

Look forward to hearing from you.

--
Luna G.

Travis CI Test and Deploy with Confidence.
www.travis-ci.com

and also builds are passing now (https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/470752015)
can we close this issue now.

<!-- gh-comment-id:449266581 --> @Basavaraju-G commented on GitHub (Dec 21, 2018): @gaul Travis-ci.org has fixed the RabitMQ authentication details now. Below is response from travis-ci support team. ``` Hi Basavaraju, Thanks for your patience. I talked with our engineering team and it appears there was a problem with IBM's RabbitMQ credentials. This should be fixed now though, so can you please try running a build and let us know how it goes? Look forward to hearing from you. -- Luna G. Travis CI Test and Deploy with Confidence. www.travis-ci.com ``` and also builds are passing now (https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/470752015) can we close this issue now.
Author
Owner

@gaul commented on GitHub (Dec 21, 2018):

This appears fixed (#874 will fix macOS failure):

https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/470774703

<!-- gh-comment-id:449517864 --> @gaul commented on GitHub (Dec 21, 2018): This appears fixed (#874 will fix macOS failure): https://travis-ci.org/s3fs-fuse/s3fs-fuse/builds/470774703
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/s3fs-fuse#509
No description provided.