Build fail PYTHIA6

O²
1

Dear experts, while building AliceO2 (within the alidock environment) with

aliBuild init O2@dev --defaults o2

I have a problem with PYTHIA6 (log in https://www.dropbox.com/s/5czh71n4p7rhron/log):

==> Building pythia6@428-alice1_O2
==> pythia6 is being built (use --debug for full output): failed
ERROR: Error while executing /persist/sw/SPECS/slc7_x86-64/pythia6/428-alice1_O2-1/build.sh on `alidock-2376’.
ERROR: Log can be found in /persist/sw/BUILD/pythia6-latest/log.
ERROR: Please upload it to CERNBox/Dropbox if you intend to request support.
ERROR: Build directory is /persist/sw/BUILD/pythia6-latest/pythia6.

Any hint? Thanks!
Antonio

2

(I’m using mac os Mojave)

3

That package should be downloaded, not built. It works correctly for me, the package is effectively downloaded.

Look carefully at the error message:

++ tar -x -C /persist/sw/INSTALLROOT/79c6188d37766459955ec25ef918022194779b0e/slc7_x86-64/pythia6/428-alice1_O2-1
tar: lib: Cannot stat: No such file or directory
tar: include: Cannot stat: No such file or directory
tar: Exiting with failure status due to previous errors

The package is being downloaded, but you have probably run out of disk space (inside the container).

Now, a bunch of suggestions.

  1. Always have alidist up-to-date within alidock (you probably do)
  2. Check the macOS configuration: you need to assign some space to your Docker disk
  3. I believe 64 GB is more than enough, but there’s probably some “leftover” from previous builds.

In practice before running anything else, confirm you have a disk size problem. From within alidock:

df -h

And before compiling, do a thorough cleanup:

aliBuild clean --aggressive

You may want to run aliBuild in verbose mode now:

aliBuild build O2 --defaults o2 --debug
4

Thanks Dario, the command

df -h

gives the following output:

[alidock] /persist/sw/BUILD/pythia6-latest $> df -h
Filesystem Size Used Avail Use% Mounted on
overlay 59G 6.7G 49G 12% /
tmpfs 64M 0 64M 0% /dev
tmpfs 3.0G 0 3.0G 0% /sys/fs/cgroup
/dev/sda1 59G 6.7G 49G 12% /persist
osxfs 932G 636G 285G 70% /home/alidock
shm 64M 0 64M 0% /dev/shm
tmpfs 3.0G 0 3.0G 0% /proc/acpi
tmpfs 3.0G 0 3.0G 0% /sys/firmware

As far as I can understand, it doesn’t seem to be a disk size problem (in any case, this is the very first installation of ALICE software I do within alidock). Shall I proceed with the aggressive cleaning + the verbose building?

Cheers,
Antonio

5

I’d say so. It seems there is something corrupted with your tarball. An aggressive cleanup should cure it.

6

Hi, I tried and the building still fails with PYTHIA6, with the same error as before. Could I try anything else?

Cheers,
Antonio

7

Thanks Dario, the command df -h gives the following output:

[alidock] /persist/sw/BUILD/pythia6-latest $> df -h

Filesystem      Size  Used Avail Use% Mounted on

overlay          59G  6.7G   49G  12% /

tmpfs            64M     0   64M   0% /dev

tmpfs           3.0G     0  3.0G   0% /sys/fs/cgroup

/dev/sda1        59G  6.7G   49G  12% /persist

osxfs           932G  636G  285G  70% /home/alidock

shm              64M     0   64M   0% /dev/shm

tmpfs           3.0G     0  3.0G   0% /proc/acpi

tmpfs           3.0G     0  3.0G   0% /sys/firmware

As far as I can understand, it doesn't seem to be a disk size problem (in any case, this is the very first installation of ALICE software I do within alidock).

Cheers,

Antonio
8

Hello Antonio, so first off, to give you some context - what is going on is happening in a CC7 environment. alidock itself has nothing to do with it. It still is bizarre and a bit unexpected.

Let’s try the nuclear solution then.

rm -rf $ALIBUILD_WORK_DIR/!(MIRROR)

Do it in an alidock console. Please copy it as it is. This will remove everything (except the MIRROR directory).

When you are done, run:

aliBuildUpdateMirrors

There is no space after aliBuild and this command may ask you for a password. When done, make sure that your $ALIBUILD_WORK_DIR contains only MIRROR, which is a symlink to /home/alidock/.sw/MIRROR:

ls -l $ALIBUILD_WORK_DIR

You can then try to start over (update alidist and O2 first):

aliBuild build O2 --defaults o2 --debug
9

Thanks Dario, I’m about to start over the O2 building, but before I shall update alidist and O2: could you please remind me the corresponding commands, just to avoid any mistake?

10

As Git contributor you must know how to do that… in brief:

cd alidist; git checkout master; git pull; cd ..
cd O2; git checkout dev; git pull; cd ..
11

Thanks, I wanted to be 200% sure :slight_smile: And by the way the build now worked fine!!

1 Like