use more granular exit codes when EasyBuildError is raised

[dagonzalezfo]

#4426
This PR will provide a basic set of error codes for EB. The included ones can be classified in 2 groups

• Eb proper codes:
  • 3: Missing easyconfig
  • 4: No specific easyblock
  • 5: Failed to import easyblock
  • 6: Failed to import class from easyblock
  • 7: No recipe for dependency (robot)
  • 8: Os dependency missing
  • 9: Unavailable sources
  • 10: Sanity check folder/file
  • 11: Can not write module at modules path
  • 12: Validate errors (this is more focus on syntax)
• Other error codes:
  • HTTP: Errors for fetching sources
  • system error codes for system calls
  • LMOD: Errors for loading module

[lexming]

I tested this PR and went ahead expanding it to cover more errors. I also created a new Enum class to gather the table of exit codes.

Please check PR dagonzalezfo#1 and specifically commit dagonzalezfo@0d31d34 with my proposed changes.

One needed change is that EasyBuild cannot forward any exit codes from HTTP requests, or from external processes, as those can be out of range (3, 128) or have the same value as the custom exit codes of EB, which would be confusing. EasyBuild should always return its own exit codes and HTTP responses or exit codes from external processes should be reported in the logs.

Example behaviour with my PR:

$ eb zlib-1.2.13-GCCcore-12.3.0.eb
[...]
== configuring...
  >> running shell command:
        potato --prefix=/home/lexming/easybuild/install/software/zlib/1.2.13-GCCcore-12.3.0
        [started at: 2024-06-11 01:51:20]
        [working dir: /home/lexming/.local/easybuild/build/zlib/1.2.13/GCCcore-12.3.0/zlib-1.2.13]
        [output and state saved to /tmp/eb-8b28i2tz/run-shell-cmd-output/potato-coba1es3]

ERROR: Shell command failed!
    full command              ->  potato --prefix=/home/lexming/easybuild/install/software/zlib/1.2.13-GCCcore-12.3.0
    exit code                 ->  127
    working directory         ->  /home/lexming/.local/easybuild/build/zlib/1.2.13/GCCcore-12.3.0/zlib-1.2.13
    output (stdout + stderr)  ->  /tmp/eb-8b28i2tz/run-shell-cmd-output/potato-coba1es3/out.txt
    called from               ->  'configure_step' function in /home/lexming/.local/venv/eb/lib64/python3.10/site-packages/easybuild/easyblocks/generic/configuremake.py (line 326)

== ... (took < 1 sec)
== FAILED: Installation ended unsuccessfully: shell command 'potato ...' failed with exit code 127 in configure step for zlib-1.2.13-GCCcore-12.3.0.eb (took 0 secs)
== Results of the build can be found in the log file(s) /tmp/eb-8b28i2tz/easybuild-zlib-1.2.13-20240611.015120.QzdZC.log
ERROR: Installation of zlib-1.2.13-GCCcore-12.3.0.eb failed: "shell command 'potato ...' failed with exit code 127 in configure step for zlib-1.2.13-GCCcore-12.3.0.eb"
$ echo $?
15

[hvelab]

Hi @lexming ,

As Danilo will be out for still some weeks more I will take care of this. Your enhancement looks impressive! About the forwarding of HTTP error codes, those are already catched in these lines as Danilo already thought of this:

https://github.com/dagonzalezfo/easybuild-framework/blob/0d31d34cb5807dd485daf349c847b41f59ce2052/easybuild/tools/filetools.py#L828

If I misunderstood you or you would like these errors to be more granular I can take a look.

[lexming]

@hvelab printing HTTP error codes in warning messages or the logs (which is what that code snippet does) is fine. What is wrong is to use those as exit code for EB as those can easily be out of range (3, 128). This is why I changed the exit code for EB in that case to well-defined EasyBuildExit.FAIL_DOWNLOAD. See a few lines further:

https://github.com/dagonzalezfo/easybuild-framework/blob/0d31d34cb5807dd485daf349c847b41f59ce2052/easybuild/tools/filetools.py#L847

[hvelab]

@lexming Great! Then, is there something left to do with this PR from Danilo's part? Please let us know if we can help in any way with your enhancement

[boegel]

@hvelab We need to get dagonzalezfo#1 merged, which will update this PR.

@lexming I think we can do this without having @dagonzalezfo around though?

[dagonzalezfo]

Hi, I will take care of it along this week :)

[lexming]

LGTM

[dagonzalezfo]

Dear @lexming, thanks for your help and improvement on this

[lexming]

LGTM

[boegel]

lgtm

[boegel]

Thanks a lot for all the effort on this @dagonzalezfo and @lexming!